Assets not found - ActionController::RoutingError (No route matches [GET] (<assets-here>))


The web interface is unable to find its assets rendering it unusable. Puppetserver and the ENC are working normally.


The system is installed from packages on centos 7. Foreman’s web interface stopped working normally when it was updated from 1.17.0 to 1.17.1.

Initially, the system was searching for asset-hash.ext where the hash was incorrect for each asset. This was possibly due to old files in the webpack directory, but I’m not certain.

However, since i’ve:

  • clobbered the assets with foreman-rake
  • uninstalled and reinstalled the foreman package RPMs
  • recovered our configs and rerun the foreman-installer

We put an install of 1.17.1 on a similar VM, which works fine, so we can verify our installation steps and perform comparisons.

example log output:

2018-05-31T15:37:04 e49c4129 [app] [I] Started GET "/stylesheets/application.css" for at 2018-05-31 15:37:04 +0000
2018-05-31T15:37:04 e49c4129 [app] [F]   
2018-05-31T15:37:04 e49c4129 [app] [F] ActionController::RoutingError (No route matches [GET] "/stylesheets/application.css"):
2018-05-31T15:37:04 e49c4129 [app] [F]   
2018-05-31T15:37:04 e49c4129 [app] [F] lib/middleware/tagged_logging.rb:18:in `call'
2018-05-31T15:37:04 8578887f [app] [I] Started GET "/javascripts/password_strength.js" for at 2018-05-31 15:37:04 +0000
2018-05-31T15:37:04 abb32155 [app] [I] Started GET "/javascripts/application.js" for at 2018-05-31 15:37:04 +0000
2018-05-31T15:37:04 fbc6b764 [app] [I] Started GET "/javascripts/locale/en/app.js" for at 2018-05-31 15:37:04 +0000
2018-05-31T15:37:04 8578887f [app] [F]   
2018-05-31T15:37:04 8578887f [app] [F] ActionController::RoutingError (No route matches [GET] "/javascripts/password_strength.js"):

I did compare the files in ~foreman/public/webpack (manifest & the bundle/vendor files) and they’re identical on the system that works and the system that doesn’t.

I’m not quite sure where to proceed with debugging but i’d definitely appreciate a point in the right direction. Thanks!


the only thing that I’d try is cleaning a browser cache or open anonymous mode and see if the issue persist

ping @ui_ux team for more ideas


Hi Marek - I ended up just reinstalling the host after deciding to cut my losses on the debugging attempts. Thanks!