-
-
Notifications
You must be signed in to change notification settings - Fork 127
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] Unable to use external nginx reverse proxy #458
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
We do not provide support for reverse proxies other than our own. I believe nextcloud has documentation on how to properly reverse proxy this application. You are welcome to look in our reverse proxy confs https://github.com/linuxserver/reverse-proxy-confs/blob/master/nextcloud.subdomain.conf.sample, note that you'll also need to check the includes within swag, to determine how we handle this. closing as out of scope. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
I use linuxserver/docker-nextcloud image in my Unraid. I also use nginx on my Ubuntu server, which opened port 9443. I want to access nginx from the outside through port 9443, and then proxy access to nextcloud, but nginx always lost my port number.
Expected Behavior
Nginx doesn't lost my port number.
Steps To Reproduce
Access my domain to my nextcloud
Environment
CPU architecture
x86-64
Docker creation
Container logs
What configuration do I need to modify?
The text was updated successfully, but these errors were encountered: