Nextcloud-snap: Removing trusted domain and lets encrypt certificate

Created on 14 Sep 2017  路  5Comments  路  Source: nextcloud/nextcloud-snap

Hi,

I changed my dns provider and need to remove the old https certificate from lets encrypt and the domain from the trusted domain. I have been searching around in nextcloud forum and here but couldn't find much related to the problem. I appreciate if you could help. Thanks in advance.

Most helpful comment

You must be using the Box. Judging from the bug reports I've seen, yeah, it's normal. I'm not sure what the deal is with that image (I was not involved in making it), but from what I've seen it's harmless.

I'm glad you're sorted! I'll go ahead and close this, then.

All 5 comments

You can see the list of trusted domains with:

$ sudo nextcloud.occ config:system:get trusted_domains
foo.com
bar.com

To remove one, use the index in that list. For example, to remove bar.com from above:

$ sudo nextcloud.occ config:system:delete trusted_domains 2

You can disable HTTPS using:

$ sudo nextcloud.disable-https

And then try getting certs for your new domain just as you did before. If you run into issues with that, blow away the old certbot data at /var/snap/nextcloud/current/certs/certbot and try again.

Thanks for the quick response mate. I have done everything you said except the certbot thing but when i go to the website over https or try to login with nextcloud android app, i get The url does not match the hostname in the certificate.. Disabling https doesn't remove the certificates.. How can i remove the certificates? by removing certbot? like rm -f certbot ? The whole folder?

Disable HTTPS should stop using the certs, even though they're still on disk. Although since it used HSTS you have a bit of an issue since your browser is caching the fact that it's HTTPS. Try visiting it in Firefox's private mode (i.e. open up a "private window").

If you must remove the certs, yeah, blow away /var/snap/nextcloud/current/certs/certbot.

Removing the certbot solved it mate. Thanks alot. By the way i have been getting these errors with every command many times:
ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.

Is it normal?

You must be using the Box. Judging from the bug reports I've seen, yeah, it's normal. I'm not sure what the deal is with that image (I was not involved in making it), but from what I've seen it's harmless.

I'm glad you're sorted! I'll go ahead and close this, then.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mo-seph picture mo-seph  路  6Comments

pilsnerbeer picture pilsnerbeer  路  6Comments

nihil21 picture nihil21  路  6Comments

aptanet picture aptanet  路  7Comments

edrohler picture edrohler  路  3Comments