Recent content by Tim_Wakeling

Thank you Manos! I followed your instructions, installed the iptables service (it was not installed) and was able to disable firewalld. Now its status shows as: $ systemctl status firewalld ● firewalld.service Loaded: masked (Reason: Unit firewalld.service is masked.) Active: inactive...

I just tried checking the status of plesk-firewall and firewalld, and got the following output: $ systemctl status plesk-firewall ● plesk-firewall.service - Plesk firewall rules Loaded: loaded (/usr/lib/systemd/system/plesk-firewall.service; enabled; vendor preset: disabled) Active...

Hi Manos - thanks for the heads-up. How would I go about checking whether firewalld is configured in the way you have highlighted, so as to know whether it's safe to disable? Thanks!

Hi again ... another NetworkManager update occurred this morning and once again, all websites went down, just like above. I restarted the firewall and everything was back up. My host advised me to disable NetworkManager and revert to using network-scripts, which I have done, but realising that...

I confess I didn't know about iptables. I used the Firewall from the Plesk interface, and it seemed to work as advertised. What does iptables do, and should I remove it if I'm using the Firewall in the Plesk interface? How would I do that? Thanks!

By "both services", do you mean firewalld and fail2ban?

Just tried that and it took everything down! Had to restart the server manually from the VPS control panel. Now it's all back up. OK, I think the fail2ban thing was a red herring. I've tracked down the exact time things went wrong, and it was about 3.20 am, just when the following updates were...

Something very odd happened last night on my server. About 4 am, when nothing was due to run (the backup completed at 1.25 am), all sites went down. I could not log into Plesk, but I did have the CLI. nginx crashed when I tried to restart it, and plesk repair all -y also failed at the stage of...

Thanks @trialotto - I wasn't quite clear in how I explained it. As well as all those warnings, I *also* had an nginx error involving setting a directive twice on one domain. It was my mistake, and had nothing to do with all the warnings. But it sounds from what Peter was saying that the warnings...

Ah, when you wrote that I realised - at the end of all those warnings was one message that probably caused the error to appear along with all the warnings: a duplicate directive. The red box was around the lot and it was not obvious that the last error was the only one causing the red box. It...

Just to say, @TobiasP - you're right, I don't use Kolab either.

Yes, it does seem to remove the error! I will set all my domains to "none" for now.

I will try this, thank you - and will review all the further replies to this thread for clues. Thanks to others for joining in with your thoughts! It looks like I am not alone with this problem and hopefully a solution will be found.

Thanks for the tip! But when I type nginx -t I just get a readout of the errors I posted above, i.e. the following two lines for every domain on my server: nginx: [warn] protocol options redefined for 193.33.178.154:443 in /etc/nginx/plesk.conf.d/vhosts/domain.com.conf:6 nginx: [warn] protocol...

On my server with nginx 1.24 I am getting the following red errors: Unable to configure the web server: Execution failed. Command: httpdmng Arguments: Array ( [0] => --reconfigure-all [1] => -skip-removing ) Details: Execution failed. Command: httpdmng Arguments: Array ( [0] =>...