-
-
Notifications
You must be signed in to change notification settings - Fork 325
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
[Bug] Some browsers do not work properly when running behind nginx reverse proxy #384
Comments
What do your browser logs say? |
I have this running behind Nginx Proxy Manager and its working as expected on Safari (iPhone 16), Chrome and Brave (MacBook). My compose file is as follows:
Compare this to yours and/or post it here. |
edge log
docker-compose.yml
Connections from local addresses that do not pass nginx work fine |
We don’t use bootstrap so this seems to be from some browser plugin. Try to load the page without plugins or with another browser and see if that works. Also, be sure to load the page in a private tab to ensure there is no problem with logs. If Firefox works but everything else does not, this hints to a problem with your browsers as well. There have been some fixes on PairDrop v1.11.1. Consider updating the container and retrying.
Apart from that your setup looks fine. Do the docker container logs contain errors? |
I updated it to 1.11.1 and setting |
Some browsers do not work properly when running behind nginx reverse proxy
In my environment it works fine only with firefox
I open the page but the name still loads and the button on the top right cannot be opened except for the theme and information.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Bug occurs on official PairDrop instance https://pairdrop.net/
No
Version: v1.11.0
Bug occurs on self-hosted PairDrop instance
Yes
Self-Hosted Setup
Proxy: Nginx
Deployment: docker compose
Version: v1.11.0
Additional context
The nginx .conf looks like this
The text was updated successfully, but these errors were encountered: