-
-
Notifications
You must be signed in to change notification settings - Fork 153
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 Report] nginx reverse proxy. Bad Gateway: undefined #592
Comments
getting this as well. |
I'm also experiencing this issue on |
Have you all looked at http://dev.yacht.sh/docs/Advanced/Proxy I went through and reworked the documentation website, There are old documents on the yacht.sh site, please use the subdomain of dev.yacht.sh, also There is a new version coming out sometime at the end of the year. The main site is not going to be updated until the new version is released. The dev.yacht.sh will remain the temp location for the most current documents. Also, try pulling with selfhosted/yacht:devel image; it had lots of fixes applied to it that other images have not. These directions are my current setup with a docker host running Debian in AWS with Nginx proxy manager/reverse proxy as a container hosted there as well. It works and passes yacht through just like any other website it's hosting. |
Describe the bug
When I revere proxy using nginx proxy manager I get
Bad Gateway: undefined
in a red bar at the bottom.To Reproduce
Steps to reproduce the behavior:
docker run -d --network nginx-net -p 8000:8000 -v /var/run/docker.sock:/var/run/docker.sock -v yacht:/config selfhostedpro/yacht
Bad Gateway: undefined
Expected behavior
Yacht loads like it does when going to 192.168.1.179:8000
Screenshots
![image](https://private-user-images.githubusercontent.com/53239525/241445602-badfb277-5bb8-4300-923f-1abf16f9b818.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg0Mjg2MzQsIm5iZiI6MTcxODQyODMzNCwicGF0aCI6Ii81MzIzOTUyNS8yNDE0NDU2MDItYmFkZmIyNzctNWJiOC00MzAwLTkyM2YtMWFiZjE2ZjliODE4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE1VDA1MTIxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWFkZGE1YzUyZTFhMjZhMzJjNjQ0YjdkM2Q2YWMxMzQxMmYzYjk0YTA3OTkwOGVmMWI1ZGI2M2RhNmEwZDNmMmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.hidgo1M1ahnLO5xrqiAGqJTFvXFwDNuppQbG4FCDKL4)
![image](https://private-user-images.githubusercontent.com/53239525/241445675-285ccd95-6fba-4d82-a032-0d32712c89f1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg0Mjg2MzQsIm5iZiI6MTcxODQyODMzNCwicGF0aCI6Ii81MzIzOTUyNS8yNDE0NDU2NzUtMjg1Y2NkOTUtNmZiYS00ZDgyLWEwMzItMGQzMjcxMmM4OWYxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTUlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE1VDA1MTIxNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE2YmM2NmQ2ZTg3Nzg4MmYxYzczOGQwODEyYTNmNWUyYTBmOTExYWJlMjM0MjE0MDFkODcwOGFlMjg4ZWZmODEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.t3eTD02huaiLjMYDnhMIPwYvNzgiQHX_Bkl93DuoYiU)
Desktop (please complete the following information):
Additional context
It worked when my network was
bridge
and I used cloudflare tunnel as a reverse proxy** Logs **
The text was updated successfully, but these errors were encountered: