Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread: CentOS2Alma discussion
Correct, however as I "suddenly" received the 502 like this thread and resolved it with the help of this thread I added my resolution for others.
Thank you mentioning to add "127.0.0.1/8" as I haven't done that yet.
while i had the same issue I had a different solution, the whitelist didnt seem to exist anymore so i created it:
touch /etc/asl/whitelist
I followed it with running and only applying configuration again.
plesk repair web
both commands give a positive response. renewing the certificate also fails from the console. Strangest is that all my other websites renew properly automated, but once I request them manually they fail.
Since a few weeks I cannot renew certificates via the control panel, I continuesly receive a cURL error 35 followed by a cURL error 56 eventually. Automatic renewals seem to do fine.
Similair issues with Plesk are described on the letsencrypt forums...
This wasn't the first time but ProFTPD randomly stops working while it's still listening on port 21 it doesn't accept requests other than SFTP.
Status: Connection established, waiting for welcome message...
Error: Connection closed by server
I've already tried re configuring passive FTP...
When I lower Selinux to Permissive it changes to the following error:
proftpd[3852]: mod_ctrls/0.9.5: error: unable to bind to local socket: Address already in use
Since the latest update this week I receive this error when a user tries to connect to FTP
In the log (tail -f /var/log/messages) it displays the following error:
proftpd[11996]: mod_ctrls/0.9.5: error: unable to bind to local socket: Permission denied
I cannot really find any suitable...
So have example.com as a main domain registered with only some glue records at my registrar as following:
ns1.example.com
ns2.example.com
ns1.fire.example.com
ns2.fire.example.com
And my plesk server is registered as fire.example.com with two nameservers and unique ip's:
ns1.fire.example.com...
At first I installed a single domain certificate. However the customer requested a wildcard due to the use of dynamic subdomains. When I unassigned the certificate and removed the DNS record I created a wildcard subdomain and requested a new *wildcard* certificate. However, no wildcard...