http.sys not listening on port 443 for some reason my certificate is not working for ssrs

Anonymous
2026-01-07T07:33:12.15+00:00

Hi,

I m back again my http.sys is not listening on 443 and 80 at all curl is failing , i can see my certificate added but its not working due to nothing listening on 443,

Why this keeps happening it should be listening when we add a cert for 443 port but for some reason it does not integrate with ssrs config, can you suggest some simple way to overcome this every time,

By the way this time in a different environment i m testing certificate with SAN not a standalone cert for ssrs service so if there is any extra steps needed please suggest?

I can share the logs, command output as well and i m not able to open a support ticket so please help here

Thanks

SQL Server Reporting Services
SQL Server Reporting Services

A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.

0 comments No comments

Answer recommended by moderator
Shruti Dhruv 875 Reputation points Microsoft External Staff Moderator
2026-01-08T09:46:47.8533333+00:00

Hi Shahzeena ,

Welcome to Microsoft Q&A Forum!
You can check for these steps for troubleshooting-

  1. Check current bindings
    Run : netsh http show sslcert
    If nothing is listed for 0.0.0.0:443 or your IP:443, then HTTP.sys is not listening.
  2. Verify SSRS URL reservations
    In RSReportServer.config, confirm URLs match the SAN names.
  3. Finally, restart SSRS service after binding.

Additionally, try going through this link to troubleshoot the issue.
https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/iis/www-authentication-authorization/troubleshooting-ssl-related-issues-server-certificate

Hope this helps!
Thank You

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. AI answer

    2026-01-07T07:33:24.1133333+00:00

    If your http.sys is not listening on ports 443 and 80, it could be due to several reasons. Here are some steps you can take to troubleshoot the issue:

    1. Check SSL Configuration: Ensure that your SSL certificate is properly configured with http.sys. You can check the SSL configuration by running the command:
         netsh http show ssl
      
      Look for the IP:Port pair and ensure that the certificate hash is correctly set. If the certificate hash is NULL or has an invalid GUID, that could be the issue.
    2. Add URL ACL: If you are running IIS Express or a similar service, you may need to add a URL Access Control List (ACL) to allow it to use port 443. You can do this with the following command (run as an elevated prompt):
         netsh http add urlacl url=https://localhost:443/ user=everyone
      
      This command allows the specified user to access the URL on port 443.
    3. Check for Conflicts: Ensure that no other application is using port 443. You can check this by running:
         netstat -aon | findstr :443
      
      This will show you if any other process is listening on that port.
    4. Firewall Settings: Make sure that your firewall is not blocking port 443. You may need to create an inbound rule to allow traffic on this port.
    5. IIS Configuration: If you are using SQL Server Reporting Services (SSRS), ensure that the SSRS configuration files are correctly set up to use the SSL certificate. You may need to specify the certificate in the SSRS configuration manager.
    6. Testing with SAN Certificate: Since you mentioned using a Subject Alternative Name (SAN) certificate, ensure that the SAN entries are correctly configured and that the hostname you are using matches one of the SAN entries in the certificate.

    If you continue to experience issues, consider checking the logs for any specific error messages that might provide more insight into the problem.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.