Nextcloud Subdomain Cert No Longer Valid
I have a linode running Nextcloud AIO from the marketplace. At setup, I used a domain purchased through namecheap but which is controlled in the Linode Domains. After setup, I could successfully access nextcloud through the subdomain, for example sub.domain.com, of my domain domain.com. The SSL cert for the domain is autoupdating and showing as valid when I access the AIO interface, but the subdomain is not. How do I get a valid cert for this subdomain? I did everything through the marketplace set up and have made no changes to the domains or networking since.
3 Replies
tlambert
Linode Staff
The Nextcloud AIO Marketplace Application deploys the nginx-proxy and docker-letsencrypt-nginx-proxy-companion containers. According to their documentation, renewal should be automatic.
If your TLS cert is not being renewed automatically, I suggest reading through the docker-letsencrypt-nginx-proxy-companion troubleshooting information or opening up an issue on the GitHub repo.
The certificate for the domain is being automatically updated, but the subdomain I set up during deployment to use to access Nextcloud is not. I will look over the docs in the links you provided to see if they address my issue.
After not having a valid cert for about two weeks, I checked today and the subdomain cert is valid again. I'm not sure what, if any, the fix action was. The only change I made was to check the DNS records for the domain listed on the Linode Domains page. I added one for the subdomain even though one already existed then went to the site to check, but that was less than a minute after adding the redundant entry (and the cert issue date is listed from last month, from a date that's earlier than when I noticed this issue). Regardless, the issue is resolved.