Getting “site can’t be reached” error when trying to access workspace

Check if the workspace has an entry in your custom DNS server.

Written by kingshuk.das

Last published at: June 27th, 2025

Problem

When you try to access your workspace, you receive a server error saying the site can’t be reached. The following image shows the error from the browser UI. 

 

 

Cause

The workspace is using a custom DNS that does not match the hostname IP address.

 

Solution

  1. First, obtain the custom DNS CIDR from your cloud console.  
  2. From the terminal, run nslookup on your hostname. 
%sh
nslookup  <hostname>
  1. Next, ensure the hostname is resolving to the IP address matching the DNS server records you checked in step 2. 
  2. Ensure your IP and the configured IP from the custom DNS server match. Otherwise, point your host to the proper DNS classless inter-domain routing (CIDR).