NoMachine on Chrome OS 80

Forums / NoMachine for Mobile / NoMachine on Chrome OS 80

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #25873
    AvatarEssem
    Participant

    Hello,

    I have been using the NoMachine Android app version 6.1.9 on my Chromebook and it has been working well. However, I recently updated to Chrome OS 80, and ever since this update I have been unable to connect to my Windows 10 server on version 6.9.2. Whenever I try to connect, it freezes on the “Connecting to <IP address>…” screen and eventually crashes. How would I fix this? Thanks in advance.

    #25877
    AvatarTor
    Contributor

    Hey there. We’re working on a version to fix this problem. If you enable the developer mode we could also send you an APK version including the fix, otherwise subscribe to this report to be alerted when we’ll release it:

    https://www.nomachine.com/TR10Q09450

    #25959
    AvatarBrian Repko
    Participant

    Just bought an ASUS C434 Flip Chromebook to test using Chromebooks for work and have the same issue.

    I’m using NoMachine Android 6.1.9 and this is a new Chromebook that upgraded to Chrome OS 80.0.3987.137

    Everything in terms of setup seems to work but when I try to connect (to Ubuntu EC2 via VPN), I get the same.

    It freezes on “Connecting to <session-name>” and then eventually I get the “this application is unresponsive – wait, close, or report.

    I’ve signed up for email notification on the TR and would be more than happy to try the APK and load that in developer mode.

    #25960
    AvatarBrian Repko
    Participant

    I forgot to add – I am connecting via a key file (.pem) and not a password. Not sure if the permissions on the .pem file matter (as I had to copy it to where it could find it). Same .pem file works for regular ssh when properly protected.

    #26016
    AvatarTor
    Contributor

    Hi Brian, thank you for the report. The problem is not related to the frontend, but to the OS app sandbox getting stuck while the app is connecting to the remote desktop. We had to work on our build details and shipped architectures to solve it, but this change required many more aspects to be tuned, improved or changed completely, so it is taking more time than expected. I see you’d like to install a testing APK in developer mode, so we’ll contact you soon. 🙂

    #26345
    AvatarMrWoo
    Participant

    Hi – joined the forum to comment to this topic.

    Having the same issue on Pixel Slate, is it possible to be provided the APK to test as well?

    #26386
    AvatarBrian Repko
    Participant

    Just a note that I was able to run the Linux version and that ran great. I’ve heard that it is slower and that the Android version is the preferred route (is that correct NoMachine?). I’ve not been running it all day everyday however so I can’t speak to it’s performance (I’m waiting for a mouse that works to be delivered to the house for that).

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

You must be logged in to reply to this topic.