NoMachine on Chrome OS 80

[Essem]

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.

[Tor]

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

[Brian Repko]

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.

[Brian Repko]

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.

[Tor]

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. 🙂

[MrWoo]

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?

[Brian Repko]

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).

[Tor]

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

@MrWoo no problem, we’ve added you to the list of testers. We’re solving some important store requirements before publishing the beta version, we’ll contact you as soon as it will be ready.

I’ve heard that it is slower and that the Android version is the preferred route (is that correct NoMachine?)

@Brian where did you hear that?! 😀 Unless who said it had some very specific issues (which we would be more than happy to investigate), you can expect the same level of performance on all platforms we support. Of course there are a lot of parameters that can affect the experience and sometimes tuning the configuration could be required.

[ender3600]

I was using the android app on my Chromebook but after ChromeOS updated to 80, it didn’t work anymore. As a work around I installed the Linux version of NoMachine on my Chromebook and that worked until ChromeOS updated to version 81. Now I don’t have a solution for my Chromebook. 🙁

[bryce.schober]

Any updates on the beta version’s ETA? Could I be added to the testers, @Tor?

[Tor]

Hi Bryce, we’ll add you to the list of testers. Since we’re working on a version 6.9 we’ve still some things to check, but we’re also evaluating to just update a 6.1 to distribute it for testing in a shorter time. I hope we can contact you all within a couple of weeks.

[Author]

Posts