Forum Replies Created
-
Posts
-
Hi Gideon, thank you for your report. Initially I thought your issue was caused by a missing access files permission, but while troubleshooting it we’ve found something wrong. It seems our framework gets a wrong answer when querying Android about what is the root folder the app has access to, and this happens not just in the sandbox but in any folders tree. We’re still investigating it, but we’ll be sure to include a fix in the incoming app maintenance.
Until then you can work around the issue by opening app settings and by tapping the “Reset default settings” link. Since the application has the “all files” access, it will detect again the default transfer folder and set it to “Download”, which is more comfortable to move your files before uploading them.
Brian, thank you for the data, we’re analyzing it together with some test results on our side.
There is something I didn’t understand, though. Did you try to login to NoMachine Network with your User Id to confirm that you get the 2FA push notification? The user login is not needed to approve connections to your server, but it is just a way to confirm that our service can correctly send push notifications to your device. Thanks.
@Brian can you please verify that your iPhone is still allowing NoMachine to show notifications? You can check that in Settings > Notifications > NoMachine.
If the system configuration is correct, please try to login to Network in the NoMachine app and verify if you get the notification. If the app awaits for a 2FA confirmation but you still don’t get the notification, login by using your recovery code then, once logged in, disable and enable again the option to receive notifications in NoMachine app > Settings > Network.
Hi! I’m sorry for the delay, I was sure your post was handled but… can I say my brain is burning because it’s too hot? 😀
By the way, kidding aside, your problem seems to be caused by a Wacom driver, however I didn’t understand if you started reproducing it after updating to v9 or if also the previous installed version was affected. It should definitely be a Wacom problem so any NoMachine version should make no difference. Could you temporarily uninstall it and confirm that the NoMachine client starts correctly, please?
Hi. You don’t need to do anything when the IP changes, the server automatically reconfigures and notifies the new listening address. If you’ve physical access to the server you can start the NoMachine player, enter Settings > Server > Status and click the “Start the server” link. If you want to do it through a terminal, run the command
sudo /etc/NX/nxserver --startup.Hey, I’m sorry for not writing you back! I’ve received your stackdumps and devs are working on trying to reproduce your issue, so far without luck. I’ll update the thread as soon as they tell me how to proceed.
Thank you for sharing the logs, we’re analyzing them. We’d also like to verify if the blank screen and following disconnection was caused by a segmentation fault. Could you check the folders
~/Library/Logs/DiagnosticReports
/Library/Logs/DiagnosticReportsand send any stackdump file with prefix nxnode, please? No need to install again version 9, if the IPS files exist they’ll still be there.
It’s me again. Can you please save server side logs and send them to forum[at]nomachine[dot]com? You can do that by opening the NoMachine client > Settings > Server > Security > Take logs (below in the panel) and select where to save the file. We’d like to identify some operational parameters that are common in the issue I mentioned in my previous post.
Would you like to install a package implementing a potential fix for your problem? We’d just need to know what is the product you installed on the server machine (if you’re not sure about it, open NoMachine client > Settings > Server > Updates).
What type of Mac hardware do you’ve on server side (macbook, iMac, etc) and what processor does it use (Intel, Silicon)? We’ve already started some internal tests, but the more we know the better it is. I’ll keep you updated.
Hi. Can you please share a few details about your client and server OS version and working environment? We’re not aware of issues so we’d need to run some tests on your specific configuration.
Hey there. We’ve found the issue and documented also a workaround:
https://kb.nomachine.com/TR06W11407
The fix will be included in the next maintenance which is to be released shortly.
@thibaut the client mode being reverted could be caused by a client process overwriting your change, so if you want to test that, be sure to close all running nxplayer instances.
Additionally can you confirm if, like @wernermaes, you’re using the SSH protocol to connect and agent forwarding to authenticate?
We’re still in process of investigating the behaviour, but of course it is not expected so there is nothing wrong on your side.
Could you please export client side logs (Settings > Security > Take logs) and send them to forum[at]nomachine[dot]com? We’re like to address this issue quickly, any hints will be helpful.