- This topic has 6 replies, 2 voices, and was last updated 1 year, 10 months ago by
.
-
Posts
-
Hi guys, I have an Oracle Cloud VM with Ubuntu 22.04 + KDE which was working fine with NM 7.x. After upgrade to 8.4.2 I can’t connect to it anymore by NM. The OCI VM is my Server w/ Ubuntu 22.04 +KDE, and the client is Kubuntu 22.04, also updated to NM 8.4.2. I have this setup for more than year and always worked. Suddenly, after upgrade to 8.4.2 it stopped. I uninstalled NM completely, delete everything and installed in as a fresh install. Nothing. I can RDP to the VM, can SSH to it, but can’t “NX” to it. Error Message is: “No route to the network or to the server <server IP> found”. If I choose to use SSH, instead of NX the error msg changes to: “Running NM session over a ssh connection is not supported on this server. Do you want to switch to the NX protocol?” And If I choose ok I got the route error. What do you suggest ? Is there any log I can send to check ? I like NoMachine a lot , it far superior to RDP and I got used to it. To have an idea of how it works fine I could watch Youtube on the VM as I were in my laptop.
Hi Fabs74,
please answer to a few questions that will help us to get rid of some doubts.
How did you do the NoMachine update procedure ? Was it with automatic updates or manual?
Did you have any NoMachine custom settings set for version 7?
When you write “delete everything and installed in as a fresh install” did you delete the entire /usr/NX/ directory?
Did you change anything in Ubuntu settings on Oracle Cloud after NoMachine update?
What is the output after executing the command: sudo /usr/NX/bin/nxserver –status?
What program do you mean by RDP?
Regards,
TomHi Tom, thanks for answering. So ,
1- How did you do the NoMachine update procedure ? Was it with automatic updates or manual?
First I did a regular linux update (sudo apt update) , then the regular NoMachine update through the UI. After updates I lost the access.
2-Did you have any NoMachine custom settings set for version 7?
No, just the regular Vanilla settings.
3- When you write “delete everything and installed in as a fresh install” did you delete the entire /usr/NX/ directory?
Yes, found it in a post somewhere here. Complete uninstall and directories removal.
4- Did you change anything in Ubuntu settings on Oracle Cloud after NoMachine update?
No, no changes, just the regular system updates (22.04)
5- What is the output after executing the command: sudo /usr/NX/bin/nxserver –status ?
NX> 111 New connections to NoMachine server are enabled.
NX> 161 Enabled service: nxserver.
NX> 161 Enabled service: nxnode.
NX> 161 Enabled service: nxd.
6- RDP is remote desktop protocol. I installed an RDP server on the VM, which I can enable in case of problems like this. In fact that was the first remote access solution I had before I had known NoMachine. I’m using KRDC on my laptop to access the VM. [Removed ] works fine too, but as I use KDE I kept just KRDC as it works.
I attached a prtscrn of the remote access
Attachments:
Hi Fabs74,
are you connecting to one of the addresses show in the screenshot?
The addresses I see there are private.
Kubuntu (NoMachine client) is also on Oracle Cloud?Regards,
TomTom, I don’t know what happened, but seems that my morning answer didn’t arrive. I’m connecting to a public address, which I blurred on propose (Left corner). Starts with 144…. I’m running Kubuntu on my laptop and Ubuntu +KDE on the OCI VM. Both 22.04. Is it possible to get a link to the 7.X version, I would like to test with that because it was working with it. And again I can SSH and RDP to that address without any problem as you can see by the ss.
Fabs74,
please check if you have open port 4000 for TCP and UDP protocols in Virtual Cloud Network Details – Security Lists.
You can also test if the port is actually working by setting ssh to this port and connect ssh to port 4000 from client machine.Perhaps after the upgrade you don’t have the port added in iptables, you can add it by running the command:
iptables -I INPUT 6 -m state –state NEW -p tcp –dport 4000 -j ACCEPT.Regards, Tom
Great suggestion Tom. Thanks to it I could troubleshoot it better. Reconfigured all VCN security list for change ssh to 4000 , reconfigured the sshd and nothing. No connection after and same “no route to host” error displayed in SSH. Tried your iptables commands but get too much errors. Search a little bit more and found this : https://www.reddit.com/r/oraclecloud/comments/r8lkf7/a_quick_tips_to_people_who_are_having_issue/
which give this little command :
sudo iptables -I INPUT -j ACCEPTand voilá. It worked. The only problem is that it seems it didn’t kept the iptables when reboot the VM even after issue the:
sudo suiptables-save > /etc/iptables/rules.v4 exit. But I’ll troubleshoot this later. Seems something Ubuntu specific. By at least I can connect now.
This topic was marked as solved, you can't post.