Using JuiceSSH on my phone, I’m able to connect to my device without any problems when I’m on my home Wi-Fi. However, when off WiFi and connected to my VPN, the server doesn’t connect. I’m still able to access the services it’s running, but can’t SSH into the server itself.

Edit: I thought I answered everyone’s questions but I’m not seeing the answers so I’m posting the info here.

I get the below message and nothing happens. Then about 60 seconds later Juice gives a timeout error.

ssh_socket_connect: Nonblocking connection socket: 98 ssh_connect: Socket connecting , now waiting for the callbacks to work

I’m using the built in VPN service in my router. It uses the OpenVPN protocol.

Edit 2: Using the same VPN config file, I’m able to access the server using Putty on my laptop. So I’m wondering if it is a Juice specific issue.

        • LachlanUnchained@lemmyunchained.net
          1·
          1 year ago

          Really strange. Probably done all this, but just run through it again make sure you haven’t got a typo somewhere or something.

          1.	Check Connection Settings: Ensure the IP, port, and authentication details are correct in JuiceSSH.
2.	Firewall Rules: Confirm the SSH port (usually 22) isn’t blocked by any firewalls on your network or server.
3.	Try another SSH App: To see if it’s a JuiceSSH-specific issue, download another SSH client like Termius and test the connection.

          (I’d probably start with 3, might narrow it down to a juice config problem, I’m not very familiar with juice)

          • boothin@kbin.social
            1·
            1 year ago

            I would also test by connecting to the vpn and trying to go to a service’s ip or ping an ip on the network behind the vpn from the browser. I use juice and ovpn on my router as well and it works fine, so its unlikely to be a juice specific problem

            • LachlanUnchained@lemmyunchained.net
              1·
              1 year ago

              Yeh. It’s strange if it’s the same config file. Works on a laptop via putty.

              Surely just a configuration issue. Or like I said. Even a typo. I’m an absolute newb. I’ve spent days debugging networks, only to find a typo somewhere.