• [6.10.0] VM connect to VNC via Browser fails because of Caching issue

    astronax

    By astronax

      • Annoyance

    Hi all,

     

    i just tried to setup a new ubuntu vm and used the integrated vnc feature as gpu. once setup i started the vm and tried to connect via the

    But it fails with "Failed to connect to server", it is not working event after a minute, is it possible that this functionality has broken with 6.10.0?

    the vm logs did not report an error, and I remember this to work greatly with 6.9.2? i have tested the vnc connect with an existing vm of mine, which does not connect anymore without chaning the configuration as well

     

    Steps to reproduce:

    • head to vms in gui /VMs
    • Add new VM
    • select Ubuntu (same issue with Windows, have not tested mroe)
    • set memory to 2gb, but gues this is not relavant
    • Machine is by default to q35-6.2
    • BIOS OVMF, by default
    • choose an ubuntu iso, i selected 22.04 lts desktop
    • head down to graphics card and choose "vnc"
    • VNC Driver QXL Best, should be default
    • save and start vm
    • connect via context menu via vnc remote and wait for the error message

     

    So regarding a new VM this is a showstopper, as i am not able even to select or choose any install parameters and therefore can not connect via ssh or anything else to the machine.

     

    PS: i am about to restart and upgrade to 6.10.1 but have to wait another hour to complete some work to do so, will also report back after safe boot, but i am 99% sure this is not a plugin issue (besides vm backups plugin, there is nothing related to vms nor gpu plugins installed)

     

    as pointed out this is due to browser caching using old files, i expected this be loaded correctly on an unraid version update, changed priority to annoyance

    casy-diagnostics-20220525-1602.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    Squid

    Even though there is cache-busting logic in place, many users find that they still have to clear the browser history (cookies etc) when upgrading to a new version and using VNC

    Link to comment
    astronax
    1 minute ago, Squid said:

    Even though there is cache-busting logic in place, many users find that they still have to clear the browser history (cookies etc) when upgrading to a new version and using VNC

    alright thats the case, it is a browser caching issue, thanks for point that out. i used a private browsing window and it worked again. there should be a flag for the browser to point out so cache has to reload.

     

    resolved but should not even occur when using correct caching settings?

    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires

    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control

    Link to comment
    Paul_Ber

    I upgraded weeks ago.

     

    Now today I cannot connect to my VM without using an incognito tab or window.

     

    This just started today.  Chrome Desktop.

     

    Edit:  Did this

    image.thumb.png.d07fcb61c96f1c266e1f5db7df809f85.png

    Edited by Paul_Ber
    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.