This repository was archived by the owner on Feb 16, 2023. It is now read-only.
502 Bad Gateway after update 1.4.4 to 1.5.0 #1331
Unanswered
Burschi500
asked this question in
Support
Replies: 1 comment 3 replies
-
Hi Burschi Error 502/503 Bad Gateway usually appears only on the proxy itself who can't reach its backend. Does the process itself run and do you have any logfiles in your paperless directory? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Good morning,
after updating to 1.5.0 (bare metal) and copying over the paperless.conf and adjusting ownership i get a 502 when accessing paperless. I use nginx as proxy, but only for internal use.
What did i do wrong during updating?
Beta Was this translation helpful? Give feedback.
All reactions