Configured privacy settings disallow access for workspace <workspace-id> over your current network.

Question

Configured privacy settings disallow access for workspace <workspace-id> over your current network.

John Aherne 151

Hi All,

We have a couple of Databricks workspaces that are deployed with secure access - basically you can only log in when you are within the network, However, I am running into a problem where I sometimes get this error:

“Configured privacy settings disallow access for workspace <your-workspace-id> over your current network. Please contact your administrator for more information”

If I open my browser for the first time, it will successfully log in. However, if I leave it for a while, my session will timeout and when I try to reauthenticate I will get that error.

If I am working on other things in my browser and add a new tab to log in, I will get the error.

When I get the error, nothing will fix it unless I close all browser instances (including InPrivate windows) and open a brand-new browser.

This problem affects some others on the team, but there are people who do not have the issue at all.

I realize that somehow subsequent log in attempts are going over public networks, but I have no idea how to properly identify or diagnose what is happening.

Any suggestions on where to look or how to figure out what is causing this?

Thanks!

Martijn Staps 0 Reputation points

2023-12-08T07:53:53.1033333+00:00

Did you manage to get this fixed? We've tried the suggested changes, but it doesn't work. Azure Support doesn't seem to care, they think it's related to a 6-hour session/login time-out.

However, the issue randomly occurs, sometimes even within 30 minutes of inactivity. We keep the Databricks tab open in the browser and sometimes (not all the time), when we come back to the tab with our Databricks workspace we get this issue.

Configured privacy settings disallow access for workspace <ID> over your current network. Please contact your administrator for more information.

I think it's related to some sort of webbrowser cookie, we need to close our browser in order to re-authenticate. A page refresh doesn't help, but does work when we clear our cookies -> F5 (page refresh) and re-authenticate.

It's a very ennoying issue because during the day we keep switching around in the browser for multiple applications. For now we're opening Databricks in the Edge browser and do our normal browsing in Chrome so we don't need to kill all our tabs.

Any ideas?
Felippe Borges 96 Reputation points

2024-11-11T15:08:53.56+00:00

Hello all!!!

This is a DNS issue. You should configure your DNS to resolve xxxxxxxx..azuredatabricks.net address.

The workspace has an internal IP address and when you try to access it without the DNS record created in your DNS server, your traffic goes to the public IP address from the workspace.

After you create the DNS A record you will be able to access it.

1 answer

Your answer

Martijn Staps 0 Reputation points

2023-12-08T07:53:53.1033333+00:00

Did you manage to get this fixed? We've tried the suggested changes, but it doesn't work. Azure Support doesn't seem to care, they think it's related to a 6-hour session/login time-out.

However, the issue randomly occurs, sometimes even within 30 minutes of inactivity. We keep the Databricks tab open in the browser and sometimes (not all the time), when we come back to the tab with our Databricks workspace we get this issue.

Configured privacy settings disallow access for workspace <ID> over your current network. Please contact your administrator for more information.

I think it's related to some sort of webbrowser cookie, we need to close our browser in order to re-authenticate. A page refresh doesn't help, but does work when we clear our cookies -> F5 (page refresh) and re-authenticate.

It's a very ennoying issue because during the day we keep switching around in the browser for multiple applications. For now we're opening Databricks in the Edge browser and do our normal browsing in Chrome so we don't need to kill all our tabs.

Any ideas?
Felippe Borges 96 Reputation points

2024-11-11T15:08:53.56+00:00

Hello all!!!

This is a DNS issue. You should configure your DNS to resolve xxxxxxxx..azuredatabricks.net address.

The workspace has an internal IP address and when you try to access it without the DNS record created in your DNS server, your traffic goes to the public IP address from the workspace.

After you create the DNS A record you will be able to access it.

Answer 1

QuantumCache 20,366 Moderator

Hello @John Aherne,

Thanks for reaching on this forum.

Indeed this issue is frustrating, Couple of things to consider to troubleshoot :

Is there any IP Address change while you're using Databricks. You can use a site like whatismyip.com to see your current IP address. If it's changing over time or when you open a new browser tab, that could be why you're getting the error.

We can also check of VPN connectivity: Some VPNs can cause your IP address to appear differently to Databricks, which could cause the error.

You may want to disable Browser extensions, or You could try connecting from a different network and see if the problem persists.

You can check the status of Azure services and regions on the Azure status page. please let us know and we can help you further.

John Aherne 151 Reputation points

2023-06-14T13:15:03.36+00:00

You are a life saver!!

After months of dealing with this issue, I have not encountered it at all in the last few days.

I doubt I will find out exactly what was changed, but I am guessing it was some sort of dns issue.
John Aherne 151 Reputation points

2023-06-14T13:17:18.3+00:00

It suddenly started working. Unfortunately I do not know what was changed, but my suspicion was a dns problem.
QuantumCache 20,366 Reputation points Moderator

2023-06-14T19:20:06.29+00:00

Hello @John Aherne , Glad that the issue was resolved.

please click "Accept Answer" and upvote it. So that we can close this thread.
Please contact us any time if you need further help on this forum!
John Aherne 151 Reputation points

2023-06-15T17:05:48.94+00:00

Aaand it's back again :(
John Aherne 151 Reputation points

2023-06-15T17:11:09.25+00:00

There are no address changes that I am aware of. We connect via zScaler VPN and the internal network address is the same when I get the issue as when I restart my browser to connect again.

It's a secure Databricks workspace, so the connection should go over our internal network.

I disabled all browser extensions, but it didn't help.

The workspace is up and running as others are able to connect and are working in there while I get the problem.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
QuantumCache 20,366 Reputation points Moderator

2023-06-16T17:27:49.7566667+00:00

Hello @John Aherne, Just checking in if you had a chance to send us an email for offline support?
John Aherne 151 Reputation points

2023-07-11T00:38:25.9133333+00:00

Ah, sorry! Ended up using a separate browser (chrome) for databricks only - This seems to be working, and anecdotally this seems to fix it for others too. Not sure why it would work in Chrome but not Edge.

Share via

Configured privacy settings disallow access for workspace <workspace-id> over your current network.

1 answer

Your answer