publish asp.net core project without suspend host RRS feed

  • Question

  • User338455301 posted

    i upload my .net core project in plesk 

    but when i change it and publish it again i must suspend the host is plesk then upload new .dll files and start it,

    i use ftp upload

    how publish and upload dll files without suspend host ?

    Monday, December 28, 2020 4:58 AM

All replies

  • User753101303 posted


    You could perhaps use App Offline file (app_offline.htm) | Microsoft Docs to gracefully stop current http requests before updating the site (and don't forget to remove this file once done).
    As pointed by this link, it is done by "Web Deploy" which is perhaps an available option according to the Plesk documentation.

    Monday, December 28, 2020 9:59 AM
  • User338455301 posted

    i use web deploy but i have a problem 

    i check more times my username and password but i have this error for username and password

    username : jahan-andish
    password: xxxxxxx

    with this username and information i log in to my plesk correctly
    but i have error in web deploy 

    Monday, December 28, 2020 12:05 PM
  • User753101303 posted

    When posting an image you may want to hide any information that could help a hacker.

    I'm not using Plesk but according to Cannot validate Web Deploy connection with additional Plesk Web User: ERROR_USER_UNAUTHORIZED (401) Unauthorized – Plesk Help Center you may need to add explicitely "subscription users" to allow access through Web Deploy?

    Monday, December 28, 2020 12:16 PM
  • User338455301 posted

    i have this user for login to plesk and work correctly but this user has problem for publish with web deply 

    what's problem ?

    by the way when i click validation connection i have this error for first time


    Tuesday, December 29, 2020 7:41 AM
  • User753101303 posted

    Seems Securing Plesk and the Mail Server With SSL/TLS Certificates | Plesk Obsidian documentation ie Plesk is using currently a self signed certificate which gives warning #2.

    In addition the certificate is intended to secure a given site name but is used for another site name (for example using a forums.company. com certificate to secure the blogs.company.com site) which shows #1.

    Note sure how much control you have on that with your hosting service. Make sure first it happens only on the admin side as an end user browsing on a misconfigured https site could be wary and just stop here.

    Tuesday, December 29, 2020 1:26 PM