Search results

Perhaps this helps? Issue - Failed to apply the firewall configuration - [ext-firewall] set to 40 seconds

Described the solution for nginx here: Issue - Failed to apply the firewall configuration - [ext-firewall] set to 40 seconds Can be similarly modified for other web servers.

My hoster has analyzed the problem with Plesk. It should be fixed with an update. Temporarily it should help to do the following: systemctl edit nginx.service Paste: ### Editing /etc/systemd/system/nginx.service.d/override.conf ### Anything between here and the comment below will become the...

Super vielen Dank, das hat geholfen. Wäre natürlich klasse, wenn die Zertifikate automatisch unter chroot laufen würden :)

@Peter Debik but I don't use WP CLI. Its a normal http Request I made here

I tried it again: My Panel.ini: [ext-firewall] confirmTimeout = 120 confirmTimeoutCli = 120 Wanted to open TCP port 8080 for everyone. Error: Now with: Plesk Obsidian Version 18.0.54 Update #2, zuletzt aktualisiert: 2. Aug. 2023 04:22:24 @Jeroen Bl I use the default ssh port - same error...

Command: curl -u user:passwd https://example.com/wp-cron.php?doing_wp_cron Error: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (77) error setting certificate file: /etc/ssl/certs/ca-certificates.crt Checked file: [CODE]ls -l...

Feel free to use this shell script: Input - Plesk Fail2Ban: Integration for AbuseIPDB

If no output is desired except for errors: #!/bin/bash # Your AbuseIPDB API Key API_KEY="YOUR_ABUSEIPDB_API_KEY" # 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...

Hello! If you want to report the blocked Fail2Ban IPs from Plesk to the AbuseIPDB, you can do this with the following shell script I created. This increases the likelihood that hosters will become active and infected systems will be uncovered. It includes a check that already reported IPs are...

My Plesk crashed after the update finished. I restarted the server and the last error message was gone afterwards. Nevertheless, I am unsure how often there are problems after updates or even that Plesk hangs. The system has a lot of computing power, that won't be the reason.

The error seems to have been fixed in the current Plesk Obsidian version 18.0.54. The message no longer appears. There is now a new surprise for this:

The error seems to have been fixed in the current Plesk Obsidian version 18.0.54. The message no longer appears. There is now a new surprise for this:

Sometimes Plesk also shows that the rule was successfully recorded (message above). However, it does not appear in iptables and the status widget at the bottom right shows the quoted error I post at the first post. When I reload the firewall page, it is active and the rule is shown as active...

No, that's the only rule I wanted to add individually. I have already tried twice to first uninstall and then reinstall the firewall component and also to be on the safe side ran a plesk repair all -y. I recently reinstalled the system with Ubuntu 22. Fresh reinstallation. Then resumed the...

Apparently there are several with the same problem on completely new systems. I have the same error now. If you buy software and updates bring in bugs, don't make users pay to fix the bugs. This is obviously not about a special, individual case of a single user on a special system, but about a...

Hello, can someone tell me what's going on here? I don't have a SiteBuilder extension or similar installed? When updating I get the message:

Without the rule it also takes some time but works. But it should be possible to add your own rules. There is no other rule with port 8080.

I've only one custom firewall rule I want to add: port 8080 incoming. I've already set [ext-firewall] confirmTimeout = 40; in panel.ini. But I get the error every time: Any ideas?

Problem persists after following these tips and reinstalling: https://www.plesk.com/kb/support/docker-service-is-still-running-on-server-when-docker-extension-was-removed-from-plesk/ Docker can then be installed again, but the settings for the port are not visible