Search results

I have also contacted the host provider about this. And I was probably very correct in my assumption. We suspect that it is due to the very outdated kernel on the host system, which is shared with a modern Ubuntu 22.04 operating system on openvz. hostnamectl Virtualization: openvz Kernel: Linux...

@Sebahat.hadzhi

plesk bin http3_pref --enable -nginx https://docs.plesk.com/en-US/obsidian/administrator-guide/web-servers/apache-and-nginx-web-servers-linux/plesk-for-linux-http3-support-in-plesk.80026/

I was just able to reproduce it this way too, so the task limit doesn't seem to be the problem: After that it worked again on 2 attempts. Is it possible that Plesk sometimes does something in the background and if an update takes place during this time, that it then hangs? Cronjobs or...

Unfortunately there is nothing to be found anywhere. These are the first entries from the log. I don't understand it either. But the problem is reproducible after every Plesk update, which I install myself via https://example.com:8447/installer/summary.html. The other user here had the same...

@Bitpalast /var/log/sw-cp-server/error_log - Many entries of: cat /var/log/sw-cp-server/sw-engine.log (nothing more)

But I'm not entirely sure whether this is the solution to the problem. As there was a real loop when restarting the service tonight. Ps. Too bad you can only edit here for 4 minutes, that's a bit short. journalctl -u sw-engine -n 100 --no-pager

I have the checkbox as well.

Analysis Commands cat /proc/sys/kernel/pid_max → Shows the maximum number of process IDs (PIDs) available system-wide. Output: 4194304 This is a very high limit, meaning the system allows up to 4.19 million simultaneous tasks. It’s a kernel-level setting and not a practical limit for...

It seems to have something to do with the cgroup limits? I still have the error with Plesk updates. https://talk.plesk.com/threads/plesk-backend-often-not-accessible-when-installing-updates-manually.378687/

What I then see is that the sw-engine.service is not running (in the repair kit). Does this take longer after an update until it starts again? Even hours? This has not yet been observed with automatic updates.

Hello, when I install a Plesk update manually and the installation is completed successfully, I can access my websites normally. But when I try to log in to the Plesk backend, I usually get an error message when I call up the login page and it is recommended to use the repair kit. If you then...

I was just wondering if Plesk validates something like that or just files it and that's it? I have an Ubuntu 22.04 server. According to Crontab.guru - The cron schedule expression generator it is not a standard rule. So I was unsure how to find out if it works or not. Anyway, it seems to be...

Does Plesk Onyx for Linux support the cron syntax 30 11,16 * * 3-7 for scheduling tasks? I want to run a script at 11:30 AM and 4:00 PM every Wednesday through Sunday.

@LRob That fits, thank you very much! One hand washes the other :)

@Kaspar This code works fine also with IPv6: #!/bin/bash # Your AbuseIPDB API Key API_KEY="123" # File where already reported IPs are stored REPORTED_IPS_FILE="/var/log/reported_ips.log" # If the file doesn't exist, create it [ ! -f "$REPORTED_IPS_FILE" ] && touch "$REPORTED_IPS_FILE"...

@Kaspar Unfortunately, for a few days now, thousands of such bots have been sending corresponding requests to the web urls within a few hours, which places a heavy load on the CPU. These requests are contained in each of these bot IPs. And are apparently not recognized by the previous Fail2Ban...

Hey! I would like to block an IP if any of the following URLs are accessed three times. Essentially, if a bot tries to access these files multiple times, it should be automatically blocked: /wp-content/plugins/index.php /admin/function.php /wp-admin/user/network.php...

You can also simply prevent it via .htacesss or nginx directive. But with all these questions, one thing is paramount: inexperienced users do not know this. However, Plesk suggests on the help page that the WordPress Plesk jail protects against brute force. I also assumed this at first: But then...