-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
SSL passthrough hosts #1479
base: develop
Are you sure you want to change the base?
SSL passthrough hosts #1479
Conversation
The build fails due to some timeout waiting for the sqlite integration check container to be spun up. But as this relies on a docker image built in the ci, I cannot replicate it locally to see why it is not working. @jc21 |
When this kind of this happens in CI you can view the artifacts for more info. The error for sqlite is:
|
cf09468
to
4b60d58
Compare
4b60d58
to
70163a6
Compare
This is an automated message from CI: Docker Image for build 10 is available on DockerHub as Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes. |
Finally got the migration working, SQLite has more quirks which are not handled by knex than I thought. |
This is an automated message from CI: Docker Image for build 11 is available on DockerHub as Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes. |
This pr also needs rebasing on |
This is an automated message from CI: Docker Image for build 12 is available on DockerHub as Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes. |
This is an automated message from CI: Docker Image for build 13 is available on DockerHub as Note: ensure you backup your NPM instance before testing this PR image! Especially if this PR contains database changes. |
@chaptergy Just a reminder this PR needs a rebase. I'm really invested in it, so I am hoping it can get merged. |
Hi, any update? |
I would also love to hear some news on this topic. Nginx Proxy Manager is a great tool and actually right now this feature is the only one I am missing so far. Nice work so far, but can you give us some hints about this feature. Is it still planned to be released an is there probably already a schedule when we can expect a release? |
Same here - I am really looking forward to this. Getting SSL Passthrough working would allow me to more easily migrate onto this, given that part of my environment includes a setup with an existing Letsencrypt key that I must keep operational (that needs to standalone). |
This would be very helpful for apps that want to terminate their own SSL. |
PR is now considered stale. If you want to keep it open, please comment 👍 |
What is missing to get this merged? |
This PR would resolve #853.
SSL passthrough would be a new type of host where the ssl certificate of the upstream server is used, so no ssl termination is done at the proxy. But the only way this is possible in nginx is streams, using SNI to forward the packet to the right destination. As a stream and the normal proxies using http cannot be on the same port, all https traffic has to go through the stream, which then could forward it internally to the http proxy. As this reduces performance for all hosts, this feature is strictly opt-in. The documentation was updated to add a section about this to the advanced config page.