this post was submitted on 16 Jun 2023
2 points (100.0% liked)

Selfhosted

40246 readers
972 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] eneff@discuss.tchncs.de 1 points 1 year ago* (last edited 1 year ago)

What address is sshd listening on?

It would need to be able to listen to incoming connections via the VPN's tunnel device. So either 0.0.0.0 (so all addresses) or explicitly on whatever the tunnel's assigned address is, I think.

This could also be a firewall issue, can you share your routing tables?