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 new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.
ok, so when i log into the server, via example.no-ip.biz:8443 it forwards me to https://example:8443 which is a problem. How can i fix this? host name is example and domain name is no-ip.biz.
What type of No-IP Redirect or Host record did you create at No-IP? If you create just a normal DNS HOST A record it should work fine. I just created one something.no-ip.biz and browsed to https://something.no-ip.biz and the Plesk CP login comes up, the browser address line is then:
i already have it set to dns hosting. when i go to example.no-ip.biz, the page shows up. but as soon as i add :8443 it tries going to example:8443.
when i set up the server, all i had configured on my computer was the host name. now i've gone back and put in the domain name but it seems it hasn't taken effect.... i've restared it serveral times and still no change.
You may have to wait for the changes to the No-IP to fully take effect. Assuming you originally set it up as a Web Redirect, when you submit the change to make it a DNS HOST A record INSTEAD of the web redirect. Make sure you don't still have a web redirect for 'example'.
Also on the server, post the output of the 'hostname' command. It should be a FQDN like 'example.domain.com'