-
|
I'm setting up a new privately hosted instance in a docker container. When I try to sign up I get: The log file shows: And here is my compose file: Any thoughts on why this might be happening? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
|
Wanted to try fizzy for the first time, same issue. I have an even simpler docker configuration, i just launched the container with
(secret key generated by |
Beta Was this translation helpful? Give feedback.
-
|
I've not been able to reproduce this yet. That simple Can I ask a bit more about the setup you both have?
|
Beta Was this translation helpful? Give feedback.
-
|
I'm using Brave on macOS 15.5 as a browser, the container itself is running on a Debian vm on Proxmox in the local network. Same issue in Safari. In regards to the missing mail config, I didn't realize an smtp server was mandatory. It would be great to be able to test the software without an email provider, especially when running in the single tenant mode and creating the first user. This is my complete container log. |
Beta Was this translation helpful? Give feedback.
-
|
I tried to find out if my problem has something to do with the mail config and provided an smtp configuration. I use mailpit to replace an smtp server for my test scenario. This is the docker compose file I came up with. Is there a way to produce more detailed logs via environment args to further investigate this? name: fizzy
services:
web:
image: ghcr.io/basecamp/fizzy:main
restart: unless-stopped
ports:
- 80:80
environment:
DISABLE_SSL: true
SECRET_KEY_BASE: ee90237ddc9bb4d8b0676c4ef921ad6f
MAILER_FROM_ADDRESS: [email protected]
SMTP_ADDRESS: mailpit
SMTP_PORT: 1025
SMTP_USERNAME: user
SMTP_PASSWORD: pass
volumes:
- fizzy:/rails/storage
mailpit:
image: axllent/mailpit
restart: unless-stopped
ports:
- 8025:8025
environment:
MP_MAX_MESSAGES: 5000
MP_DATABASE: /data/mailpit.db
MP_SMTP_AUTH_ACCEPT_ANY: 1
MP_SMTP_AUTH_ALLOW_INSECURE: 1
volumes:
- mailpit:/data
volumes:
fizzy:
mailpit: |
Beta Was this translation helpful? Give feedback.
-
|
For now, I'm accessing the container directly. Same result on Arc, Safari and Firefox. Removing the mail variables doesn't seem to change anything. |
Beta Was this translation helpful? Give feedback.
-
|
We actually just re-enabled default debug logging in the container. If you pull and try again, can you see any clues in the container logs for what's triggering the 422? |
Beta Was this translation helpful? Give feedback.
-
|
Yep, same for me. |
Beta Was this translation helpful? Give feedback.
-
|
Would you mind checking in the browser console if the request is including a e.g. for me I see: |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if I'm looking in the right place, but I don't see that header: 
|
Beta Was this translation helpful? Give feedback.
-
|
Ahh, that's the problem. That header won't be sent unless you're in a secure context, which in this case means either using HTTPS or accessing it locally (localhost). I see in that case the origin is We'll look into how to support this use case. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks - that would be great! I confirmed that throwing the same instance behind a reverse proxy does not result in this error. |
Beta Was this translation helpful? Give feedback.
-
|
I'll just chime in and say I am experiencing the same issue. Unraid docker config, mail setup and apparently working. Got the same error: Can't verify CSRF token authenticity |
Beta Was this translation helpful? Give feedback.
-
|
Adding on, this seems to be the likely culprit case. #2080 seemed to be the last PR that worked. |
Beta Was this translation helpful? Give feedback.
Ahh, that's the problem. That header won't be sent unless you're in a secure context, which in this case means either using HTTPS or accessing it locally (localhost). I see in that case the origin is
http://192.168.1.251:8011, so neither of those.We'll look into how to support this use case.