Restart the service from your computer's "Services" menu or Task Manager.
Ensure your computer’s system clock is accurate, as incorrect times often trigger SSL verification failures.
Localhost Refused to Connect Error: 5 Confirmed Ways to Fix It - Hostinger 21 Jan 2026 — https localhost11501 verified
Are you trying to a local HTTPS server, or are you troubleshooting a specific error on this port?
Ensure the backend application (e.g., the digital signature service or local server) is actually running in your system tray or Task Manager. Firewall Rules: Restart the service from your computer's "Services" menu
When an ASP.NET Core app runs on a random port (sometimes 11501), it automatically uses this trusted certificate. Visual Studio or dotnet run will show “Verified” in the browser.
The word "verified" is the key to understanding the modern web's security model. In a traditional HTTP connection (unencrypted), there is no verification of identity; anyone on your network could, in theory, intercept the data. When you see the word "verified" (often accompanied by a padlock icon in the browser’s address bar), it means the connection is: Ensure the backend application (e
Cookies marked Secure can only be transmitted over HTTPS. If your frontend on https://localhost:3000 needs to call an authentication API on https://localhost:11501 , both must be HTTPS with valid certificates. The “verified” status ensures the browser sends those cookies.