Selfhosted

37811 readers

713 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

Remote access in a country with heavy cencorship (lemdro.id)

submitted 2 months ago by [email protected] to c/selfhosted

22 comments fedilink hide all child comments

Where I live wireguard and openvpn are completely blocked and my isp doesn't provide a public ip.

Tailsclale and cloudflare tunnels don't work either.

Is there a last resort method for accessing my home server (a mini pc running openwrt and docker).

Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 13 points 2 months ago* (last edited 2 months ago) (2 children)

Can you ssh out? You could setup a VPS somewhere and use remote port forwarding to tunnel back home.

ssh -R 80:localhost:80 user@vps # forward HTTP traffic from remote host to the local host

You can even run ssh over an ssh tunnel for inceptiony goodness.

ssh -R 2222:localhost:22 user@vps  # your home system
ssh -p 2222 homeuser@vps  # From your remote system

[–] [email protected] 5 points 2 months ago (1 children)

Yes I can SSH to my US vps. I'll give this a try thank you.

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago)

SSH port forwarding is quite handy. You can have SSH setup a SOCKS proxy that you can use to send your browser traffic through the tunnel as well.

[–] [email protected] 1 points 2 months ago (1 children)

have you heard of sshuttle?

[–] [email protected] 3 points 2 months ago

Interesting - I had not. It was ages ago I was doing something like what I posted (well before that project ever got started) and it worked "well enough" for what I was doing at the time. Usually I'd run a SOCKS proxy on that second SSH line (-D 4444) and just point my browser at localhost:4444 to route everything home (or use foxyproxy to only route some traffic home).

Looks like sshuttle may have better performance though and provide similar functionality.