• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue NET::ERR_CERT_AUTHORITY_INVALID

hardbrasil

Regular Pleskian
Hi fellas,
i already installed ssl on domain, everything is ok when i use main IP of server (share IP)

when i set a fix IP to the domain, website go offline, and by chrome i got this

NET::ERR_CERT_AUTHORITY_INVALID

and by firefox i got default plesk page
 
Hi hardbrasil,

you might have set "redirect to HTTPS" and still got the SELFSIGNED Plesk - certificate as the default SSL - certificate. Pls. change the certificate to a real one, or switch off SSL - usage for that domain. ;)
 
hi,
actually no. i mean i am using a real ssl (purchased one). the issue start when i set a FIX IP.
if i continue using shared IP of server ssl works>

i tried to disable https redirect, still the same.
 
Hi hardbrasil,

in this case, you have to step out of your anonymity and provide the depending FQDN, for further investigations. It could as well help to post your webserver - configuration files and pls. don't miss the one from the "default" domain on your server, which is available at your standart apache and nginx installation path. ;) Apart from all, you already know, that log - files are the best for investigations, as you are a long-term member of this forum. :p
 
there is no issue with domain logs, even on webserver level.
my fdqn is admin.next4.net.br -> 158.69.97.192
 
Hi hardbrasil,

you might be informed, that with STANDART APACHE - installation, there are "../sites-available" and "../sites-enabled" ( where configuration files in "sites-enabled" are symlinks from "sites-available" ) for apache directing to "/var/www/html" as documentroot. Are they existent on your server? Because calling the site "http://admin.next4.net.br/" directs to the files from your standart APACHE - WEBSERVER - installation on your server... not to any Plesk page. Plesk doesn't generate configuration files for "/var/www/html" :p
Calling "https://admin.next4.net.br/" directs as well to the very same Test - pages, with your Let's Encrypt certificate from your vhost "admin.next4.net.br".

there is no issue with domain logs, even on webserver level.
This statement doesn't match your initial post in this thread:
NET::ERR_CERT_AUTHORITY_INVALID
If you get an SSL - error with your browser, you will see this in your logs as well! ;)
 
Back
Top