Need help with a frustrating SSL cert problem.
retained text
Okay, some background first. Here's the part of my stack in question, everything is on my local network: * Gitlab running in a docker container, and gitlab-runner in a docker container, both in the same VM. * Nginx proxy manager in a docker container, in it's own VM. It's grabbing certs from letsEncrypt, and applying them to my domain. * Pihole in it's own VM as my local DNS, with openDNS as it's upstream source (This may or may not be relevant later) **This has been working great for several years.** Here's what I've been through and the errors I've been running into: The whole SSL drama from earlier in the week prompted me to grab new SSL certs via nvinx proxy manager. This worked as expected. Yesterday, I pushed some changes to a repo and kicked off the build process. It failed immediately with the following error: `fatal: unable to access '<gitlab_repo_url_redacted>': SSL certificate OpenSSL verify result: unable to get local issuer certificate (20)` I assumed there was maybe something cached from earlier in the week, and new certs weren't being grabbed. I then hit refresh in firefox, and it gave me an SSL error: `SEC_ERROR_UNKNOWN_ISSUER` I inspected the certificate, and it said it was issued by openDNS, which seemed pretty odd to me. Why wasn't it issued by letsEncrypt? Okay, maybe something went wrong, so I went back to nginx proxy manager and pulled a new certificate. Gave it a little while to do its thing and propagate, then cleared cookies and cache in firefox and refreshed the page, and it loaded fine. Inspected the cert, and it was issued by letsEncrypt as expected. Okay, try build process again, and it failed with the same error. Tried restarting the VM to clear cache, and still same error. Start googling, and ended up finding that the docker container might be getting its certs from the host VM, so I tried forcing the VM to grab new certs by manually deleting everything in `/usr/share/ca-certificates` and `/etc/ssl/certs` and running `update-ca-certificates.` After confirming they were all new, I restarted the VM again for good measure, and the build process still threw the same error. At this point I gave up and assumed something was cached that I couldn't find, and slept on it. This morning, tried running the build process again, and still same error. I've run out of ideas, any help would be greatly appreciated.
document fetched 2026-10-26 00:28 · canonical https://reddit.com/r/selfhosted/comments/1xf7ebp/need_help_with_a_frustrating_ssl_cert_problem