• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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