• 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!
  • 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 Asp.Net Core Docker Container that uses HTTPS

Brandon Turpin

Basic Pleskian
I have a docker container that is running an asp.net core website. It works just fine and I have the docker proxy rules to use the site for the domain name. The issue I have now though is that when I update my asp.net website to have https and use port 443, I now have port 80 and port 443 being used. I can only use one on the proxy rules and if I choose port 443 it does not work. If I choose port 80 it errors out saying it has too many redirects. I am not sure how to use the docker container and proxy rules for a site that is https.
 
Back
Top