snap refresh error x509: certificate signed by unknown authority
hello,

we are using a ubuntu 18.04 server with snap installed.

if we try to refreh our snaps (core and rocketchat) we get the error

x509: certificate signed by unknown authority

i did a apt get update and apt-get upgrade and all packages are up to date.

i searched for this error and i found som…
problem solved

the file /etc/ca-certificates.conf was modified and all mozilla root cas are removed with a “!” at the beginning of the line.

i removed all “!” from the lines and ran update-ca-certificates. now all root certificates are copied to /etc/ssl/certs. after that i restart the snapd and …
hey [@j.kassner](/u/j.kassner),

please see the solution to your question here:

[image]

["signuture is invalid" cdn 1.7.10 js viewer](https://devforum.zoom.us/t/signuture-is-invalid-cdn-1-7-10-js-viewer/24302/4) [web sdk](/c/web-sdk/13)

hey [@j.amelsberg](/u/j.amelsberg),

it appears you are using your sdk app key and secret to generate the signature. you need to use your jwt key and secret app to ge… thanks for getting back to me [@michel1](/u/michel1)! in this case, i recommend you to contact our support team: [how to contact our support team ✉](https://forum.asana.com/t/how-to-contact-our-support-team/87774). unfortunately i don’t have the tools in the forum to check what’s causing the error in your screenshot but our support team should be able to assist here.

when you c… yep, getting my clients mixed up.

[image] macencrypt:

i found called "--renew-hook" in v 2.8.9

i think hooks have to be part of your original --issue/--install-cert commands. if that's right, feeding it to --cron doesn't have any effect.

how about doing (as root):

acme.sh --install-cert \

… the problem has been solved.

i got in contact with our provider and they were able to apply the proper access to the folder for verification.

thank you for all of your help and patience. this thread can now be closed. [image] soydepr:

certbot: error: unrecognized arguments: renewal

you should still be able to renew. the command is:

certbot-auto renew was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . oh my god … i have to appologize very, very much for wasting your time. as so often the problem is sitting in front of the screen :frowning:

i am using certbot inside a script where i make a backup of the /etc/letsencrypt folder, stops apache, on so on …

my mistake is, that my backup of /etc/letse… first of all, you need to check if you are using a self-signed certificate.

if so, you have to accept it first: double-clicked on the request in the network pane, and ow prompted you whether you wanted to accept the certificate.

other option will be to use the [overwolf.web.sendhttprequest()](http://developers.overwolf.com/documentation/sdk/overwolf/web/#sendhttprequest) funct… We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1. this issue is now confirmed fixed by a large percentage of our user base. if you're still having issues, please make sure you on the latest version of malwarebytes (at the time of this article, it's malwarebytes 3.5.1.2522 with component package version 1.0.441).
 


 


 if you continue to have issues after that, please make a new post using the following as a guideline