• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Certificate issue with web deploy using wrong Service URL

SimonHolman

New Pleskian
When we enable web deploy and download the publishing profile file, it uses the users domain as the MSDeployServiceURL rather than the servers host name. The Web Management Service certificate matches the host name of the server, not the client site name, so the web deploy fails with a certificate error.

Is there a way to change the default publishprofile template to use the proper service URL?
 
Good question, I didn't find it in the panel.ini.

Maybe the template file is somewhere in the Plesk installation folder?
 
I sent this to support and the response boiled down to "There's no way to change it and the users should either manually edit the file once downloaded, or setup the publish settings themselves" which is a fairly crazy response in my opinion.
 
Please keep voting everybody.

We need to be able to customize the Web Deploy configuration file (because the Plesk default is not working correctly. The hostname should be the same as the server hostname and then put an SSL certificate in IIS for the server hostname under IIS > Management Service)
 
Back
Top