• 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 Your connection is not private

linuxnow

New Pleskian
Server operating system version
Nginx
Plesk version and microupdate number
18.0.56
Hello,

My webmail service: webmail.company.com points to a specific public Ip: x.x.x.x

When I open the public IP it shows me Plesk Panel, while when i Open the webmail it shows the roundcube. Meanwhile, when I open the company.com:8443 (default port of plesk) is everything okay with the certificates.

I have a question regarding the specific public Ip: x.x.x.x when I open it shows the output as below:

Your connection is not private​

Attackers might be trying to steal your information from 192.x.x.x (for example, passwords, messages, or credit cards). Learn More


NET::ERR_CERT_COMMON_NAME_INVALID

This server could not prove that it is 192.x.x.x; its security certificate is from serverX-X.Xlhost.com. This may be caused by a misconfiguration or an attacker intercepting your connection.

Can you explain and assist me in this solution? How to fix? Which is the impact of it
 
Back
Top