8000 nginx-proxy ssl · Issue #24 · odoocker/odoocker · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

nginx-proxy ssl #24

New issue
8000

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Open
Edions1 opened this issue Jul 5, 2024 · 5 comments
Open

nginx-proxy ssl #24

Edions1 opened this issue Jul 5, 2024 · 5 comments
Assignees
@yhaelopez

Comments

@Edions1
Copy link
Edions1 commented Jul 5, 2024

Hello, firstly! gratitude to the administrators for the content made available. I'm having a lot of difficulty pointing my self-signed certificate to nginx-proxy. I can't tell if it's the note or the structure of the certificate
@Edions1
Copy link
Author
Edions1 commented Jul 5, 2024

2024/07/04 21:25:46 Contents of /etc/nginx/conf.d/default.conf did not change. Skipping notification 'nginx -s reload'

*273 cannot load certificate "data:": PEM_read_bio_X509_AUX() failed (SSL: error:0480006C:PEM routines::no start line:Expecting: TRUSTED CERTIFICATE) while SSL handshaking, client: 192.xxxxx, server: 0.0.0.0:443

@yhaelopez
Copy link
Contributor
yhaelopez commented Jul 16, 2024 •
edited
Loading

Hi, @Edions1.
I appreciate your words! And thanks for contributing with this issue

We currently don't support self-signed certs. We are heading to change the current setup from nginx, nginx-proxy and acme-companion, which are 3 nginx containers by themselves, to a single nginx option (nginx-proxy-manager). Or, if preferred, use Traefik.

However, it is still need some time to get developed.
I highly recommend you use a small AWS EC2 instance to test the certificates in a real server with the current setup.

@yhaelopez yhaelopez self-assigned this Jul 16, 2024
@Edions1
Copy link
Author
Edions1 commented Jul 17, 2024

@yhaelopez thank you for your speed in responding, when possible I am available to contribute to the project

@pxeio
Copy link
pxeio commented Aug 29, 2024 •
edited
Loading

launched_nginx-proxy_1 | nginx.1 | 2024/08/29 03:04:59 [error] 28#28: *11 cannot load certificate "data:": PEM_read_bio_X509_AUX() failed (SSL: error:0480006C:PEM routines::no start line:Expecting: TRUSTED CERTIFICATE) while SSL handshaking, client: x.x.x.x, server: 0.0.0.0:443
Should be using letsencrypt, right?

Replaced my IP with x.x.x.x

I'm getting similar error.

@pxeio
Copy link
pxeio commented Aug 29, 2024

my bad, I added acme to SERVICE. The readme could be improved as far as updating the production letsencrypt endpoint under the ACME_CA_URI. It's a little confusing and for a moment I thought I was supposed to add ACME_CA_URI to SERVICE in .env. Thank you for your work on this repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yhaelopez yhaelopez

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yhaelopez @pxeio @Edions1
0