How do I access a local host (192.168.1.x) from my VPS via SSH?

[GisaLab]

Hello, I'm using version 1.13.1 and I'm a complete beginner. How do I access a local host (192.168.1.x) from my VPS via SSH?
I created 2 client machines, the vps and the local host, which is in the same local network as the PANGOLIN-LAN site, then a private resource in host mode to the destination 192.168.1.x, in access control I tried all the client machines and without any I cannot connect via ssh.
The only solution I found was to open a public port to the target host.

[RadioHerzblut]

https://github.com/orgs/fosrl/discussions/1295#discussioncomment-14133084

It's the same scenario as in this post.
But it won't work without opening the port.

Alternatively, you can set up a direct VPN connection to your LAN. But here, too, you need to open the port. However, the Wireguard port is in death mode.

[GisaLab]

Thank you for your reply. I haven't had much time to look into this problem these past few days, and I managed to get the SSH connection working. The Newt binary wasn't up to date; I updated it, but it still didn't work. Looking at the logs of the newt-gateway-lan host, I saw that the route wasn't added for the target host. I was tearing my hair out for hours when I stopped and then restarted the Newt service. It added the route and worked. I don't know if running the newt install command or the command during the binary installation creates additional connection instances and causes interference?

I encountered another issue which is probably a bug. I had this problem during the first installation of Pangolin (yeah, I stupidly did an rm of the folder containing the Pangolin config). When adding a public resource with the domain nc.domain.com whose target is in the LAN network of the PANGOLIN-LAN site (host newt-gateway-lan), I get a 404 page and in the Traefik dashboard the HTTP service 10-xxx-service@http corresponding to the public resource is absent. A network error message can sometimes be displayed when modifying the resource. So I thought okay maybe something went wrong when the resource was created so I deleted it and recreated it. This worked for a few hours then the same problem occurred again: the http service 10-xxx-service@http corresponding to the public resource was missing. This time I disabled the registered SSL and then re-enabled it, and it worked. The http service 10-xxx-service@http corresponding to the public resource was added to Traefik.

I have another resource for another target in the PANGOLIN-LAN site and it works perfectly, I haven't had any problems. It's only the public resource with the domain nc.domain.com that has this problem.