Skip to content
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

Open
Commiccannon opened this issue Jan 7, 2025 · 4 comments
Open

Reverse proxy issue #825

Commiccannon opened this issue Jan 7, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@Commiccannon
Copy link

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

  • Part-DB Version: 1.15.0
  • PHP Version: 8.3.15
  • Database Server sqlite 3.40.1

Desktop (please complete the following information):

  • Issue with every browser tired (chrome and edge) and both phone and PC
@Commiccannon Commiccannon added the bug Something isn't working label Jan 7, 2025
@jbtronics
Copy link
Member

Is Part-DB even running properly? Does it show something in its error logs?
A timeout sounds more like Part-DB cannot be reached at all.

@Commiccannon
Copy link
Author

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

@jbtronics
Copy link
Member

How does your reverse proxy config look like?
Can your reverse proxy really reach part-DB? Does DNS resolving works?

I would expect that this is not really a Part-DB issue, but a an communication error between the reverse proxy and Part-DB.

@Commiccannon
Copy link
Author

Commiccannon commented Jan 8, 2025

partdb.subdomain.conf.txt

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants