mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-09 14:53:00 +03:00
🐛 Bug Report: Unable to kick off Setup #395
Reference in New Issue
Block a user
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 @ryphez on GitHub.
Reproduction steps
Access pocket.domain.com/login/setup
Expected behavior
I should be able to setup Pocket Id
Actual Behavior
Leveraging Unraid, Docker build log
Even tried switching back to just port 3000 rather than 3002 which I had setup before. I've adjusted the port in SWAG as well
Pocket Id Log
@stonith404 commented on GitHub:
With "CADDY_PORT". See the README for the configuration options.
@ryphez commented on GitHub:
So my mapping in my SWAG config should point to the Caddy Port not the frontend port, correct?
@wargio commented on GitHub:
You are accessing directly the frontend instead of caddy which does the reverse proxy for the frontend (3000) & backend (8080).
@stonith404 commented on GitHub:
You're probably accessing Pocket ID on port
3000but you should use theCADDY_PORTwhich defaults to80.@ryphez commented on GitHub:
Hmm, the issue I have is SWAG (nginx) already runs on port 80. Nothing in the Unraid template exposes port 80, only port 3000.
Is there a way to adjust the Caddy port?
@cdanis commented on GitHub:
Expose just the Caddy port. Ignore the 'frontend port' -- only Caddy should talk to that directly. And never export two different pod ports onto one host port as you've done :)
SWAG should talk only to Caddy, which wraps both the frontend and backend.
@ryphez commented on GitHub:
I've adjusted to the ports to map how it seems like they should yet still get the error. I'm not sure what could be causing it. The page loads with SWAG pointed at 8183.
CADDY_PORT = 8183
Front End = 3000
Back End = 8080
Expose 3000 -> 8183
Expose 8183 -> 8183
Docker Build Command
Error
SWAG Config
@cdanis commented on GitHub:
Correct. The Caddy port is the entry point for the app
On Mon, Jan 20, 2025 at 5:59 PM ryphez @.***> wrote:
@ryphez commented on GitHub:
Okay, I've adjsuted to remove the other exposing and only kept
8183 -> 80
I reverted the caddy port change given its an internal port and wouldn't conflict.
I still get the same setup error though accessing "https://pocket.domain.com/login/setup"
error
Here is my latest docker deploy
@wargio commented on GitHub:
you are still accessing the frontend. if you really want to not use caddy (like i do) and just Nginx, you can do this:
on docker you need to define
HOST=0.0.0.0env variable (because by default the backend binds to127.0.0.1) and expose the two ports internally (you can avoid changing all the other env vars besides thePUBLIC_APP_URLwhich is required):127.0.0.1:12673:3000pocket-id frontend127.0.0.1:12674:8080pocket-id backendThen on nginx just set this