-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
nginx reverse proxy with subpath documentation not valid nginx syntax #15931
Comments
http://domain.com/git/
(running nginx/1.16.1 and Gitea version 1.8.3+2-g11f6ed4f8 built with go1.12.6 : bindata, sqlite, sqlite_unlock_notify):
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
The docs as of today already have this trailing slash added. |
sounds like this fixed then. |
This is what works for me for
http://domain.com/git/
(running nginx/1.16.1 and Gitea version 1.8.3+2-g11f6ed4f8 built with go1.12.6 : bindata, sqlite, sqlite_unlock_notify):Without the trailing slash on proxy_pass everything was 404.
Originally posted by @defulmere in #8635 (comment)
when using the above in an nginx config, nginx gives me the following error:
nginx: [emerg] "proxy_pass" cannot have URI part in location given by regular expression, or inside named location, or inside "if" statement, or inside "limit_except" block in /etc/nginx/locations/venberg.xyz_sites/gitea:2
using @donpdonp 's inital solution worked perfectly.
only issue now is that mydomain.xyz/git/ works, but mydomain.xyz/git (without trailing space) gives a 404 error.
The text was updated successfully, but these errors were encountered: