[GH-ISSUE #64] RPI issues #61

Closed
opened 2026-02-26 05:34:01 +03:00 by kerem · 2 comments
Owner

Originally created by @burnacid on GitHub (Feb 3, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/64

I'm having a lot of issues with getting SSL to work.
I'm running nginx proxy manager on a Raspberry Pi 3+
Normal HTTP proxies work like a charm. But fail when I try to setup any to SSL.

On requesting a LetsEncrypt certificate I get a popup message saying "Timeout"
On refresh the certificate is there. But when I link it to one of the proxies the proxy stays offline and doesn't work at all.

I've generated a LetEncrypt wildcard certificate. Tried to upload that. But again failed with the message 400 upload failed.

What am I missing? I love the way nginx proxy manager lets me setup reverse proxies. Great tool keep up the work man.

Originally created by @burnacid on GitHub (Feb 3, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/64 I'm having a lot of issues with getting SSL to work. I'm running nginx proxy manager on a Raspberry Pi 3+ Normal HTTP proxies work like a charm. But fail when I try to setup any to SSL. On requesting a LetsEncrypt certificate I get a popup message saying "Timeout" On refresh the certificate is there. But when I link it to one of the proxies the proxy stays offline and doesn't work at all. I've generated a LetEncrypt wildcard certificate. Tried to upload that. But again failed with the message 400 upload failed. What am I missing? I love the way nginx proxy manager lets me setup reverse proxies. Great tool keep up the work man.
kerem closed this issue 2026-02-26 05:34:01 +03:00
Author
Owner

@burnacid commented on GitHub (Feb 3, 2019):

Console shows

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for hostname.hidden
Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. hostname.hidden (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://hostname.hidden/.well-known/acme-challenge/A23xVKQEHS1xF6MTGimwA2A2w3-Z5IsPUJ2vjlDCO0k: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p"
<!-- gh-comment-id:460030865 --> @burnacid commented on GitHub (Feb 3, 2019): Console shows ``` Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for hostname.hidden Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains. Waiting for verification... Cleaning up challenges Failed authorization procedure. hostname.hidden (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://hostname.hidden/.well-known/acme-challenge/A23xVKQEHS1xF6MTGimwA2A2w3-Z5IsPUJ2vjlDCO0k: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>404 Not Found</title>\n</head><body>\n<h1>Not Found</h1>\n<p" ```
Author
Owner

@burnacid commented on GitHub (Feb 3, 2019):

Never mind. The issues was ownership of the data and letsencrypt folders.
Fixed it with
sudo chown -R pi:docker /opt/nginx-proxy/*

<!-- gh-comment-id:460048657 --> @burnacid commented on GitHub (Feb 3, 2019): Never mind. The issues was ownership of the data and letsencrypt folders. Fixed it with `sudo chown -R pi:docker /opt/nginx-proxy/*`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#61
No description provided.