Potential Cookie issue behind reverse proxy

Support
1

My version of HedgeDoc is: 1.9.7

What I expected to happen:
When clicking “+ new guest note” the editor should load.

What actually happened:
I just see a loading spinner when clicking +new guest note.
The console shows:
AUTH failed: Cookie is invalid.

I already tried:

Reverse proxy file: I’m using caddy v2 so it shouldn’t need any real config other then reverse_proxy.
The main site loads fine, it’s only when you click end up at the editor via /new

I also checked the Docker compose files. The containers can communicate (main site works) and I believe hedgedoc is configured correctly:

  • CMD_DOMAIN=hedgedoc.mydomain
  • CMD_USESSL=false
  • CMD_PROTOCOL_USESSL=true
  • CMD_ALLOW_ORIGIN=[‘hedgedoc.mydomain’]
  • CMD_HSTS_ENABLE=true

Also tried this one, but i’m getting out of my depth here:

  • CMD_COOKIE_POLICY=none

The network tab shows the requests are all green. The socket.io upgrades too. It’s just that cookie message.

Actual cookies for the domain are as follows:

|space_units|4|hedgedoc.mydomain|/|2024-03-16T20:40:38.000Z|12||✓|None||Medium||
|indent_type|spacehedgedoc.mydomain|/|2024-03-16T20:40:38.000Z|16||✓|None||Medium||
|keymap|sublime|hedgedoc.mydomain|/|2024-03-16T20:40:38.000Z|13||✓|None||Medium||
|loginstate|false|hedgedoc.mydomain|/|2024-03-16T21:27:02.000Z|15||✓|None||Medium||

2

Nevermind, I solved it! :grin:

I had to add this to the Caddyfile:

 header_up X-Forwarded-Proto {scheme}

I was led to believe this was the default case with caddy v2 but it appears not!

Hopefully this helps somebody else in the future.

Nothing to see here, you can go about your business; move along.

P.S. it does say there are three exceptions here:
reverse_proxy (Caddyfile directive) — Caddy Documentation (caddyserver.com)