mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #1809] 💬 [Question] Running cypht behind reverse proxy fails #713
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#713
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dakky on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1809
💬 Question
I just installed the app via docker compose. I simply took the docker-compose.yaml from this repo.. I extended the labels of the app container for my traefik (reverse proxy settings) in a manner i did quite often for other apps.
After starting the stack i can login and there the problems begin.
I get a completely broken page:
The browser console does not look so very fine:
Any idea how to fix that?
@IrAlfred commented on GitHub (Dec 11, 2025):
Thanks @dakky for reporting this!
We’re going to look into the issue. To help us investigate further, could you provide a bit more information about your setup? Especially the details of your reverse proxy (Traefik) configuration.
In particular, it would be useful to know:
This will help us reproduce the issue and understand why the page appears broken after login. This seems to be related to https://github.com/cypht-org/cypht/issues/1416
Thanks again for taking the time to report this!
@dakky commented on GitHub (Dec 11, 2025):
Of course.
Here are my labels attached to the container:
So basically there are no "special" middlewares or rewrite rules involved.
I added a debug container in order to see the requests headers, which are sent to the app:
oh and of course the logfile (i tried to catch the relevant parts, as it is quite repetative):
@IrAlfred commented on GitHub (Dec 12, 2025):
Thank you @dakky for providing these details
@indridieinarsson commented on GitHub (Dec 12, 2025):
@dakky : Have you tried setting the DISABLE_ORIGIN_CHECK environment variable to false? It's explained here :
github.com/cypht-org/cypht@7c4c2bfe32/config/app.php (L256)I am running cypht behind traefik, and setting this to false was necessary for it to work.
There is a .env.example file in the repo, it is handy to use that as a starting point and include it via
@dakky commented on GitHub (Dec 12, 2025):
unfortunetely this does not change anything. And
falseis the default as your codesnipplet shows. But i triedtruetoo with no change in the behavior.@dakky commented on GitHub (Dec 12, 2025):
omfg ... it is working. it seems the latest tag ist totally broken. I set it statically to 2.5.1 and now its working.
examing this on dockerhub looks strange:
latest:
2.5.1:
when looking deeper the latest tag points to 2.5.0, which seems to have at least an issue.
so basically 2 things need fixing:
@indridieinarsson commented on GitHub (Dec 13, 2025):
Sorry for messing things up.
DISABLE_ORIGIN_CHECK=true (this time copy-paste from my config, to circumvent my goldfish-memory)
this is how it is in my config. Disable the origin check, since the reverse proxy messes with the origin of the cookies. Or that's the way I understood it when setting things up.
But good thing you got it working anyway, just wanted to clear things up for future error-hunters, since my last comment was factually wrong.
And it's always a good idea to take a look at the logs (docker compose logs) and look out for errors in there.