Open AryehGielchinsky opened 14 hours ago
Make sure the SSL certificates for Nextcloud and Immich are configured correctly and match the subdomains they use. You can check the SSL certificate settings in the NPM management interface. In addition, you can also consider replacing docker with a tool such as servbay, which is very suitable for your needs. servbay has comprehensive SSL certificate automatic configuration functions
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
I've got NPM setup with Docker Compose. I have it pointing to other docker containers on the same host with a shared docker network. For a long time everything worked fine, but recently I've been getting SSL errors for Nextcloud and Immich, while Jellyfin and Gitea work fine. Nextcloud and Immich get SSL_ERROR_UNRECOGNIZED_NAME_ALERT
The weird thing is if I load Jellyfin or Gitea and then Nextcloud or Immich, Nextcloud or Immich will work for for a bit. I checked wireshark, and it looks like Nextcloud and Immich try and fail with TLS 1.2, while Gitea and Jellyfin use TLS 1.3 and succeed.
Here is my compose:
Everything is on the same domain. I use sub domains to distinguish between services.
Nextcloud Nginx custom config
Immich Nginx custom config
client_max_body_size 50000M;
Jellyfin and Gitea don't have Nginx custom Configs.
Nginx Proxy Manager Version
v2.11.3
To Reproduce Steps to reproduce the behavior:
Expected behavior
No SSL error.
Screenshots
Operating System
Server: Ubuntu Server 22.04 Desktop: Ubuntu Desktop 22.04
Additional context
Docker version 27.3.1, build ce12230 Firefox 131.0.2 (64-bit) (deb version)