Cannot log in to migrated 1.14.3 instance

Problem:

I am attempting to migrate a 1.14.3 instance from an Ubuntu 14.04 machine to a 16.04 one so I can use the package availability to upgrade the instance later. After I import the database dump, I am unable to log in with any account, either LDAP based or the admin account using the password that is confirmed working on the original instance. Using “foreman-rake permissions:reset” is also fruitless; I cannot log in as admin with the new password foreman-rake provides me with.

Oddly, resetting the database with db:migrate + db:seed still doesn’t let me log in, even though the fresh install certainly did.

Expected outcome:

Able to log in to at least the local admin account after database import.

Foreman and Proxy versions:

Foreman 1.14.3
foreman-proxy 1.14.3-1

Foreman and Proxy plugin versions:

foreman-tasks 0.8.6
foreman-discovery 8.0.1
foreman-docker 3.0.0

Other relevant data:
I haven’t been able to find much in the way of relevant error messages or logs, but this seems to cover the login process:

2018-08-08T15:00:34 329bef52 [app] [I] Started POST “/users/login” for 10.46.50.98 at 2018-08-08 15:00:34 +0200
2018-08-08T15:00:34 329bef52 [app] [I] Processing by UsersController#login as HTML
2018-08-08T15:00:34 329bef52 [app] [I] Parameters: {“utf8”=>"<9C><93>", “authenticity_token”=>“IRuTa2ZANyMuCJ4K5kfdXzY/MzrJ9dDozMin0UV8pq2Bnyq2aA2tFKwD/s7fbDYANwEuPzlHaZ+6ODG/7C8YSQ==”, “login”=>{“login”=>“admin”, “password”=>"[FILTERED]"}, “commit”=>“Login”}
2018-08-08T15:00:34 329bef52 [app] [I] Redirected to https://foreman-ng.dev.drint.net/users/login
2018-08-08T15:00:34 329bef52 [app] [I] Completed 302 Found in 9ms (ActiveRecord: 3.1ms)
2018-08-08T15:00:34 321a74d6 [app] [I] Started GET “/users/login” for 10.46.50.98 at 2018-08-08 15:00:34 +0200
2018-08-08T15:00:34 321a74d6 [app] [I] Processing by UsersController#login as HTML
2018-08-08T15:00:34 321a74d6 [app] [I] Rendered users/login.html.erb within layouts/login (2.2ms)
2018-08-08T15:00:34 321a74d6 [app] [I] Rendered layouts/base.html.erb (1.1ms)
2018-08-08T15:00:34 321a74d6 [app] [I] Completed 200 OK in 6ms (Views: 3.9ms | ActiveRecord: 0.2ms)
2018-08-08T15:00:34 321a74d6 [app] [I] Started GET “/javascripts/locale/en_GB/app.js” for 10.46.50.98 at 2018-08-08 15:00:34 +0200
2018-08-08T15:00:34 321a74d6 [app] [F]
| ActionController::RoutingError (No route matches [GET] “/javascripts/locale/en_GB/app.js”):
| lib/middleware/tagged_logging.rb:18:in `call’
|
|
2018-08-08T15:00:34 321a74d6 [app] [I] Started GET “/javascripts/locale/en_GB/app.js” for 10.46.50.98 at 2018-08-08 15:00:34 +0200

Never mind - it appears that either Apache or my browser had cached something. A restart of Apache and now I am able to log in.

Sorry, false alarm.