• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Web deployment task failed

shinichi kudo

Basic Pleskian
Error Web deployment task failed. (The connection to the remote computer ("example.com") was established with the Web Administration Service, but authorization was not possible.

in onyx 17.8

is there any fix ?
 
You should collect more information about the problem. It is hard to say something just based on error you provided.

Troubleshooting Common Problems with Web Deploy
Here you can find recommendations on how troubleshoot problems with web deploy.

Please take a look in event viewer or WMsvc log file to analyze the problem, and then get back with some new details regarding the problem.

Thank you.
 
j1nbln

Link to the image

While publishing a .NET core application via Web Deploy in Visual Studio 2017, it fails with the following error:

Error Web deployment task failed. (The connection to the remote computer ("example.com") was established with the Web Administration Service, but authorization was not possible. Ensure that you are using the correct user name and password to connect to the website And that the credentials represent a user who is authorized to access the site. For more information, see: Web Deploy error codes.) Make sure the site name, username, and password are correct. If the issue is not resolved, please contact your local or server administrator. Error details: The connection to the remote computer ("example.com") was established with the Web Administration Service, but authorization was not possible. Ensure that you are using the correct user name and password, that the Web site to connect to, and that the credentials represent a user who is authorized to access the site. For more information, see: Web Deploy error codes. The remote server returned an error: (401) Unauthorized.

the user and password are correct , i found article at this link for this bud
Web Deploy publishing fails: ERROR_USER_UNAUTHORIZED

but only offer iis.php file replacement for version 17.0 and 17.5

my version is 17.8 ,, how i could fix this issue ?
 
> but only offer iis.php file replacement for version 17.0 and 17.5
> my version is 17.8 ,, how i could fix this issue ?
Fix provided in article is already included in 17.8

Please check logs here:
%SystemDrive%\Inetpub\logs\WMSvc
you can see 401 error on some lines.
for example, as explained in article:

Code:
2011-05-12 15:50:12 192.168.0.211 POST /msdeploy.axd site=default%20web%20site 8172 user1 192.168.0.203 - 401 1 1326 124

can you please show what you can see there. (you can replace exact site name and user login with asterisks)
 
when i use the website user

#Software: Microsoft Internet Information Services 10.0
#Version: 1.0
#Date: 2018-04-05 23:04:12
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2018-04-05 23:04:12 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 - **.**.158.245 - - 401 2 5 1889
2018-04-05 23:04:13 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 userxxx **.**.158.245 - - 401 2 0 396
2018-04-05 23:04:27 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 - **.**.158.245 - - 401 2 5 95
2018-04-05 23:04:27 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 userxxx **.**.158.245 - - 401 2 0 141
2018-04-05 23:04:50 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 - **.**.158.245 - - 401 2 5 93
2018-04-05 23:04:50 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 userxxx **.**.158.245 - - 401 2 0 141
2018-04-05 23:04:52 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 - **.**.158.245 - - 401 2 5 92
2018-04-05 23:04:52 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 userxxx **.**.158.245 - - 401 2 0 135
2018-04-05 23:11:53 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 - **.**.158.245 - - 401 2 5 90
2018-04-05 23:11:53 **.**.**.** HEAD /msdeploy.axd site=******.com 8172 userxxx **.**.158.245 - - 401 2 0 138



when i use windows user


#Software: Microsoft Internet Information Services 10.0
#Version: 1.0
#Date: 2018-04-06 22:39:13
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2018-04-06 22:39:13 **.**.**.** HEAD /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** - - 200 0 0 220
2018-04-06 22:39:13 **.**.**.** HEAD /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** - - 200 0 0 126
2018-04-06 22:39:56 **.**.**.** POST /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** - - 200 0 0 43185
2018-04-06 22:39:56 **.**.**.** POST /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** VSCmdLine:WTE1.0.0.0;sid=6c3dki97-542a-473d-a7e1-d5uu380eb31c;op=Sync - 200 0 0 42745
2018-04-06 22:39:56 **.**.**.** HEAD /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** - - 200 0 0 151
2018-04-06 22:43:03 **.**.**.** POST /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** - - 200 0 0 187175
2018-04-06 22:43:03 **.**.**.** POST /msdeploy.axd site=*****.com 8172 WinUser **.**.**.** VSCmdLine:WTE1.0.0.0;sid=6c3dki97-542a-473d-a7e1-d5uu380eb31c;op=Sync - 200 0 0 186681
 
We have additionally checked on clean Windows Server 2016 with Plesk 17.8 and publishing using Web Deploy from Microsoft Visual Studio is working correctly.
Let's try to investigate what is different in your environment.

You have created domain, enabled WebDeploy support for that domain in Plesk, downloaded .publishsettings file from Plesk and then imported these settings in your client?
By the way, which client you are using?
 
When i install new windows server 2016 then i make update first for security issues then install plesk... Plesk install not complete and stop

If i install windows then plesk then update windows it work but i have this issue with Microsoft deploy

I use visual studio 2017

...

Also want to ask if i could download and install the new version of. Net Core 2.x or this will break my services
 
> Plesk install not complete and stop
what do you mean? installation failed? is there anything in logs? what security update you are talking about? updates for Windows itself?

> Also want to ask if i could download and install the new version of. Net Core 2.x or this will break my services
you can install .NET Core 2.x, it shouldn't break any other services.
 
here's the log for the error after update

click here

about the .net core plesk now support version less than 2.2 , i want to install the latest version from microsoft is this will break any thing and i have to wait for official update from plesk or i could download the installer from microsoft and update it without problems ?
 
Last edited:
As I can see in logs real error is "Password is incorrect. At least 5 characters, no national characters".
Could you please try to install Plesk and specify password during installation with latin symbols. Have you really entered national symbols in password? We will check this problem on our side once again.

Regarding 2.2 version which is not yet shipped and supported by Plesk:
integration with .NET Core is mostly forward compatible. It means that you can install newer versions, and even if they will not be properly displayed in Plesk, they should work properly on your websites. .NET Core global module is integrated in IIS, so there is no need to enable .NET Core on website in Plesk specially. You just need to publish application made for .NET Core 2.2 on website and it should work properly after that.
 
about the log and the password, i tried 5 times to install plesk ,,

1st install plesk with national characters "it is a space and a Dot characters" after windows update ---> failed "i sent the log above"
2nd install plesk with without national characters after windows update ---> failed "same error but no password problem"
3rd install plesk with without national characters before windows update ---> Success
4th install plesk with without national characters after windows update ---> failed "same error but no password problem"
5th install plesk with without national characters before windows update ---> Success and continue for production and password changed to more strong one

i tried to install it in 4th time because i want system update and bare bone before installing anything, then start to install my services but plesk fails so i installed it first then updated the system but now i have problem in Web Deployment

this was at the beginning of this month and logs deleted after successful install in 5th time , i found this old log by chance in my files on external hard (i think i moved it unexpectedly ), other logs deleted unfortunately
 
Back
Top