Search results

Did you activated the pagespeedboost for all sites? I had that issue by doing so. So I did a roll back, and everything was fine.

Maybe this help, after a new installation some month ago this step was forgotten by me. Look at your network interface for the ipv6 route and activate it via CLI: ip -6 route add default via "YOURROUTE-IPV6" dev "YOURNETWORKINTERFACE" additional reregister IP at CLI ip -6 addr add "YOURIPV6" dev...

For all who need serverwide, for all domains too. At CLI: plesk bin site -l | while read domain_name; do plesk bin site -u $domain_name -webstat awstats; done

Thanks a lot. It works. And the loop should also do. Thanks for that link too.

Hi, Server Update to Debian11 from debian 10, the wabalyzer is not more supported. No matter I could live with awstats. But I have a large number of domains to be switched. I tried it via Subscription plan. It do not work, every subscription with former webalyzer got notthing set at stats. I...

Not on 11 to 12 but I had the same problem at my first try of 10 to 11. I did a misstake in not correct overrride /etc/apt/sources.list Step 9 correctly and not doing Step 1. Broke my server. After rebuilt with snapshot and doning right it worked. Mixing bullseye and bookworm so not work.

I had after updates somewhen the same problem. My solution is: Have you additional IPs? Reread IPs and get unregistered IPs at serverside registered again. Reread IPs. Then run the repair tool. First I run to ensure me --db --mysql --dns, ! That order ! ; I tested out, that the order the...

Look here: https://support.plesk.com/hc/en-us/articles/12377714344983-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk- Backup everything before, importent.

Hi I may remember to have the same issue, not on a IONOS server last year. So I don't think thas an Inonos issue. It is something with IPv6. Im not a specialist, but I solved it till today by dropping a line out of /etc/network/interfaces: Get rid of: iface lo inet6 loopback But for future...

Maybe something is wrong with the backup-file. Try an older one, an additional steps back. Make a snapshot, delete the domain and after restore it. So you evade this domain update steo out of the failture notice. Snapshot is for a step back.

That was it. Thanks. Once I didn't took notice of the changelog such things happens.

Hi I had this fetch error some days ago and it was caused be fail2ban. I uninstalled it and reinstalled it and it was gone. Maybe this helps.

AH00526: Syntax error on line 61738 of /etc/apache2/plesk.conf.d/server.conf: RemoteIP: Error parsing IP RemoteIPInternalProxy (Name or service not known error) for RemoteIPInternalProxy It happend this night after new update was automatically done. Maybe this has to do...

So as I promised. I did a redo. This time it went through without any issues. The only thing I changed was to connect via cable instead WLAN. So my educated guess is that in april the WLAN connection was intererupted at the critical stage of the DB work (where the flush of the user and the new...

nginx ignores htaccess, so when you got nginx as proxy for any kind of static files, e.g. jpeg, served by niginx the result for pagespeedinsights or similar tools will be a fail. Try for experience a stop of nginx for that subscription and look and feel and to get a clue what happend. I stopped...

I had something like that some Updates ago. It caused issues when bachup. I identified two issues, one was trouble with 2 htaccess files. I removed them, waited some time and got up one which works (there must have been a fault somewhere in the files). The second was a problem that 3 IP's where...

Had two years ago same issue. Made a Backup and snapshot of everything, just for a step back opportunity. then I got a new subdomain connected it via dns entries to the server where plesk is and waited a day or so that new dns entries became recognized. tested the subdomain, normally it should...

And now I'm aware of doiing again to get the issue again. Except that error messanges the server and everthing else doing fine. I normally do nothing at the DB of plesk. Only if I have to following any instructions of a plesk solution. Maybe I did something wrong last weekend. And thanks for...

It was starting with error massanges in the Webserver Configuration troubleshooter. The solution was explained here: https://www.plesk.com/kb/support/error-in-plesk-new-configuration-files-for-the-apache-web-server-were-not-created-due-to-the-errors-in-configuration-templates/ At step 2 it gave...

Oh your looking for Flushing and stopping at point 9 or so. So far I did all im a row, that's why I'm a bit affraid do do again. So far the server runs, and I will take a bit of time the redo it. The original intention was to delete some dead nginx entries in db. via CLI. As I read in the plesk...