CSRF token verification failed

  • Used Zammad version: 3.2
  • Used Zammad installation source: package
  • Operating system: ubuntu 16.04.6
  • Browser + version: Chrome/Firefox

Actual behavior:

On login I get the error:

CSRF token verification failed

Since this night I’m not able to login into my Zammad installation.

Since 01:37 this morning there are a lot of the following erros in my log file:

error log

[Wed Dec 04 01:37:08.223377 2019] [proxy:error] [pid 14708] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:6042 (localhost) failed
[Wed Dec 04 01:37:08.223583 2019] [proxy:error] [pid 14708] AH00959: ap_proxy_connect_backend disabling worker for (localhost) for 60s
[Wed Dec 04 01:37:08.223596 2019] [proxy_wstunnel:error] [pid 14708] [client 79.192.201.109:39696] AH02452: failed to make connection to backend: localhost
[Wed Dec 04 01:37:08.223811 2019] [proxy:error] [pid 14708] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:3000 (localhost) failed
[Wed Dec 04 01:37:08.223820 2019] [proxy:error] [pid 14708] AH00959: ap_proxy_connect_backend disabling worker for (localhost) for 60s
[Wed Dec 04 01:37:08.223824 2019] [proxy_http:error] [pid 14708] [client 79.192.201.109:39696] AH01114: HTTP: failed to make connection to backend: localhost
[Wed Dec 04 01:37:13.156531 2019] [proxy:error] [pid 16623] (111)Connection refused: AH00957: WS: attempt to connect to 127.0.0.1:6042 (localhost) failed

Any idea what could be wrong? It worked for weeks without any problems…

Please take a look at this thread which is quite current:

By the way, connection refused has nothing to do witgh CSRF and means that Zammad proberbly doesn’t run.

1 Like

Oh, gosh…
I saw/read the topic but didn’t saw the last posts.
Thanks a lot your solution worked for my.