Troubleshooting 'Can't Reach This Page' Errors in SQL Server Management Studio 19

Updated: 29 Jun, 2025 • 0 • min read

Table of Contents

Troubleshooting SSMS Errors

Connecting to SQL Server or Azure SQL resources using Microsoft Entra authentication within SQL Server Management Studio (SSMS) is a common practice, providing enhanced security and centralized identity management. However, users, particularly those operating within highly secure or restricted network environments, may encounter authentication errors that prevent successful login. These errors often manifest as browser-related issues, specifically “Can’t reach this page” or “Unsupported browser” messages, stemming from how SSMS interacts with the system’s web browser to complete the authentication flow.

Understanding the underlying cause is key to resolving these connectivity problems. Microsoft Entra authentication, when used by desktop applications like SSMS, typically utilizes an interactive flow. This involves SSMS opening a web browser window, directing the user to the Microsoft Entra login page, and then redirecting back to a specific local address (a localhost URL with a dynamic port) after successful authentication to capture the necessary tokens. Issues arise when this browser interaction or the subsequent redirection and communication back to SSMS are blocked or misconfigured, especially in environments with strict network policies, proxy servers, or modified default browser settings.

Let’s delve into the specifics of the errors encountered in different SSMS versions and the detailed steps required to address them. The behavior related to browser interaction has changed between SSMS versions, necessitating different approaches depending on which version you have installed. It is crucial to identify your SSMS version before attempting any resolution steps to ensure you apply the correct fix for your specific scenario.

‘Can’t Reach This Page’ Error in SSMS 19.1 and Later¶

Users of SQL Server Management Studio version 19.1 and subsequent releases might encounter a frustrating error message when attempting to authenticate using Microsoft Entra ID (formerly Azure Active Directory). Instead of the expected login prompt completing successfully, a browser window or embedded browser component displays an error indicating that a specific local address cannot be reached. This typically presents as a standard web browser error page.

The error message usually states:

Can’t reach this page

Make sure the web address http://localhost:55555 is correct

Search for this site on Bing

Refresh the page

More information

There was a temporary DNS error. Try refreshing the page.
Error Code: INET_E_RESOURCE_NOT_FOUND.

This error specifically references a localhost address on a dynamically assigned port (like 55555), which is the address SSMS instructs the browser to redirect to after Microsoft Entra completes the user authentication process. SSMS is listening on this local port to capture the authentication response containing the necessary security tokens. The INET_E_RESOURCE_NOT_FOUND error suggests that the browser, for some reason, cannot establish a connection to this localhost address, preventing SSMS from receiving the authentication callback. This could be due to various factors interfering with local loopback connections or how the browser handles redirects to non-standard URIs in a restricted environment.

Cause of ‘Can’t Reach This Page’ Error¶

The primary reason for the emergence of the “Can’t reach this page” error in SSMS 19.1 and later versions is a deliberate change in the application’s default behavior regarding browser usage. Starting with SSMS 19.1, the setting Use system default web browser located under Tools > Options > Azure Services was changed to default to True. This means SSMS now preferentially attempts to use your system’s configured default web browser to perform the interactive parts of the Microsoft Entra authentication flow.

This change was implemented largely in response to user feedback and the retirement of Internet Explorer in June 2022. Earlier versions of SSMS that relied on older embedded browser components, sometimes tied to Internet Explorer, were presenting users with “Unsupported browser” messages during authentication, as their internal components were no longer compatible with modern Microsoft Entra security requirements. By defaulting to the system’s external browser, SSMS aimed to leverage a fully supported, up-to-date rendering engine for the authentication pages. However, in tightly secured environments, launching an external browser and allowing it to communicate back to a dynamic localhost port can be problematic, potentially being blocked by security software, group policies, or proxy configurations that don’t allow loopback connections for external processes initiated this way.

Resolution for ‘Can’t Reach This Page’¶

Resolving the “Can’t reach this page” error typically involves adjusting SSMS settings or ensuring your system’s browser configuration is compatible with the authentication flow. Two main methods can be employed:

Method 1: Configure SSMS Browser Setting

This method involves reverting SSMS to use an embedded browser component rather than relying on the external system default browser. This can often bypass restrictions that apply specifically to external browser processes.

Open SQL Server Management Studio.
Navigate to the Tools menu.
Select Options.
In the Options dialog, expand Azure Services.
Select Miscellaneous.
Find the setting Use system default web browser.
Change its value from True (the default in 19.1+) to False.
Click OK to save the changes.
Restart SSMS.
Attempt to connect using Microsoft Entra authentication again.

Setting this option to False tells SSMS to use its built-in browser control for the authentication process. This embedded control runs within the SSMS process space, which might have different permissions or less stringent restrictions applied by network security software compared to an external browser process. This often allows the localhost callback to function correctly within the confines of the SSMS application.

Method 2: Set and Configure System Default Browser

If Method 1 is not desired or doesn’t resolve the issue, ensuring your system’s default browser is properly configured and capable of handling the authentication redirect is the next step. This is particularly relevant if certain browsers are restricted or misconfigured in your environment.

Ensure you have a modern, supported web browser installed (like Microsoft Edge, Chrome, Firefox).
Set one of these supported browsers as your system’s default browser. The steps vary slightly depending on your operating system and preferred browser. For example, in Windows, you can usually do this via “Default apps” in System Settings.
Crucially, ensure the default browser is not being heavily restricted by group policies or security software that might block redirects to localhost or dynamic ports. Check browser settings related to security, pop-ups, and redirects.
In Microsoft Edge specifically (as mentioned in the original text), you can go to Settings, navigate to the Default browser page, and explicitly specify Microsoft Edge as the default. While this is part of step 2, sometimes verifying this setting within the browser itself is helpful.
After setting/verifying the default browser, restart SSMS and attempt the Microsoft Entra authentication again.

This method relies on the external browser correctly receiving the redirect from Microsoft Entra ID and then being able to successfully connect back to the localhost address on which SSMS is listening. If network security or browser policies prevent this loopback connection for external processes, this method may still fail, making Method 1 a more reliable solution in heavily restricted environments.

‘Unsupported Browser’ Error in SSMS 19.0.2 and Earlier¶

Prior to the changes introduced in SSMS 19.1, users running SSMS versions 19.0.2 and earlier often encountered a different browser-related error during Microsoft Entra authentication. This error explicitly stated that the browser being used was unsupported or outdated.

The error message displayed was typically:

Keep your account secure

Your organization requires that you set up the following authentication methods to prove your identity.

Update your browser

Your browser is not supported or up-to-date. Try updating it, or else download and install the latest version of Microsoft Edge.

You could also try to access https://aka.ms/mysecurityinfo from another device.

This message appeared because older versions of SSMS, when configured to not use the system’s default browser (which was the default setting in these older versions), relied on an embedded browser control. This control was often based on components tied to Internet Explorer, which became unsupported by modern web standards and security protocols used by Microsoft Entra ID following IE’s retirement. Therefore, the Microsoft Entra login page would detect this embedded control as an outdated and unsupported browser, blocking the authentication process for security reasons.

Resolution for ‘Unsupported Browser’¶

To resolve the “Unsupported browser” error in SSMS 19.0.2 and earlier versions, the goal is to force SSMS to use a modern, supported browser, which means using the system’s default browser instead of the outdated embedded control. The resolution steps are essentially the opposite of Method 1 for the 19.1+ error, reflecting the change in default behavior and the underlying issue being addressed.

Method 1: Forcing SSMS to Use System Default Browser (SSMS 19.0.2 and earlier)

This method involves changing the SSMS setting to leverage the system’s default web browser, which is expected to be a modern and supported application.

Open SQL Server Management Studio (version 19.0.2 or earlier).
Navigate to the Tools menu.
Select Options.
In the Options dialog, expand Azure Services.
Select Miscellaneous.
Find the setting Use system default web browser.
Change its value from False (the default in 19.0.2-) to True.
Click OK to save the changes.
Restart SSMS.
Attempt to connect using Microsoft Entra authentication again.

By setting Use system default web browser to True, you instruct SSMS to offload the authentication webpage rendering and interaction to your operating system’s configured default browser. Assuming your system’s default browser is a modern, supported application (like Edge, Chrome, Firefox), it will be recognized by the Microsoft Entra login page, allowing the authentication flow to proceed correctly.

Method 2: Set and Configure System Default Browser

Similar to the resolution for the “Can’t reach this page” error, ensuring your system has a modern default browser properly configured is essential when SSMS is set to use the system default. This method complements Method 1.

Ensure you have a modern, supported web browser installed (like Microsoft Edge, Chrome, Firefox).
Set one of these supported browsers as your system’s default browser. Configure this via your operating system’s settings (e.g., “Default apps” in Windows).
In Microsoft Edge, access Settings, navigate to the Default browser page, and specify Microsoft Edge as the default browser, if that is your chosen application.
Verify that the chosen default browser is not being blocked from opening or handling redirects by other system settings or security software.
After setting the default browser, restart SSMS and try the Microsoft Entra authentication again.

This method ensures that when SSMS calls upon the system’s default browser (as configured in Method 1 for older SSMS versions), it invokes a compatible application capable of successfully completing the Microsoft Entra authentication sequence.

More Information and General Troubleshooting¶

It is important to understand that these settings are applied on a per-installation basis for SQL Server Management Studio. There is no global option or group policy setting within SSMS itself that can configure this behavior for all users across an organization. Each SSMS installation needs to be configured individually, which is a key point for system administrators managing multiple developer or user machines.

The Microsoft Entra authentication flow in applications like SSMS follows a standard pattern, often utilizing the Authorization Code Flow with PKCE. This involves:
1. SSMS initiates the flow and redirects the user’s browser to the Microsoft Entra login endpoint.
2. The user authenticates in the browser.
3. Microsoft Entra redirects the browser back to a pre-configured redirect URI. For desktop applications like SSMS using interactive flows, this redirect URI is often a localhost address on a dynamic port (e.g., http://localhost:55555/auth).
4. SSMS is listening on this specific localhost address and port. When the browser redirects back, SSMS intercepts the request, extracts the authorization code or tokens from the URL parameters, and then uses these to acquire access tokens to connect to the requested SQL resource.

The errors discussed (“Can’t reach this page”, “Unsupported browser”) occur during steps 3 and 4. The “Unsupported browser” error happens at step ⅔ if the browser component is too old. The “Can’t reach this page” error happens at step ¾ if the browser cannot connect back to the localhost address SSMS is listening on.

In restricted environments, several network and system configurations can interfere with this flow:

Proxy Servers: Proxy configurations can sometimes interfere with localhost loopback connections, especially if the proxy is configured to handle all network traffic. Ensure that localhost traffic on dynamic ports is bypassed by any active proxy.
Firewalls: Local or network firewalls might block outbound connections initiated by SSMS or the default browser, or crucially, incoming connections to the dynamic localhost port where SSMS is listening. Explicit rules might be needed to allow these connections.
DNS Resolution: While localhost should theoretically bypass DNS, sometimes complex network setups or DNS proxy configurations can impact its resolution or the handling of requests directed to it. The INET_E_RESOURCE_NOT_FOUND error specifically mentions a temporary DNS error, which might point to underlying network stack issues, even if not directly DNS related for localhost.
Security Software: Antivirus, endpoint protection, or data loss prevention (DLP) software can sometimes interfere by treating the browser launching or the localhost callback as suspicious activity. Temporarily disabling such software (under strict supervision and policy) can help diagnose if it is the root cause.
Browser Configuration: Beyond setting the default, specific browser security settings, installed extensions, or group policies applied to the browser can inadvertently block redirects or communication with non-standard URIs like localhost:port.

If the specific SSMS options don’t immediately resolve the issue, troubleshooting these underlying network and system configuration points is essential. Verify that you can access login.microsoftonline.com from the machine. Check active network connections and listening ports when SSMS attempts authentication. Use browser developer tools to inspect the redirects happening during the login flow.

Here is a simplified representation of the SSMS Microsoft Entra authentication flow using Mermaid syntax:

```mermaid
sequenceDiagram
participant User
participant SSMS
participant SystemBrowser
participant MicrosoftEntraID

User->>SSMS: Initiate Connect (Entra Auth)
SSMS->>SystemBrowser: Launch Browser to Microsoft Entra Login Page
SystemBrowser->>MicrosoftEntraID: Request Login Page
MicrosoftEntraID->>SystemBrowser: Display Login Page
User->>SystemBrowser: Enter Credentials & Authenticate
MicrosoftEntraID->>SystemBrowser: Redirect to http://localhost:PORT/auth
SystemBrowser->>SSMS: Attempt Connection to localhost:PORT
alt Successful Callback (SSMS 19.1+ Use Default=True, SSMS 19.0.2- Use Default=True)
    SSMS->>SystemBrowser: Receive Callback Request
    SSMS->>MicrosoftEntraID: Exchange Code for Tokens (Backend)
    MicrosoftEntraID->>SSMS: Provide Access Tokens
    SSMS->>User: Authentication Successful, Connect!
else Callback Failed ('Can't reach this page')
    SystemBrowser-->>User: Display 'Can't reach this page' Error
end
alt Unsupported Browser (SSMS 19.0.2- Use Default=False)
    SSMS->>SSMS: Use Embedded Browser
    SSMS->>MicrosoftEntraID: Request Login Page (from Embedded)
    MicrosoftEntraID-->>SSMS: Display 'Unsupported browser' Error
end

```

This diagram helps visualize the points where the process can fail based on the browser configuration or the ability to reach the localhost callback address.

Consider creating a simple table to summarize the recommended SSMS setting based on version:

SSMS Version	Default “Use system default web browser”	Recommended Setting for Entra Auth Issues in Restricted Environments	Primary Error Addressed by Recommended Setting
19.1 and later	True	False (Use embedded browser)	‘Can’t reach this page’
19.0.2 and earlier	False	True (Use system default browser)	‘Unsupported browser’

Adhering to these version-specific recommendations for the SSMS browser setting, combined with a thorough check of network configurations, firewall rules, and security software, should help resolve the common browser-related authentication errors encountered with Microsoft Entra ID in SQL Server Management Studio. Remember that testing changes incrementally and verifying system settings after applying resolutions is crucial for successful troubleshooting.

Were you able to resolve the issue using the methods described? Do you have unique network configurations that might be contributing to these problems? Share your experiences and further questions in the comments below!

Computacionvinchi