mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #1020] Unraid Docker Compose access denied for user 'cypht'@'172.17.0.1' #546
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#546
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 @ansonryan on GitHub (May 14, 2024).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1020
Originally assigned to: @IrAlfred on GitHub.
💬 Question
During the installation through Unraid compose, the log reported the following warnings:
My configuration on Unraid compose is as follows:
@marclaporte commented on GitHub (May 14, 2024):
FYI, we are working to revamp our Docker support
WIP: https://github.com/cypht-org/cypht/pull/1001
Context: https://github.com/cypht-org/cypht-docker/issues/31
@marclaporte commented on GitHub (Sep 28, 2024):
@ansonryan Please retest with latest release: https://hub.docker.com/r/cypht/cypht
@IrAlfred commented on GitHub (Aug 23, 2025):
Hello @ansonryan,
The latest release, Cypht 2.4.2, is now available on Docker Hub. Could you please retest when you have a moment?
You can pull it from: https://hub.docker.com/r/cypht/cypht
We're waiting for your feedback to confirm everything is working so we can close this issue. Thank you!
@IrAlfred commented on GitHub (Sep 24, 2025):
Hello @ansonryan
I'm closing the issue, but please reopen it if you experience the problem again on the latest version.
@Neon-44 commented on GitHub (Nov 13, 2025):
not the original author, but I still get the Error.
I get a 502 on the website, the logs show failed login to the database. I assume that's the Cause for the 502. Can you reopen this @IrAlfred ?
@IrAlfred commented on GitHub (Nov 13, 2025):
Which version are you currently using ?
We need more details about your issue so we can try to reproduce and fix
@Neon-44 commented on GitHub (Nov 13, 2025):
502 was me reverse proxying to a nonexistent container, i am sorry, please ignore that.
I am on tag latest. I pruned all volumes and deleted the data dir in hopes of re-creating a fresh envronment. I have also tried to select the most important stuff from the logs:
at first it all seems to work
But then I get the first error. Funnily enough it seems that the Database only now starts, even though cypht before already logged that it successfully connected.
and then at the end of the log I have a
@IrAlfred commented on GitHub (Nov 13, 2025):
@Neon-44
To help us investigate this issue efficiently, can you please share the content of your docker-compose.yml file?
For your security, please remember to:
Redact any sensitive information like passwords, or secrets before sharing.
You can replace them with placeholders like [REDACTED] or [SECRET].
This will allow us to replicate your environment and identify the root cause. Thank you!
@Neon-44 commented on GitHub (Nov 13, 2025):
Galdly. It is mainly just your example with
@IrAlfred commented on GitHub (Nov 13, 2025):
Thank you @Neon-44
I've been able to reproduce the issue. The error indicates the user was configured for localhost access only. I'm investigating the root cause and will provide an update once I have more information.
@IrAlfred commented on GitHub (Nov 13, 2025):
@Neon-44
You can use this workaround meanwhile