Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.98 minutes in June 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Plesk Services on an Amazon Lightsail Instance – Allow Open Access

by | Jun 12, 2021

By default, we cannot access the Plesk interface and a number of Plesk services on Plesk instances deployed from Amazon Lightsail images.

Mostly, this happens when the ports they require to operate are blocked by the Amazon Lightsail Firewall.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how we can allow access to Plesk Services on an Amazon Lightsail Instance.

 

Access to Plesk Services on an Amazon Lightsail Instance

To access Plesk and use these services, we need to manually allow connections to specific ports or port ranges.

By default, Amazon Lightsail allows all outgoing connections and blocks all incoming connections on Plesk instances.

However, there are exceptions for connections to ports on:

  1. SSH server – TCP 22
  2. Web server – TCP 80, TCP 443

Access to the Plesk interface and Plesk services using ports not listed above is blocked.

To allow access to a Plesk service on an Amazon Lightsail instance:
  • Initially, we go to Amazon Lightsail Home.
  • Under “INSTANCES”, we click the instance and then go to the “Networking” tab.
  • Under “Firewall”, we click +Add another and specify the following:
    a) “Application”- The default “Custom” value.
    b) “Protocol” – We select either TCP or UDP from the drop-down list.
    c) “Port range” – Specify the port or a port range corresponding to the Plesk service to allow access to.
  • Finally, we click Save.

To access Plesk for the first time, we need to allow access to the services below:

  1. The administrative interface of Plesk over HTTPS – TCP 8443
  2. Plesk Installer, Plesk upgrades, and updates – TCP 8447
  3. Domain name server – UDP 53, TCP 53

In addition, here’s a table with the list of ports different Plesk services require to operate.

For security reasons, our Support Techs recommend allowing access only to services we want to use.

We can keep the ports corresponding to the services we do not want to use closed.

For example, to use mail, open all ports listed in the “Mail” section.

Plesk Services on an Amazon Lightsail Instance

For the list of ports, we need to open to allow migrating customers and domains to or from the instance.

[Need help with the procedure? We are here for you]

 

Conclusion

In short, we saw how our Support Techs allow access to Plesk Services on an Amazon Lightsail Instance.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

AWS Support

Use your time to build great apps. Leave your servers to us.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.
AWS Support

Use your time to build great apps. Leave your servers to us.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.

Categories:

Tags:

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF