-
I'm using the docker-compose version of paperless-ng and have it up and running and can access it locally through my LAN. However, when trying to access it through SWAG, I get a 502 error bad gateway. I'm fairly certain it's my swag configuration for paperless-ng but I don't know what I'm doing wrong. Here is my conf from SWAG.
Here is my docker compose for paperless-ng. I didn't include redis in this because I already have redis up and running for something else.
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Are you running SWAG inside a container and is it part of the network 'lsio' ?
If it is not running inside a container, you would need to reference to localhost or 127.0.0.1 inside your swag config. |
Beta Was this translation helpful? Give feedback.
-
the network could be a thing i use or maybe PAPERLESS_CORS_ALLOWED_HOSTS or PAPERLESS_ALLOWED_HOSTS env vars are set or set wrong! Check your ports, as TobeanderZyphr said below. Inside container network you use the original port not the exposed one. Eg.: 8000 for paperless |
Beta Was this translation helpful? Give feedback.
-
the lsio network has 'external' on it but you're right, I SWAG was using port 8010. After switching it back to 8000 and changing it under healthcheck as well and rebooting both containers, I'm able to access paperless-ng externally now. Thank you both! |
Beta Was this translation helpful? Give feedback.
the network could be a thing i use
network_mode: lsio
if it is a single networkor maybe PAPERLESS_CORS_ALLOWED_HOSTS or PAPERLESS_ALLOWED_HOSTS env vars are set or set wrong!
Check your ports, as TobeanderZyphr said below. Inside container network you use the original port not the exposed one. Eg.: 8000 for paperless
edits: deleted wrong stuff.