-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reverse proxy issue #825
Comments
Is Part-DB even running properly? Does it show something in its error logs? |
Partdb is running fine, I can access locally with no issues. The logs show no errors and no activity when I try and access externally |
How does your reverse proxy config look like? I would expect that this is not really a Part-DB issue, but a an communication error between the reverse proxy and Part-DB. |
Ive attached my reverse proxy config file, its a SWAG file so dosnt normally have the .txt as well Every device ive tried on my network can reach partdb and im having no issues with any other server under this reverse proxy. I posted this issue becuase it happened as soon as i upgraded partdb. Have there been any changes to how the proxy needs to be set up at all? |
Describe the bug
Reverse proxy was working untill i upgraded to 1.15. Same config now im getting a ERR_TIMED_OUT error, other services under the same reverse proxy are working fine
To Reproduce
Upgrade from 1.14 to 1.15.
Run a NGINX proxy under swag on same machine (10.0.0.21)
Have this in the docker-compose.yaml TRUSTED_PROXIES=127.0.0.1,127.0.0.0/8,::1,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16
Expected behavior
No change to proxy config during update, server responds as it was
Server Side
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: