Hi. After upgrading from 3.1 to 3.2 today via dl.packager.io package, zammad-web ist stuck at “Loading…”. Strange thing: On my own Chrome-Browser it works. On all other clients and and browsers it does not start. I use apache-proxy with CSRF-patch and the CSRF-message does not appear in production.log. But the following 404-message is in apache access.log:
80.xx.xx.xx - - [04/Jan/2020:18:11:19 +0100] “GET /assets/application-02dec2fdbb40aef3ac5ab[…]5e2ed3c18a97.js HTTP/1.1” 404 441 “https://service.xxx.com/” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36”
The mentioned *.js-file does not exist in /opt/zammad/public/assets
- Used Zammad version: 3.2
- Used Zammad installation source: deb https://dl.packager.io/srv/deb/zammad/zammad/stable/ubuntu 18.04 main
- Operating system: Ubuntu 18.04
- Browser + version: Firefox 68.3.0 ESR + Google Chrome 78.0.3904.108
Expected behavior:
Start Zammad Dashboard
Actual behavior:
Shows just “Loading…”-message.