# Fresh install 3.2.x: CSRF token verification failed
**URL:** https://community.zammad.org/t/fresh-install-3-2-x-csrf-token-verification-failed/3080
**Category:** Technical assistance
**Created:** [September 11, 2019, 7:53am UTC](https://community.zammad.org/t/fresh-install-3-2-x-csrf-token-verification-failed/3080 "2019-09-11T07:53:15Z")
**Posts on this page:** 1
**Showing post:** 20
### Author:  [@MrGeneration](https://community.zammad.org/u/MrGeneration)
#### Post date: [December 4, 2019, 7:43am UTC](https://community.zammad.org/t/fresh-install-3-2-x-csrf-token-verification-failed/3080/20 "2019-12-04T07:43:11Z")
> [@YosefAdPro](#):
>
> i have same problem on my Centos 7 + NGINX after update from 3.1 to 3.2.
> CSRF token verification failed.
Please have a look at the above commends from other users with nginx. 🙂
> [@cornelinux](#):
>
> I also run an update on Ubuntu from 3.1 to 3.2 and experience the same issue.
> With nginx adding
>
> ```auto
> proxy_set_header X-Forwarded-Proto https;
>
> ```
>
> in the `location /` worked out for me.
> [@herzkerl](#):
>
> Thank you very much—that worked for me as well.
>
> I have changed
>
> ```auto
> proxy_set_header X-Forwarded-Proto $scheme;
>
> ```
>
> to
>
> ```auto
> proxy_set_header X-Forwarded-Proto https;
>
> ```
>
> and that did it. Also, I wanted to share with the community the nginx config from the Plesk host (which is used only to forward the hostname/subdomain to the internal/NAT ip)—maybe it’ll be of any help for someone else…
>
> ```auto
> location ~ ^/(?!(.well-known)) {
> proxy_pass http://:80;
> proxy_set_header Host $http_host;
> proxy_set_header CLIENT_IP $remote_addr;
> proxy_set_header X-Real-IP $remote_addr;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> }
>
> ```
---
_[View the full topic](https://community.zammad.org/t/fresh-install-3-2-x-csrf-token-verification-failed/3080)._