• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by wst

  1. W

    Issue Error code 1: Can't detect .NET version when requesting Let's Encrypt cert

    Now I'm having the same on a subdomain, but the fix isn't working. also when disabling and enabling ASP.NET support and as the fix suggested, the No managed code is reset in IIS --> result asp.net core 5.0 site crashes. I got it working by: first disabling asp.net support enabling asp.net...
  2. W

    Issue Error code 1: Can't detect .NET version when requesting Let's Encrypt cert

    Ok @IgorG this fixed the issue and cert will be automatically renewed. Thanks. Still wondering where the ASP.NET Core support option is.
  3. W

    Issue Error code 1: Can't detect .NET version when requesting Let's Encrypt cert

    ok i'll try that. Why is there "Microsoft ASP support", "Microsoft ASP.NET support (Version 4.8.0)" but where is the ASP.NET Core support option? As Plesk supports ASP.NET Core and this differes a lot from ASP or ASP.NET...
  4. W

    Issue Error code 1: Can't detect .NET version when requesting Let's Encrypt cert

    I have an asp.net core 3.1 website and when trying to renew let's encrypt with www options enabled (exept mail acess (not secured) (IMAP, ...)) I get this message. If I click "ASP.NET Settings" for the domain I get
  5. W

    Issue Configuration to host ASP.NET Core 3.1 website on Plesk (Windows / IIS)

    Hi, I'm having troubles migrating an existing asp.net core 3.1 website with SQL Server database to a Windows server with Plesk. (sqlexpress and iis are enabled). Microsoft .NET Core 3.1.11 - Windows Server Hosting bundle is installed. Microsoft .NET Core Runtime - 3.1.11 (x64 && x86) are...
See more
Back
Top