Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread: CentOS2Alma discussion
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...
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...
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.
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...