dc2008

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Htd.cfg redirect #19404
    dc2008
    Participant

    Yep works great, i had to make a very slight change otherwise i got 2 “//” mid url:

     

     RewriteRule ^/?(.*)/$ /$1/nxwebplayer?desktop [L,R]
    
    to
    
     RewriteRule ^/?(.*)/$ $1/nxwebplayer?desktop [L,R]

     

    Thank you for your help

    in reply to: Htd.cfg redirect #19361
    dc2008
    Participant

    Thanks for your response.

    Yes that’s great i am looking for the desktop.nxs file to load.

    I have changed the line exactly as you advise, restarted nxserver but the redirect is still just taking me to https://example.com:4443/nxwebplayer

    Were you able to get this working? Is there any other config i have to update or refresh?

    Any help appreciated

    dc2008
    Participant

    Hi,

    Thanks for the TR link – it doesn’t appear to relate directly to my issue but I will assume you have general issues with WebRTC connections via web connections and that my experience is another symptom of your known issue.

    I notice the TR has a “minor” impact status. We are evaluating NoMachine to provide clientless browser access to Linux desktops – currently my experience is that if I enable WebRTC, the connection dies after 30 seconds-5 minutes so effectively unusable in a production environment. My understanding is that enabling WebRTC is key to testing other performance and feature tweaks i.e. sound/H264 compression, etc.

    Given this experience is there a chance this problem could be reclassified with an impact of greater than “minor”? Or perhaps an ETA or the chance to test a beta release?

    Appreciate your assistance.

     

    dc2008
    Participant

    Thank you so much for looking into this.

    Freezing Issue replicated on:
    Firefox 61.0.1 (64-bit)
    Chrome Version 67.0.3396.99 (Official Build) (64-bit)
    Opera 54.0.2952.54

    Connection using VP8 (WebRTC), audio Opus 48khz stereo

    I am glad you are able to replicate this problem – not wanting to confuse this thread with too many variables but i have carried out a fair bit of testing and replicated freezing with various STUN providers (public, local and third party), with/without h264 encoding (compiled from your web download library), different linux distros, NM Enterprise Desktop and NM Workstation products etc (all this testing was from Firefox though). I also experience the freeze outside of youtube videos etc, ie normal browsing or OS use will eventually result in a freeze. Are you able to provide an ETA for your fix or a ticket number for me to track?

    dc2008
    Participant

    I have been continuing my research into this frozen screen when WebRTC is enabled.

    I built a fresh install of NM Workstation on a server (in a hosting datacenter) directly connected to the internet so ruling out NAT issues completely.

    I load up a classic (non WebRTC) web session virtual desktop and run a YouTube video (without sound) without issue.

    Then I enabled WebRTC (using stun1.l.google.com), restart nxserver. Connect to a virtual desktop. load up a YouTube video and after a minute or so, the desktop freezes again.

    Is this a performance issue when using WebRTC? Can you guys recreate a working webplayer/webrtc virtual desktop and run video for an extended period without freezing?

    Any optimization suggestions?

Viewing 5 posts - 1 through 5 (of 5 total)