Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
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.
Thanks for your information. Please note that, we are performing this process for our customers while allowing only standard ports such as 80, 443 and plesk standard ports for public. All other ports will be blocked from public incoming access.
Similarly, the outgoing ports will also be restricted and allowed only for specific domains.