The Basics
- Nextcloud Server version (e.g., 29.x.x):
34.04? (the site is currently inaccessible so that's the best I recall)
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 24.04
- Web server and version (e.g, Apache 2.4.25):
Whatever that Snap version is using
- Reverse proxy and version _(e.g. nginx 1.27.2)
Nginx 1.24.0
- PHP version (e.g, 8.3):
Whatever that Snap version is using
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
yesterday evening
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Snap on VPS, with Nginx added via apt later
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
Previously working reverse proxy of Snap behind Nginx stopped working two days after I last used it, with no direct intervention on my part.
Steps to replicate it (hint: details matter!):
-
I used this tutorial to set things up:
Tutorial: Nextcloud snap with other services on the same server -
I enjoyed using it for a couple weeks.
-
Attempting to log in now fails due to a cert error, but interestingly different depending on the browser:
In Firefox macOS 157.0: "Unable to communicate securely with peer: requested domain name does not match the server’s certificate. HTTP Strict Transport Security: false HTTP Public Key Pinning: false:
In Chrome macOS 154.0.8037.58: “net::ERR_CERT_COMMON_NAME_INVALID”
It gets odder. Here’s the setup: The VPS has Nginx with a block pointing to what we can call subDomainA.domain.com, and a Nextcloud Snap container accessed via subDomainB.domain.com.
The Firefox error reports that the cert that doesn’t check out is from subDomainB, while Chrome reports getting the cert for subDomainA.
I have a reasonable level of experience with small server admin, but not with the details of cert management or managing them with a reverse proxy.
Any guidance on next steps to diagnose or resolve welcome. Thank you for your time reading this.
