• [6.6.0,6.6.1] VM - noVNC - Failed to connect to server - Chrome Browser


    FlorinB
    • Closed Minor

    Today I just noticed that the built in web based VNC client does not connect to any of my VMs, however with a normal VNC client from other computers the VNC connection is ok.

     

    1057042192_Screenshot-29_9_201823_24_12.png.8a9874b25e866608616b1a31c02a3be2.png

     

    2114186774_Screenshot-29_9_201823_30_30.png.bf1501a66bb0a3dd40479f83bd3c76e8.png

     

    Does anyone else have the same issue like me? What is the reason and how can i fix it?

     

    Diag archive attached.

    node804-diagnostics-20180929-2332.zip

     




    User Feedback

    Recommended Comments

    Looks like it is a Google Chrome Browser issue. Tried with Firefox and Microsoft Edge and is working. 

     

    Is this intended to be like that for Crome or we can consider it a bug?1646483666_Screenshot-30_9_201823_40_47.png.5dc77a925070bb165f2082477a14d329.png

     

    Update: Cleared the Google Chrome cache completely (not happy with that...) and now it is working in Chrome Browser as well.

     

    Case closed. No bug.

    Edited by FlorinB
    Link to comment

    I get the exact same error in Chrome. I installed FireFox and still get the same error.

     

    I tried rebooting the Unraid server and then it magically started working again.

    Edited by frakman1
    update on reboot
    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.