Hey @hofmannj,
I took a look at this. What is strange is that it works fine when debugging locally on my system, but not once it gets pushed to our backend.
It looks like it has something to do with the name resolution. It is taking a long time (~30 seconds). It is not clear why, at this point.
Immediate workaround:
You can use the IP address of your NAS instead of the hostname. You will need to disable certificate validation since the names will not match.
Future:
I have added a few fixes for the next release. These will address the previous certificate validation error you were seeing and will also allow you to continue connecting even if our backend has an issue. The latter fix will allow you to use the desktop client, which does not exhibit the same timeout issue I am seeing on the backend.
I’ll keep poking around, but this is a tricky one. I am only seeing this behavior for your particular host… it is really odd.