• 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.

Question .NetCore 3.1.5 on Plesk obsidian 18.0.27 - HTTP Error 500.0 - ANCM In-Process Handler Load Failure

Delari

New Pleskian
Hello, I did the installation of Product: Plesk Obsidian 18.0.27 Update #1 for windows to familiarize the panel with NetCore applications. created a test domain, and uploaded there an empty project created on NetCore, but when I open the site I see an error

HTTP Error 500.0 - ANCM In-Process Handler Load Failure

1.png - Displays the version of dotnet installed on the server

If I run the application locally on the server via cmd: dotnet.exe ./

2.png - local application launch

I checked the system requirements starting with Plesk Obsidian 18.0.26 should support .NET Core 3.1.3



It was also noticed if I explicitly state when publishing the application: Deployment mode: Standalone, Target runtime: win-x64 - application is work fine in IIS
But if I specify the deployment mode: Depends on the platform, Target runtime: Portable version - I get this error

3.png - installing components

The question is whether this is due to the fact that the current source version of Net Core 3.1.6, and the server supports, as I understand it 3.1.5 (see 3.png) ?

or somehow you can run a platform-specific portable version ?
 

Attachments

  • 1.png
    1.png
    53.5 KB · Views: 17
  • 2.png
    2.png
    46.5 KB · Views: 15
  • 3.png
    3.png
    64.4 KB · Views: 13
Back
Top