Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
If the errors should show again:
I had similar problems a while ago with fail2ban where reinstalling failed to fix the error. It turned out that when uninstalling, fail2ban left configuration files in /etc/fail2ban/, which were never overwritten on reinstall. When uninstalling it's best to...
It's a disc error.
I've just noticed that with the dbfile = memory setting fail2ban is actually creating a database file called 'memory' in the /root folder.
So:
dbfile = /var/lib/fail2ban/fail2ban.sqlite3 = disc I/O errors
dbfile = memory = no errors. (but not in memory, in file /root/memory)...
I've been trying to help a member here with his fail2ban installation and after following advice from a more knowledgeable member I changed my own settings yesterday so fail2ban would use a disc based database, where previously I had it stored in memory.
I woke this morning to a 25+GB logfile...
I found by experience that using a database file with a lot of domains, and therefore a lot of logs, causes quite a load in the form of disk reads/writes, slowing the whole server. It can actually get to such a load that fail2ban can stall (fail) - defeats the object. Reducing the database...
Stop the fail2ban service. Search /etc/fail2ban/fail2ban.conf for 'dbfile ='. Make that line read dbfile = memory then restart fail2ban.
Settings and whitelisted IPs are stored in the various conf files. I believe he database stores the current bans as well as the relevant counts. So any...
Whitelisted IPs are stored in /etc/fail2ban/jail.local
Would make sense just to download that file, uninstall fail2ban, clean up any errant files, install fail2ban, stop fail2ban, upload the file (overwriting preserves permissions) and finally start fail2ban.
I did find (at a later date) that...
Login to the server via ssh using 'root' and the password sent to you.
In the terminal console: # plesk repair installation
If you are on 12.5.30 that should bring plesk back. Paste the log from that here if it doesn't work - it'll give some clues
I may have made a mistake. The way I read the OP I believed omexlu12 wanted a way to make the setting through the panel, not disable the function within plesk.
Apologies if I was wrong.
I see you're working on it as www.xswaar.me is working for me whereas the others give me the service unavailable.
Did you delete the default index.html that was placed in your webroot by Plesk as that's what I'm seeing? Try www.xswaar.me/index.php. If that gives you what you want just delete...
When making any changes to DNS or nameservers you have to wait for the changes to 'propagate' through the various nameservers. I believe a way around this is to set TTL to 0 before making any changes (untested).