• 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.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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 Impossible to connect with customized URL

Farid

New Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
Obsidian 18.0.51
Hi,

I got an instance with Amazon Lightsail (Ubuntu) running with Plesk.
My domain is managed through Amazon Route 53.
I changed the URL of plesk by plesk.mydomain.com
I created a record (A) in Route 53 to link subdomain plesk.mydomain.com with my IP address used by Plesk.
I installed let's encrypt ssl certificate to this subdomain plesk.mydomain.com
If I check DNS plesk.mydomain.com I can see that linked has been done correctly with DNS propagation checker.

I opened port 8443 in my Lightsail instance in any case.

Problem that I have now, is that I can't connect to my Plesk login page using https://plesk.mydomain.com, I'm getting a timeout issue.
If I try the link https://plesk.mydomain.com:8443 I'm getting error "ERR_ADDRESS_UNREACHABLE"

If I try to connect to Plesk with my IP address using 8443, it's not working anymore...
So to resume, I don't know how to retrieve my access to Plesk....

Could someone give me some help?
 
What happens when you try to address your server using the IP address instead of the domain name?
 
If you're getting timed out it sounds like a firewall is still blocking it. I usually don't recommend this but disable ufw if you have it enabled and triple check your aws security to allow 8880 and 8443 to your server. If you're able to connect after disabling ufw and after confirming 8880/8443 is set for allow then we basically confirmed that ufw was blocking it.
 
Back
Top