You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enter admin in production environment. Tested in local production simulation as well as on my real production domain (screenshots from local simulation).
Expected behavior
Icons should appear
Actual behavior
Tell us what happens instead
Note that all other assets including other font files come through
And that they seem to be listed correctly in manifest:
Steps to reproduce
Enter admin in production environment. Tested in local production simulation as well as on my real production domain (screenshots from local simulation).
Expected behavior
Icons should appear
Actual behavior
Tell us what happens instead
Note that all other assets including other font files come through
And that they seem to be listed correctly in manifest:
(manifest mentioned file exists:
public/assets/fa-regular-400-532a487f4862ddaa7de6f6e1f79b03ff25ac5f2ad8ab683a9edfa0ab85f81629.woff
)I noticed that the request url is a bit off with double //:
assets//fa-regular-400.woff
Editing this and resending the request did nothing...
Detailed request info:
Similar issues. Not sure if related as they use gem variants.
bokmann/font-awesome-rails#74
bokmann/font-awesome-rails#183
System configuration
Here is my nginx conf (docker setup)
https://gist.github.com/satendra02/1b335b06bfc5921df486f26bd98e0e89#file-nginx-conf
The text was updated successfully, but these errors were encountered: