Repository navigation
[BUG] #887
Description
Describe the Bug
on latest ghcr.io/tinyauthapp/tinyauth:nightly got
ERR internal/controller/context_controller.go:107 > Failed to create user context from request error="user context not found" stream=app
and ui and redirect not work, work only path.allow
How to Reproduce
Expected Behavior
ui and redirects
Additional Context
No response
Logs
No response
Operating System
No response
Browser
No response
Tinyauth Version
No response
Docker Version (if applicable)
No response
Human Written Confirmation
- I confirm this issue was written by me and not generated by an LLM or AI assistant.
Activity
scottmckendry commentedon May 21, 2026
Thanks for reporting @temperance447
Should be fixed in the next nightly. Resolved by #888. Can you retest in ~4 hours when the new version is built and tagged?
temperance447 commentedon May 22, 2026
Thanks.
On the latest
nightly-distrolesseverything started working perfectly.temperance447 commentedon May 22, 2026
Hello again. same error when client_ip available
and path.allow not work with 307 error
steveiliop56 commentedon May 22, 2026
@temperance447 the logs you are sharing don't contain any useful information. This debug line just states it didn't find a user context, not a warning, not an error just an informational debug message. We cannot understand what's going wrong with two irrelevant log lines. Please share your setup, proxy config and the entire logs so as we can understand what's not working and resolve the issue.
temperance447 commentedon May 22, 2026
this error
temperance447 commentedon May 22, 2026
and previous error in file context_controller.go
new error in file proxy_controller.go
and used traefik with host X-Forwarded-For/X-Real-IP which setup client_ip
if not host for change real/client ip all work
steveiliop56 commentedon May 23, 2026
@temperance447 what you are sharing is not an error. It's just Tinyauth informing you that it did not find a user context in the request and thus it's treating you as unauthenticated, you can ignore this error.
As for the
path.allowlabel, I cannot help you unless you share your setup. A log line is not useful if you do not share yourdocker-compose.yml(of the Tinyauth container) and the labels of the app in which ACLs are not working. Client IP is not needed for thepath.allowlabel.