[GH-ISSUE #756] Timed out when activating Let's Encrypt SSL - No SSL proxy works fine #640

New issue

Closed

opened 2026-02-26 06:33:48 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:33:48 +03:00

Owner

Originally created by @v9999 on GitHub (Dec 3, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/756

Checklist
app image: jc21/nginx-proxy-manager:latest
db image: yobasystems/alpine-mariadb
vps: ubuntu 18.04 running o Oracle Cloud (VM.Standard.E2.1.Micro) x86_64
domain solving: duckdns
docker: docker and docker-compose latest versions.

Describe the bug
First of all, beautiful work on the project. Thanks a lot for the effort!

So, my problem is simple.
My proxy hosts are working normally without SSL, but if I add the inbuilt let'sencrypt SSL, the reverse proxy breaks, I begin to get timed outs and can't reach my services. I tried it with wordpress, portainer and bazarr.

If I disable the SSL, I can reach the servers just fine.

To Reproduce

One simple example with bazarr:
Here's my docker-compose:

version: '3'
services:
app:
image: jc21/nginx-proxy-manager:latest
ports:
- 80:80
- 81:81
- 443:443
environment:
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
db:
image: yobasystems/alpine-mariadb
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
volumes:
- ./data/mysql:/var/lib/mysql

bazarr:
image: ghcr.io/linuxserver/bazarr
container_name: bazarr
volumes:
- ./bazarr/config:/config
- ./movies:/movies
- ./tv:/tv
ports:
- 6767:6767
restart: unless-stopped

Ok, now we have npm working fine, which I can access with the server public ip.
Now, I set a duckdns domain to get to the server public ip.
On npm, I add a proxy host for that domain in duckdns that points to 10.0.0.3:6767 (bazarr on private ip for these oracle vps's). No SSL yet.
Accessing the duckdns link, I get to my bazarr instance.
Now that it works, I'll go back to npm and add SSL to this proxy host. Let's encrypt finish its setup normally.
Now I try to access the duckdns link and get timed out. Multiple browsers, refresh, private tab etc. doesn't fix it.

Expected behavior
The SSL for the proxy host should work.

Originally created by @v9999 on GitHub (Dec 3, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/756 **Checklist** app image: jc21/nginx-proxy-manager:latest db image: yobasystems/alpine-mariadb vps: ubuntu 18.04 running o Oracle Cloud (VM.Standard.E2.1.Micro) x86_64 domain solving: duckdns docker: docker and docker-compose latest versions. **Describe the bug** First of all, beautiful work on the project. Thanks a lot for the effort! So, my problem is simple. My proxy hosts are working normally without SSL, but if I add the inbuilt let'sencrypt SSL, the reverse proxy breaks, I begin to get timed outs and can't reach my services. I tried it with wordpress, portainer and bazarr. If I disable the SSL, I can reach the servers just fine. **To Reproduce** 1. One simple example with bazarr: 2. Here's my docker-compose: > version: '3' > services: > app: > image: jc21/nginx-proxy-manager:latest > ports: > - 80:80 > - 81:81 > - 443:443 > environment: > DB_MYSQL_HOST: "db" > DB_MYSQL_PORT: 3306 > DB_MYSQL_USER: "npm" > DB_MYSQL_PASSWORD: "npm" > DB_MYSQL_NAME: "npm" > volumes: > - ./data:/data > - ./letsencrypt:/etc/letsencrypt > db: > image: yobasystems/alpine-mariadb > environment: > MYSQL_ROOT_PASSWORD: 'npm' > MYSQL_DATABASE: 'npm' > MYSQL_USER: 'npm' > MYSQL_PASSWORD: 'npm' > volumes: > - ./data/mysql:/var/lib/mysql > > bazarr: > image: ghcr.io/linuxserver/bazarr > container_name: bazarr > volumes: > - ./bazarr/config:/config > - ./movies:/movies > - ./tv:/tv > ports: > - 6767:6767 > restart: unless-stopped 3. Ok, now we have npm working fine, which I can access with the server public ip. 4. Now, I set a duckdns domain to get to the server public ip. 5. On npm, I add a proxy host for that domain in duckdns that points to 10.0.0.3:6767 (bazarr on private ip for these oracle vps's). No SSL yet. 6. Accessing the duckdns link, I get to my bazarr instance. 7. Now that it works, I'll go back to npm and add SSL to this proxy host. Let's encrypt finish its setup normally. 8. Now I try to access the duckdns link and get timed out. Multiple browsers, refresh, private tab etc. doesn't fix it. **Expected behavior** The SSL for the proxy host should work.

kerem

2026-02-26 06:33:48 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:33:48 +03:00

Author

Owner

@v9999 commented on GitHub (Dec 3, 2020):

I'll post again under support.

@v9999 commented on GitHub (Dec 3, 2020): I'll post again under support.

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#640

No description provided.

Rows
Columns