- Used Zammad version: 3.4.x
- Used Zammad installation source: (source, package, …) Package
- Operating system: Centos8
- Browser + version: Brave/Chrome/Edge
I am having issues with a missing .js file causing the page to stay on “loading”
2020/06/26 11:17:20 [error] 12513#0: *1872 open() "/opt/zammad/public/assets/application-487103299795db0ee0f7ab6c99f90b10e70fe5458abd9cde341bc5e09a118fda.js" failed (2: No such file or directory), client: 18.104.22.168, server: support, request: "GET /assets/application-487103299795db0ee0f7ab6c99f90b10e70fe5458abd9cde341bc5e09a118fda.js HTTP/1.1", host: "support", referrer: "https://support/"
I downgraded through all 3.4.x versions and none worked, so currently back on version 3.3.
I’ve seen this issue very rarely and could never reproduce it.
It happened to me once.
The fast and dirty solution of me was to simply rename the files in
/opt/zammad/public/ to the file name your browser expects to.
I hope that helps.
After that I never had any further issues again. I can’t tell why it’s happening.
It seems that I didn’t have YARN installed on the Centos8 host. I picked this up when running a manual assets pre-compile task. Ill monitor it and see how it goes on the next upgrade.
I’m glad you could solve your issue.
I just wanted to follow up on the Yarn topic.
It usually is no problem if it’s not installed. That warning is perfectly fine and can safely be ignored.
It shouldn’t change the correct creation of precompiled assets at all.
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.