Forum Replies Created
-
Posts
-
The full verbiage of the line on my screen, under Authentication, is: “Use key-based authentication with a key you provide”.
Yes, I change the Authentication method from “Use password authentication” to that, then click Modify.
Latest from Linux to macOS.
Client: NoMachine 8.14.2 on Linux via FlatPak
Pop!_OS 22.04 LTS
Server: NoMachine 8.14.2 on macOS Sequoia 15.2
I set up a special ssh key pair (tried both ED25519 and RSA) for this connection (also tried with and without a passphrase) and verified that I could connect in a terminal without being prompted for a password.
In NoMachine on the client, I right-clicked on discovered server and selected Edit Connection. Then, Configuration->Use key-based authentication, and Modify. I used the three dots to select the private key of the pair I created. I also tried both import and non-import.
I hope that helps, fwiw.
Thank you @Britgirl.
This is not what I experienced:
If you try to connect using an SSH connection to a server where the Free Edition is installed, you will get the following message:
SSH connections are not supported on this server.
Instead, I just simply got a message stating authentication failed.
Tim
PIA VPN, but I typically only use it when traveling. The filter was for a split tunnel which PIA had me configure about 8 months ago because, I think,
npmor maybedockerhub downloads were hanging.Worse, this morning I went to connect to the MBP and once again couldn’t see it. Turns out, the filter became active again on its own even though the VPN is off. Now I’ve deleted the rule and hopefully this is really resolved.
Resolved!
Here is what I discovered. As requested earlier, I had turned off all firewalls and VPNs. What I didn’t see or think would be an issue was a filter that was created for the VPN (split tunnel) on the MBP. Even though the VPN was off, this filtering rule remained active, and prevented the discovery. I can’t say as I fully understand *why* this is offensive to the process, but I was able to replicate the behavior to confirm the solution. With the split tunnel filter explicitly turned off, the MBP is discovered as one would expect.
Thank you!
Hi @Britgirl–
I just wanted to confirm y’all got my set of logs from the higher debug version and that they are what you need?
Thanks!
Tim
I just tried deleting and reinstalling NoMachine on both the Ubuntu box and the 2017 MacBook Pro. Same result.
All computers are on the same LAN (no subnets) assigned ip addresses by the same router.
Turned firewall off on 2017 MacBook Pro and restarted. No change. I’m pretty sure the working MacBook also has the firewall on, but I’d have to check and confirm later. Either way, the 2017 MacBook Pro still doesn’t show up (I am able to connect by manually configuring).