workspace config

vg33 — Wed, 15 Apr 2026 18:28:51 GMT

"I am on a Premium AWS trial workspace (dbc-30503d28-2210). I have two issues:
Personal access tokens are grayed out and I cannot generate them
My cluster cannot make outbound HTTP requests to external APIs (getting NameResolutionError when calling api.hubapi.com)
I am account admin and workspace is showing me as admin but workspace admin settings are all grayed out. How do I fix outbound internet access on my cluster?"

That's specific enough that a community engineer will know exactly what to do.

Re: workspace config

emma_s — Mon, 20 Apr 2026 16:11:23 GMT

Hi,

On the personal access tokens greyed out, you need to enable this in the workspace settings. (you'll need to make sure you're a workspace admin first). This is in the advanced setting under workspaces ettings.

Are you validating you're a workspace admin in the account admin portal? If you are definitely a workspace admin, I'd recommend a support ticket to someone who can look into this further.

For the other part,

Premium trial workspaces use the standard Databricks-managed VPC with NAT egress by default, so outbound to the public internet should work out of the box. A NameResolutionError usually points to one of:
- DNS resolution failing on the cluster itself — run nslookup api.hubapi.com or import socket; socket.gethostbyname('api.hubapi.com') from a notebook. If it fails, the cluster isn't reaching a DNS resolver.
- Cluster in a bad state — try restarting the cluster. Transient DNS issues sometimes clear on restart.
- Serverless vs classic compute matters — which are you using? Both have outbound internet by default, but the diagnosis paths differ if it's still failing.

- Custom VPC (if this workspace uses one) — check NAT gateway routing and security group outbound rules on port 443. Default trial workspaces don't use custom VPCs, so likely not relevant here.If nslookup works but the actual HTTP call fails, that's a different class of problem (likely firewall/proxy). Worth sharing the exact error message and stack trace, plus whether you're on serverless or classic compute.

I hope this helps

topic Re: workspace config in Get Started Discussions

workspace config

Re: workspace config