Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

All https except two URLs? #335

Closed
asmaloney opened this issue Jan 16, 2016 · 5 comments
Closed

All https except two URLs? #335

asmaloney opened this issue Jan 16, 2016 · 5 comments

Comments

@asmaloney
Copy link

I'm using this in combination with docker-letsencrypt-nginx-proxy-companion to use Let's Encrypt SSL certs and it's working great. Easy to set up and get going.

I have a couple of URLs that have to remain http though. They are hard-coded into some software that can't be changed.

I've been looking at the nginx config docs and the nginx.tmpl file, but I don't see a way to do this. The listen 80 block send everything to https so there's no opportunity to deal with the URLs I want.

Am I reading that correctly? Is there some nginx magic I can use in one of the vhosts files included in the ssl server block to make this work?

@kevinsimper
Copy link

I think you should use the solution where you provide your own template to docker-gen 👍

@asmaloney
Copy link
Author

Thanks Kevin. I'll take a look. I was hoping to get away with not having to modify the template somehow...

@kevinsimper
Copy link

@asmaloney I understand, but it is fairly straigtforward! Remove that line for the config and the mount that into the container instead, and then it works perfect for you! 😄

@asmaloney
Copy link
Author

@kevinsimper It's not about how easy it is to make it work - it's about having Yet Another Thing to maintain.

Once I modify that template I have to monitor changes to the nginx-proxy version and apply them to mine. That doesn't sound so bad, but I already have 1001 other things to keep track of (and I don't do ops full time), so if I can figure out a way to use it as is, I'd prefer to do that.

@kevinsimper
Copy link

i think your problem is too specific for this project to support your case, especial when the solution is so easy for you to archive.

Alexander-Krause-Glau pushed a commit to Alexander-Krause-Glau/rpi-docker-nginx-proxy that referenced this issue Mar 31, 2018
@tkw1536 tkw1536 converted this issue into discussion #1950 Apr 10, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants