# Zammad 3.2 not working after Upgrade from 3.1 (no CSRF problem)
**URL:** https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734
**Category:** Technical assistance
**Created:** [January 4, 2020, 5:25pm UTC](https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734 "2020-01-04T17:25:56Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@jandoe](https://community.zammad.org/u/jandoe)
#### Post date: [January 4, 2020, 5:25pm UTC](https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734/1 "2020-01-04T17:25:56Z")
Hi. After upgrading from 3.1 to 3.2 today via [dl.packager.io](http://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/](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](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.
---
### Author:  [@jandoe](https://community.zammad.org/u/jandoe)
#### Post date: [January 4, 2020, 5:38pm UTC](https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734/2 "2020-01-04T17:38:07Z")
I have made an quick fix with a symlink to the newest .js-file:
root@fubbes:/opt/zammad/public/assets# la
total 10312
drwxr-xr-x 14 zammad zammad 16384 Jan 4 18:34 .
drwxr-xr-x 3 zammad zammad 4096 Jan 4 17:10 …
drwxr-xr-x 2 zammad zammad 4096 Jan 4 17:10 addons
drwxr-xr-x 3 zammad zammad 4096 Jun 19 2018 app
lrwxrwxrwx 1 root root 79 Jan 4 18:34 application-02dec2fdbb40aef3ac5ab52ce6b64a4a0b29b18e0b74f4305f7f5e2ed3c18a97.js -\> application-8b3b086b13912d0efd4f768145a11223d2a7b3e81361ac29e8c40fcb84dbd70e.js
Now it works…
---
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [January 5, 2020, 5:41pm UTC](https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734/3 "2020-01-05T17:41:21Z")
Glad you could somehow fix this, normally a `zammad run rake assets:precompile` should solve this situation as well.
It’s not happening by default (normally).
---
### Author:  [@jandoe](https://community.zammad.org/u/jandoe)
#### Post date: [January 8, 2020, 2:11pm UTC](https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734/4 "2020-01-08T14:11:40Z")
Ok thank you. If it happens again at the next update, i will try that.
---
### Author:  [@system](https://community.zammad.org/u/system)
#### Post date: [May 7, 2020, 2:11pm UTC](https://community.zammad.org/t/zammad-3-2-not-working-after-upgrade-from-3-1-no-csrf-problem/3734/5 "2020-05-07T14:11:42Z")
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.