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.
I've said it before and I am saying it again: the (lack of support) by SWSoft is unbelievable, but right now it is simply becoming ridicoulous. Seems like Plesk servers all over the place are blowing up - 25 replies to this mail alone and over 500 views but not a single reaction from SWSoft.
Well, seems after SiteBuilder (simply cannot install - error 1722 - nobody cares) another add on for Plesk we can throw out.
Same issue here, spent all Tuesday, about 20 hours trying to clean the mess up Dr. Web created.
I could not leave my server unprotected so I installed ClamWin but had to upgrade MailEnable in order for Plesk to recongnize it, so now I have spent more money on my server than I had planed to, first Dr.Web's license and now ME Pro license...
I am really upset!
BTW, I had to shut down Dr.Web (disebled it) from Windows services as it kept coming back every hour.
If you decide to install ClamWin make sure you set up a task to restart it every hour as there is something in Plesk that suddenly stops it, I have not found what it makes it stop but in the meanwhile I set the task to reset it every hour.
we have the same problem on our windows server running with PLESK. but your tip to update DR.WEB twice didn't help at all!! there are still incomming thousands of e-mails every hour.
Did you clear your que before attempting this and with Dr Web stopped? I've not tried as yet to do the update twice thing but I have DR. Web disabled at the moment, manually cleared my que and all has been fine (of course minus anti-virus). Just trying to understand where you are in the process before I try this.
So how did you restart? Do you mean re-enabled Dr. Web via the component page, then reboot server? Just trying to be clear as I don't need this to start all over again
Can someone provide the link to the update, I do not want to have another catastrophe to deal with.
thanks
OK reading the past posts to get the latest path we just need to run the update program located directly on our web server. There is no program to download and run?