• 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.

Resolved Cannot access to Plesk panel page

miphan

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian 18.0.50

Attachments

  • 2023-05-02_18-04-06.png
    2023-05-02_18-04-06.png
    9.6 KB · Views: 20
  • plesk_err.png
    plesk_err.png
    53.5 KB · Views: 14
Chrome probably won't let you login, because the SSL/TLS certificate data are wrong. Please try to use another browser and accept the SSL/TLS "exception" so that the browser connects using a wrong certificate.
 
Chrome probably won't let you login, because the SSL/TLS certificate data are wrong. Please try to use another browser and accept the SSL/TLS "exception" so that the browser connects using a wrong certificate.
I've tried but no luck. I'm not sure if this issue is related to the DNS configs.
 
Since you got in using 8880, I would take a look now at getting a proper hostname setup based on one of your domains and issuing an actual SSL for it so that you can go back to the https port. Glad you got in!
 
Since you got in using 8880, I would take a look now at getting a proper hostname setup based on one of your domains and issuing an actual SSL for it so that you can go back to the https port. Glad you got in!
Thank you, Mark. All my issues have been fixed now. Much appreciated :D
 
Back
Top