Search results

Yes, agreed, @PeterK900 can't see the relevant data, because he's not root.

Another approach can be to contact official Plesk support. They'll most likely succeed in identifying and solving the issue.

That's not possible when MariaDB is on your system. It must log start/stop actions. Maybe try "journalctl -xe" without the unit parameter and scroll through the actions. You can also check /var/log/messages or /var/log/syslog for entries related to MariaDB. Generally: When MariaDB starts or...

journalctl -xe -u mariadb

If you could please provide the log message(s) that describe the startup issue, I am sure that other experts here or myself will be able to help.

Would give some more details on it? MariaDB has probably logged the reason why it doesn't want to start. Most frequently there is an error in /etc/my.cnf.

It took me a while to see the new dashboard. Only now since 18.0.64 where it automatically became the default I am seeing it for the first time. And I must say: Very well done! Keyword: "Endowment effect", we had a mail conversation on that one ... It's a really much more useful page now with...

@Tomsohner It's nothing that Plesk should do as it is not a task for control panel developers, but a task for system administrators. Your approach of banning subnets is one valid approach. At my business here we currently ban 600+ subnets practically permanantly, and there has never been a...

Did you check your network interface card settings that IPv6 is actually active on your host? Does your host listen to it?

And did you follow the advice of the first step to verify that the IP is indeed reachable on the server?

Would not a solution ideal that runs a regex replace operation on the webserver configuration files so that upon the next reload or restart the updated version is loaded? It would avoid the need for a short downtime due to reconfiguration of all files by the normal Plesk reconfiguration tool.

The proxy_ssl_protocols are only relevant for the internal communication between Apache and Nginx. As this traffic is local only, there is practically no risk.

All backup content is packed in a single .tar file. It needs to be downloaded and unpacked to have a separate directory for the one client you want to restore.

Username: TITLE [Minor] Text placeholder variable appended to otherwise correct translated text PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Obsidian 18.0.63 #4 Alma 8.9 PROBLEM DESCRIPTION After changing the PHP version of a website, the green confirmation box "Information...

Username: TITLE Update to 18.0.63 #4 removed /etc/fail2ban/jail.local, crashed Fail2Ban PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Obsidian 18.0.63 #4 Alma 8.9 PROBLEM DESCRIPTION In one case the automatic minor Plesk update to 18.0.63 #4 has removed the...

A reason for this behavior can be that another domain or subdomain is configured to use the same document root directory or a directory that descends from that directory. In such cases Plesk will not remove the directory. It's a well done protection against accidentally removing document roots...

It is required to either reload specific jails or to reload the fail2ban configuration altogether to apply changes in configuration or filter files.

Similar thread: Question - New bad bot fail2ban filter: will overwrite customization?

Check out this related thread: Resolved - Error fail2ban since update to 18.0.63, other users are reporting that custom configs in the directory reserved for custom configs are removed by the update.

That could be a security risk. It might be better to duplicate the dataset and use 127.0.0.1 in the duplicate instead of localhost.