• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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