White page when trying to access "/auth/callback?code=CODE"

When trying to access https://crm.avocat-ludusan.ro/auth/callback?code=THECODE I’m getting a white page. In the Console the error I’m getting is:

vue.esm.js:1897 Error: state does not match
    at Ne.<anonymous> (index.es.js:1657)
    at Generator.next (<anonymous>)
    at index.es.js:65
    at new Promise (<anonymous>)
    at b (index.es.js:61)
    at Ne.handle (index.es.js:1641)
    at An.<anonymous> (app.js:25)
    at u (index.es.js:14257)
    at Generator._invoke (index.es.js:14432)
    at Generator.forEach.e.<computed> [as next] (index.es.js:14300)

This occurs when doing the initial/first user registration.

Any idea on how to fix this?

Does this happen every time?
Did you go back&forward in the browser?
What kind of browser do you use?
Do you have cookies enabled?


Does this happen every time?

Yes, for all users, including now. Please feel free to create a new user at https://crm.avocat-ludusan.ro

Did you go back&forward in the browser?


What kind of browser do you use?

Chrome, Firefox and Safari, both on Windows and Mac. Happens on all.

Do you have cookies enabled?

Yes. There’s no cookie blocker, nor ad blocker.

Also this occurs when using jwilder/nginx-proxy and jrcs/letsencrypt-nginx-proxy-companion. Can you please try on your end, because on my end it fails each time, on any deployment I’m testing.

What I see from here – you are making requests to http and not https.
This is (probably) where data (state) gets lost

See your config.js file (https://crm.avocat-ludusan.ro/config.js)

Should point to https.

Not sure what you changed and where you changed it. Hope this helps you.

I didn’t changed anything. I’m executing this:

version: '3.5'

    image: cortezaproject/corteza-server
    restart: on-failure
    env_file: [ .env ]
    depends_on: [ db ]
    volumes: [ "./data/server:/data" ]
      - "8081:80"

    image: postgres:13
    restart: on-failure
    healthcheck: { test: ["CMD-SHELL", "pg_isready -U corteza"], interval: 10s, timeout: 5s, retries: 5 }
      POSTGRES_USER:     corteza
      POSTGRES_PASSWORD: corteza

Here’s the .env:


After this I’m forwarding 443 to 8081. I’ve tried both by using a standard NGINX daemon, and with Nginx Proxy Manager.

server {
	set $forward_scheme http;
	set $server "";
	set $port 8081;

	listen 80;
	listen 443 ssl http2;

	server_name crm.avocat-ludusan.ro;

	ssl_session_timeout 5m;
	ssl_session_cache shared:SSL:50m;
	ssl_protocols TLSv1.2 TLSv1.3;
	ssl_prefer_server_ciphers off;

	ssl_certificate /etc/letsencrypt/live/npm-3/fullchain.pem;
	ssl_certificate_key /etc/letsencrypt/live/npm-3/privkey.pem;

	location / {
		add_header       X-Served-By $host;
		proxy_set_header Host $host;
		proxy_set_header X-Forwarded-Scheme $scheme;
		proxy_set_header X-Forwarded-Proto  $scheme;
		proxy_set_header X-Forwarded-For    $remote_addr;
		proxy_set_header X-Real-IP          $remote_addr;
		proxy_pass       $forward_scheme://$server:$port;

I’m not touching the Docker container any form.

Can you please provide a working NGINX config, just to be sure that NGINX is not involved in any way?

Please note that this occurs only when using HTTPS. It works as expected via HTTP.

Please see my last post here:

1 Like

So basically I should just add this to .env?


LETSENCRYPT_HOST=... should be would be enough.