Topic: NET::ERR_CERT_AUTHORITY_INVALID on Chrome
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.2.1 MARIADB edition
- Deployed with iRedMail Easy or the downloadable installer?downloadable installer
- Linux/BSD distribution name and version: freebsd
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx):nginx
- Manage mail accounts with iRedAdmin-Pro?no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
I'm planning a server hw upgrade from an old 2010 running iRedMail 1.0.
I finished installing 1.2.1 on the newer server and could access https://IP/mail and https://IP/iredamdin. I have valid letsencrypt certs, which are also working with the old server.
DNS is resolved, only the not-secure keeps showing, and even after the respective iRedMail Certs/Key are linked to letsencrypt according to letsencrypt in freebsd.
The 'not secure' to the left side of the URL, where it is normally a green padlock, says some invalid root certificate that expires on 26 April 2030, not the letsencrypt ones that are linked.
If I put this,
openssl x509 -noout -dates -in /usr/local/etc/letsencrypt/live/domain.com/cert.pem
notBefore=Mar 20 21:02:25 2020 GMT notAfter=Jun 18 21:02:25 2020 GMT
Do you know why they can't latch properly to the iRedMail certs/keys?