You should read better posts in the topic you've mentioned
LetsEncrypt - SSL certificate is not valid
Anyway, think about moving out of i-MSCP as it is dead ATM.
You should read better posts in the topic you've mentioned
LetsEncrypt - SSL certificate is not valid
Anyway, think about moving out of i-MSCP as it is dead ATM.
Well, the end actually already passed, as software is not installable anymore. So if anything will went wrong and you'll have to reinstall whole i-MSCP, you're done.
Anyway, I'm happy that your issue has been fixed.
You know Delta04 , we are working on obsolete software, everything might be a problem here. I guess that when you install this package it try to install something within old versions of certbot etc., and this might be an issue here. Anyway, you should consider moving I guess.
Delta04 yeah, just uncomment what have been commented before.
Delta04 if you did do anything from this manual: LetsEncrypt - SSL certificate is not valid
you have to revert changes you've made with 5th point. Otherwise you will get invalid SSL.
Then you have to do this: LetsEncrypt - SSL certificate is not valid
Then go to domain - Let's Encrypt and try to renew certificate. It should not be invalid anymore.
If you will still have problems, you have to get newer SSL certs within /usr/share/ca-certificates (for some reason I've got that issue on 1 out of 5 servers with Ubuntu 18.04) and put them there, then again do dpkg-reconfigure ca-certificates .
sgumbert probably they're set on Domain list as "Invalid", then you have to follow this what I've written in this post above.
Anyway, there is still issue with snap running in lxc containers. I need to figure it out somehow (instructions from internet about adding fuse, nesting support to container didn't worked here).
Thanks guys.
try the classic certbot setup by kess
Not working as well on Ubuntu.
I'll try to fix it in different way.
Edit:
What I've done finally:
- restored up changes in code which was made here: LetsEncrypt - SSL certificate is not valid
- imported new SSL certs to OS from some newer Ubuntu
- made kess certbot setup way
Now it's working great.
Anyway, time to make moving out faster.
fulltilt I did it that way before:
LetsEncrypt - SSL certificate is not valid
So probably it's time to change it for new version of certbot, as moving out all the instances of i-MSCP is not done by me yet.
I've generated new certs today for new addresses, it says "Invalid SSL Certificate" in table, and certificate is not attached to domain. No way to do it, I'll do some bypasses for remaining machines.
All the situation happened again on old ubuntu's (while we cannot get any new), as Let's Encrypt changed SSLs again: https://letsencrypt.org/certificates/ .
I guess it's final time to move along somewhere.