• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Question Domains to whitelist on plesk

Thomas Oryon

Basic Pleskian
Server operating system version
Almalinux 9.2
Plesk version and microupdate number
18.0
Hello,

We have whitelist some of the domains and we need to get all domain to be whitelisted as few new plesk URL what we whitelisted differ.

Awaiting your reply.
 

Attachments

  • image (2).png
    image (2).png
    836.1 KB · Views: 4
Whitelisting domain names? What domain names? Where? Why?

"could not resolve" means that your nameserver doesn't know the domain name and cannot deliver the proper IP address for it. Make sure that you are using legit nameservers in your /etc/resolv.conf file.
 
We are trying to setup plesk where only certain ports, IP addresses will be opened. So, in order to run plesk without on the restricted environment, we require domains, IP addresses that needs to be whitelisted inorder to work in that environment.

We will be allowing only outgoing ports to only certain ports, IP address and domains. We will be performing below operations

++++
  • Install plesk. To install plesk, we will need to allow all plesk installer URL
  • Update plesk. To update plesk, we will need to allow all plesk updater URL
  • Licensing plesk. To connect plesk license server, we will need to all plesk license URL, IP address
  • Upgrade plesk. To upgrade plesk we will need to plesk upgraders URL, IP address
++++
 
You're trying to use Plesk in an environment it's not build for. Plesk (or any control panel for that matter) is build for use in an open, connected environment. Running Plesk in a restricted or offline environment undermines it's core functionality, security posture, and maintainability.

I am not saying it's not possible to use Plesk in a restricted environment, but the reason the various repositories and URL endpoints used by Plesk (and extensions) aren't documented is because Plesk is build to be used in an open environment. Because your use case falls outside of what a control panel is typicality build for, your best course of action, imho, would be to map each endpoint and repository yourself.
 
Back
Top