mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-09 23:02:59 +03:00
🐛 Bug Report: Unraid - Failed to get application configuration: connect ECONNREFUSED 127.0.0.1:8080 #394
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
I'm running into the same issue leveraging Unraid's template similar to https://github.com/stonith404/pocket-id/issues/10
What ended up being the solution here when overriding the PUBLIC_APP_URL and Ports? My unraid is only running http, but plan for everything to go thru Cloudflare to get HTTPS on my domain pointing at "pocket.mydomain.com". I'm just wanting to start up Pocket Id to get to things being setup. I'm using SWAG too if that matters, but I haven't setup any reverse proxying yet
docker run -d --name='Pocket-ID' --net='andromedanet' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Hostname" -e HOST_CONTAINERNAME="Pocket-ID" -e 'PUBLIC_APP_URL'='http://192.168.1.50:3008' -e 'DB_PATH'='data/pocket-id.db' -e 'UPLOAD_PATH'='data/uploads' -e 'PORT'='3008' -e 'BACKEND_PORT'='8089' -e 'PUID'='099' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:80]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/nwithan8/unraid_templates/master/images/pocket-id-icon.png' -p '3008:80/tcp'Expected behavior
I should see some setup instructions on Pocket Id launch page
Actual Behavior
Listening on 0.0.0.0:3008 Failed to get application configuration: connect ECONNREFUSED 127.0.0.1:8080@stonith404 commented on GitHub:
Is there a reason why you changed the backend and frontend port? I would just keep it on default.
Additionally, you need a reverse proxy because you won't be able to add a passkey if you're not using SSL.
@stonith404 commented on GitHub:
Great, thanks for sharing your solution.
@ceedubs commented on GitHub:
Thanks @ryphez I encountered a similar issue and your comment and example nginx config were really helpful!
I also think that I figured out the issue that you were encountering when using a port other than 8080 for the backend. In addition to setting
BACKEND_PORTto8089you need to setINTERNAL_BACKEND_URLtohttp://localhost:8089, because it defaults tohttp://localhost:8080. Once I made that change everything worked fine with non-standard ports.@ryphez commented on GitHub:
I have other apps on both. I was able to swap my backend port back to 8080 which seems to be fine with the frontend port being shifted.
As for HTTPS, I take it the setup needs to go thru the reverse proxy rather than accessing it via the unsecured address. Is that correct?
I setup my SWAG endpoint and it doesn't like the added NGINX parameters listed on the main page
SWAG config - note i've changed port from 3008 -> 3002.
Updated proxy.conf with the parameters for NGINX
This gets me working! Wanted to post more of these details for others who may run into this. Appreciate the help!