Skip to content
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

Issue with recent container update and SSL #1226

Open
samara8609 opened this Issue Jan 30, 2019 · 10 comments

Comments

Projects
None yet
10 participants
@samara8609
Copy link

commented Jan 30, 2019

I'm seeing the below error when recently updating the container (within the last 24-48 hours)

nginx.1 | 2019/01/30 02:25:16 [emerg] 33#33: PEM_read_bio_DHparams("/etc/nginx/dhparam/dhparam.pem") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: DH PARAMETERS)
nginx.1 | nginx: [emerg] PEM_read_bio_DHparams("/etc/nginx/dhparam/dhparam.pem") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: DH PARAMETERS)

Nothing in my compose has changed in the last few weeks, i'm not sure whats causing this to break now. I've gone thru and deleted the configs and let it try to recreate them with the same issue. Attached is the compose i'm using.
nginx-sample.txt

@pauldalewilliams

This comment has been minimized.

Copy link

commented Jan 30, 2019

I'm not sure if/how it may be related, but I had the same issue and upon digging into it came across this: #955

I ended up changing that line in my default.conf to point to the certs directory instead of dhparam since that's where my dhparam file exists. (I'm using the letsencrypt companion container.) Once I did that, everything was back to normal. Not sure why it was only triggered with this newest image though.

My previous comment was just a temporary fix. I needed to map a volume for /etc/nginx/dhparam to fix this. Not sure how I missed this on the one instance of several I have using this setup, but that was the fix (I had mapped it on the others...). I'm using the letsencrypt companion - not sure why the newer nginx-proxy image was having a problem but what I saw was that it was not remounting the volume it had originally stored the dhparam.pem file in. Instead, it was creating a new volume, putting a blank dhparam.pem file in /etc/nginx/dhparam, and that's what prevented nginx from starting. I think this PR will fix that problem of the blank file: #1213

I was able to fix this fairly easily in my case by creating a named volume and copying over the dhparam.pem file to that so I wouldn't have to wait for a new one to generate.

@alaincao

This comment has been minimized.

Copy link

commented Jan 30, 2019

Hello, just to add my 2cents,
this problem seem to appear only in image "jwilder/nginx-proxy:latest" but not in "jwilder/nginx-proxy:alpine"

@flayks

This comment has been minimized.

Copy link

commented Jan 31, 2019

Same problem, it broke my nginx docker setup after the update :/

@jakejarvis

This comment has been minimized.

Copy link

commented Jan 31, 2019

Switching to Alpine is the only way I could get back up and running too. Seems to be behaving exactly the same as the Debian version though (as it should!) so if you need to get back up ASAP then that's the image I'd recommend pulling in the meantime.

@flayks

This comment has been minimized.

Copy link

commented Jan 31, 2019

I removed my old empty dhparam.pem I had and as other suggested before I used the alpine version of nginx-proxy, seems to get my sites back online. But this sounds definitely like a bug!

@rickygarg

This comment has been minimized.

Copy link

commented Jan 31, 2019

+1 I can't get alpine to run as well - maybe because alpine is updated too: could get the alpine to run as well. https://hub.docker.com/r/jwilder/nginx-proxy/builds

Are there dockerhub digest id's anywhere so an older build can be pulled meanwhile?

@Jules-Baratoux

This comment has been minimized.

Copy link

commented Mar 26, 2019

Same issue. I could get jwilder/nginx-proxy:0.6.0 to work :)

@JoshGlazebrook

This comment has been minimized.

Copy link

commented Mar 30, 2019

Still having this issue.

@maxguru

This comment has been minimized.

Copy link

commented Apr 1, 2019

Current version is still broken. 👎

@coderdiaz

This comment has been minimized.

Copy link

commented Apr 4, 2019

The latest version isn't work!

@Code-Bear Code-Bear referenced this issue Apr 12, 2019

Open

Site down after updating to v4.0.12 #1410

4 of 4 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.