-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[NOOB] Redirecting to proxy host with SSL #34
Comments
Yep it's certainly a possible improvement. I've found myself wanting this in one scenario before as well. Just need to be careful when the upstream server is another http proxy that expects the destination hostname to be supplied and that might be different from the source hostname. Some testing scenarios would need to be considered. In the meantime, if you want to hack things right now to get moving, find the specific nginx conf file in your data directory for the host you've set up, edit it and look at the
Replace that line with the following:
Save the file, then restart the docker container and it will pick up those changes. However, if you make changes to that proxy host inside Nginx Proxy Manager interface, it will overwrite your custom changes, so be careful there. |
Thanks for this workarround. What needs to be tested? Maybe I can help here! About Thanks, Aitor. |
Yeah so I was more thinking the following scenario:
NPM will resolve and find With the workaround code above, when you hit
|
I've pushed this https upstream proxy support to the |
Hi! First of all, thanks for the great explaination, you're totally right. I've tested the dev branch and worked as expected with no vhosts on real servers, or when you're asking for a domain the real server can handle with root or vhost. I can see some issues when you're asking for a domain the real server don't know and you're forwarding to an IP address, but i should test this a bit more. After all the HTTPS proxy hosts are working. Thanks! Aitor. |
Perfect. just wanted to open a feature request and then I came across this one. works perfectly, thanks a lot ! |
HTTPs upstream proxy support is a really good feature that covers a common scenario. Thanks! I hope this will be merged in an official release. |
Looking forward to this feature as well! |
Added in v2.0.7 |
Thank you very much! |
Hi,
First of all, sorry because is very possible that I misunderstood something or I'm doing something wrong.
The problem is I have some apps that runs only over SSL-enabled connections, so I need to reverse proxy to a SSL server but I can't find a way in the WebUI for this, this is the scenario:
User <----> (Signed SSL) Proxy <----> (Self-signed SSL) Server
The problem comes when in the UI I can type a server and port, but no the protocol (HTTP/HTTPS). Inside the app container, I can see in
/etc/nginx/conf.d/include/proxy.conf
the following variable filling:proxy_pass http://$server:$port;
So I think this is ready to enter only the IP and HTTP port in the WebUI, witch fills this variables in the proxy config, but in anyway this will be
http://[whatever]
The workarround for us is delete the
http://
in this file, and fill theserver
input with the protocol (http://[whatever]
orhttps://[whatever]
) in the Web UI. This workarround worked like a charm.SO
Is possible to add a dropdown just at the left of server imput field in "New Proxy Host" modal, to pick the protocol, and fill the variables in this way?
proxy_pass $protocol://$server:$port;
Many thanks,
Aitor.
The text was updated successfully, but these errors were encountered: