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

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