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.
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !
WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure. Join the pilot program today!
Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
The main issue seems to be this (?):
Code:
[2025-02-01 01:02:04] [2025-02-01 01:02:04] Waiting for ImunifyAV to start...[2025-02-01 01:02:05] [2025-02-01 01:02:05] ERROR: imunify360 service is stopped.
Well...
I solved it myself (Cheating a bit with the help of ChatGPT ) .
So I will post the solution for others that might run into the same issue:
In systemd (which Plesk uses on most Linux distributions), a "masked" service means it has been explicitly disabled and cannot be started or enabled until it is "unmasked."
To check the status and fix it, follow these steps:
1. Check if the service is masked
Run this command in SSH:
bash
Code:
systemctl is-enabled imunify-antivirus
If it returns masked, then the service is indeed disabled.
2. Unmask the service
Run the following command to unmask it:
bash
Code:
systemctl unmask imunify-antivirus
3. Enable and Start the Service
After unmasking, try enabling and starting the service:
bash
Code:
systemctl enable imunify-antivirus --now
4. Verify the Service Status
Check if it’s running correctly:
Bash
Code:
systemctl status imunify-antivirus
If the issue persists, try reinstalling ImunifyAV: