How to fix Error 2380 on Windows Server 2025 / Windows 11

by

Why This Error Happens

Error 2380 typically originates from SQL Server Reporting Services (SSRS) when the Report Server Web Portal attempts to load resources (scripts, images, or API calls) over an insecure HTTP connection while the parent page is being served over HTTPS. Modern browsers block this “mixed content” scenario for security reasons, causing the portal to fail silently or render incompletely. This is most commonly caused by a misconfigured URL reservation in rsreportserver.config, a reverse proxy/load balancer terminating SSL before traffic reaches the Report Server, or hardcoded HTTP references in custom report items.

Step-by-Step Resolution Guide

Step 1: Verify the Report Server URL Configuration

  • Open the Report Server Configuration Manager on Windows Server 2025.
  • Navigate to Web Portal URL and Web Service URL tabs and confirm both are bound to HTTPS, not HTTP.
  • Check the underlying XML at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\rsreportserver.config and ensure the <UrlRoot> key does not reference http:// when HTTPS is expected.

Step 2: Correct Reverse Proxy / Load Balancer SSL Termination

  • If using IIS ARR, NGINX, or Azure Application Gateway in front of SQL Server 2025, confirm that X-Forwarded-Proto headers are correctly set to https.
  • Update the <HostHeader> and <Secure> elements in rsreportserver.config to force SSRS to recognize the original HTTPS request.
  • Restart the SQL Server Reporting Services service via services.msc or run:
  net stop SQLServerReportingServices
  net start SQLServerReportingServices

Step 3: Scan for Hardcoded HTTP References

  • Search custom report definitions (.rdl files) and any embedded web parts for absolute URLs starting with http://.
  • Replace all static references with protocol-relative URLs (e.g., //yourserver/resource) or explicit https:// paths.
  • Clear the browser cache and Report Server temporary cache located at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin\Microsoft.ReportingServices.* if stale cached assets persist.

Step 4: Validate Certificate Binding on Windows Server 2025

  • Open IIS Manager (if applicable) or use PowerShell to confirm the SSL certificate is correctly bound to port 443:
  Get-ChildItem -Path Cert:\LocalMachine\My
  netsh http show sslcert
  • Re-bind the certificate to the Report Server endpoint if it is missing or expired.

Alternative or Verification Steps

  • Open the browser Developer Console (F12) on the Report Portal page and confirm no “Mixed Content” warnings appear in the Console tab after applying the fix.
  • If the error persists, temporarily disable the reverse proxy and connect directly to the Report Server via HTTPS to isolate whether the issue is proxy-related or SSRS-configuration-related.