Sure, we always can put up a knowledge base article with some troubleshooting tips if a certain error occurs. I’m hesitant to implement “special error handling” based on generic error messages because in our experience this can also lead to confusion when that error occurs for a completely different reason. This has happened before and in the end we regretted the customized error message because the situation completely changed over time.
FYI: we created a KB article with troubleshooting tips for VNC connections:
Hey Stefan! thanks for letting me know. And thanks for the KB! that would be very helpful for people that run into this again 