Search results

The same procedure as... ;) Temporary fix for Ubuntu 18: Downgrade... sudo wget https://dl.grafana.com/oss/release/grafana_8.1.7_amd64.deb sudo dpkg -i grafana_8.1.7_amd64.deb Or, have a look: https://talk.plesk.com/threads/advanced-monitoring-extension-not-working-with-grafana-8-0-0-1.361060/

Yes :/

And here... https://support.plesk.com/hc/en-us/articles/213400309-How-to-migrate-from-Plesk-for-Windows-to-Plesk-for-Linux-and-vice-versa-

This turns the server into a washing machine. ;) Joking aside. The command searches /mnt/... for the script firewall-active.sh which is apparently in a different place than here at Ubuntu18

I might be wrong, but if I had to migrate such a combination, I would first try to upgrade the Plesk version on the old Windows to the latest version, install the Plesk migrator on both servers and perform a migration in this way. If you have used the IIS as a web server on the Windows server...

Hmm... In this case I would do a find /mnt/ -name firewall-active.sh

"yourMountpoint" is just a placeholder that you have to adapt to your circumstances If you are not familiar with this or can follow the explanations, you should look for a professional service provider. After this link, the correct spelling is if you have mounted the disk with Plesk on /mnt...

I can confirm that. We haven't had any problems here since the update today, not even with the admin logout. (Ubuntu18, latest Plesk update)

Nothing easier than that... ;) Restart your server in rescue mode and mount the device on which your Plesk installation is located as described in the docs ... https://docs.ovh.com/gb/en/dedicated/ovh-rescue/ Now navigate to the directory: /yourMountpoint/opt/psa/var/modules/firewall Open the...

/usr/local/psa/var/modules/firewall/firewall-emergency.sh hth...

I am not asked, but I have something to say about it. Many security-minded admins do not like it when functions are implemented and activated in the ACP without being asked, which access functions outside the server or handle authorizations carelessly in the standard system. I don't want to...

Rootaccess for Admin is enabled by default. https://support.plesk.com/hc/en-us/articles/4405249374994-How-to-disable-root-access-via-the-SSH-Terminal-extension-for-the-Plesk-administrator- So restart Plesk after changes should do the trick ;) service sw-engine restart && service sw-cp-server...

Add to plesk panel.ini [ext-ssh-terminal] rootAccessAllowed = true

Remove it: /modules/catalog/index.php/installed

There ;) Your note above, in connection with what is quoted, indicate that the connection: Database / Php / Webbrowser / Nginx is running out of resources somewhere and one in the row gets stuck. (Gateway timeout ...) Either the settings of those involved must be optimized or the RAM must be...

In that case, you may need to upgrade from 24 to 32 GB of RAM or more to avoid such bottlenecks. Then, with more ram, you should check your database settings and carefully increase the value for Connections.

Your problem is that either a search bot opens a lot of connections very quickly or someone tries DOS on the domain. Check this by opening the log file acess_ssl.log for the domain concerned and looking there for entries of an IP address from which many page views take place in quick...

Open your panel.ini Editor... Add: [screenshotService] url = "" save... then... service sw-engine restart && service sw-cp-server restart

The error seems to be fixed, after another 2.4.9 installation this morning from PPA for Apache 2.x : Ondřej Surý the error no longer occurs. :D

In my opinion, this is really not a Plesk problem, but it becomes a Plesk problem if Plesk "over night" undoes my settings, which deactivate Nginxproxying for this IP/domain and change the IP/domain to Apache only.