Certificate issues via Pangolin

ℹ️ Support
, , , , , ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32.0.3 freshly installed AIO yesterday
  • Operating system and version (e.g., Ubuntu 24.04):
    • Windows via Docker
  • Web server and version (e.g, Apache 2.4.25):
    • What came with 32.0.3
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Pangolin, see text
  • Is this the first time you’ve seen this error? (Yes / No):
    • yes
  • When did this problem seem to first start?
    • today, fresh setup
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • docker run

Summary of the issue you are facing:

Connecting through Pangolin gives me: net::ERR_CERT_AUTHORITY_INVALID.

I reinstalled NC yesterday because I was running into some issues I couldn’t fix otherwise.
I was only able to reinstall it by opening ports 80/443 on the host and setting up a reverse proxy, otherwise the AIO installation wouldn’t continue since a cert couldn’t be retrieved. Meaining: i was unable to install it through Pangolin.

At this point I have to add: bare with me, I’m a newbie :slight_smile:

Now, I’d like to add that NC runs flawlessly either through Caddy + opened ports or through the Cloudflare tunnels. I’d prefer Pangolin, however.

Pangolin can connect to the local resource on 192.168.0.52:11000 just fine. But when I try to connect to it, it gives me the ERR_CERT_AUTHORITY_INVALID, possibly because both the local install and Pangolin have retreived a LetsEncrypt cert that doesn’t match?

I installed NC with this run command under windows:

docker run ^
–init ^
–sig-proxy=false ^
–name nextcloud-aio-mastercontainer ^
–restart always ^
–publish 8080:8080 ^
–publish 8443:8443 ^
-e APACHE_PORT=11000 ^
-e APACHE_IP_BINDING=0.0.0.0 ^
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config ^
–volume //var/run/docker.sock:/var/run/docker.sock:ro ^
-e NEXTCLOUD_DATADIR=“/run/desktop/mnt/host/d/Nextcloud” ^

Steps to replicate it (hint: details matter!):

  1. I installed NC with the run command above

  2. Fire up caddy, open ports 80 and 443 and go through the AIO installation pretty much with default settings.

  3. Login to cloud.xyz.com as provided during the install, which fails

I’ll add more details if I can. Right now it’s working through CF and I need to upload my files before I revert back for tinkering…

Any help appreciated