Workspace FQDN being truncated for wss

I managed to get an instance to start up completely yesterday - and I think I have everything set up as it should now. However, when I create a workspace and try to access it - I get a wss name resolution error. It looks like the FQDN of the instance is being truncated.

So our domain :
<prefix>.nodeable.io is being truncated to <prefix>.nodeable, which means the workspace Gitpod is trying to access has an invalid URL.

From the workspace list, I can see the URL is correct - with the missing .io at the end.

From what I can see, I have the domains set correctly in values.yaml and can see the workspace URL should be ok:

https://<doimain prefix>.nodeable.io/start/#f09e4970-9258-484d-baa1-1bf7af048446

And the resulting URL also looks ok:
https://f09e4970-9258-484d-baa1-1bf7af048446.ws.gitpod.k3s.scw.nodeable.io/

but I get this error in the browser console:

WebSocket connection to 'wss://gitpod.k3s.scw.nodeable/api/gitpod' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

Any idea if this is a bug and if there is a work-around, or if there is somewhere I may have misconfigured something?

That actually seems to be a bug in our code for domain names with more than 3 segments in front of the TLD. A host like gitpod.scw.nodeable.io works, gitpod.k3s.scw.nodeable.io not. Thanks for letting us know. I will investigate further and get back to you soon.

ok - thanks for finding that.

I will adjust my deployment to use a shorter URL for now.

1 Like