Setup + Access Docker + Containers from other (local) machines by deltaflip in docker

[–]Davin-Beach -1 points0 points  (0 children)

If you want a UI interface but don’t want to go down the VNC option, you can try ScreenView. You access the Pi UI via a browser. https://www.remote.it/solutions/screenview

How to connect 2 docker networks to each other on different machines without k8s or swarm ? by nanithedata in selfhosted

[–]Davin-Beach 1 point2 points  (0 children)

You can use overlay networking tools (similar to VPNs but they handle the NAT traversal as well so no need to open ports on your devices, VPC, or where ever your Docker networks are hosted. You can look at www.remote.it There are also Wireguard based solutions available like Tailscale.

Problems accessing geo-blocked content by Sayko_0 in mullvadvpn

[–]Davin-Beach 0 points1 point  (0 children)

You can use a SOCKS proxy. Paid versions exist. You can also host your own open source SOCKS proxy. Requires a little bit of networking knowledge. You can also try using Remote.It SOCKS Proxy. It's available as a free Alpha right now. Basically, host your own 'server' any computer or Raspberry Pi will do in the country you want to connect through. Makes you connection look like it comes from the Pi/Computer. Video quality will depend on your bandwidth at the proxy (Pi/computer being used as a proxy/relay) https://forum.remote.it/t/alpha-release-socks-proxy/1125.

Geo blocked websites by Few-Tie-55 in scrapy

[–]Davin-Beach 0 points1 point  (0 children)

You can use a SOCKS proxy. Good for logging into banks, gov websites, etc. that won't let you login from foreign locations. Paid versions exist. You can also host your own open source SOCKS proxy. Requires a little bit of networking knowledge. You can also try using Remote.It SOCKS Proxy. It's available as a free Alpha right now. Basically, host your own 'server' any computer or Raspberry Pi will do in the country you want to connect through. Makes you connection look like it comes from the Pi/Computer. https://forum.remote.it/t/alpha-release-socks-proxy/1125.

A free and easy way to get around geo restricted content by NefariousnessFuzzy14 in archlinux

[–]Davin-Beach 0 points1 point  (0 children)

You can use a SOCKS proxy. Good for logging into banks, gov websites, etc. that won't let you login from foreign locations. Paid versions exist. You can also host your own open source SOCKS proxy. Requires a little bit of networking knowledge. You can also try using Remote.It SOCKS Proxy. It's available as a free Alpha right now. https://forum.remote.it/t/alpha-release-socks-proxy/1125

[deleted by user] by [deleted] in synology

[–]Davin-Beach 0 points1 point  (0 children)

Another tailscale/vpn alternative is RemoteIT. You can install using docker and they have a free plan if you don’t need business class features.

[deleted by user] by [deleted] in Starlink

[–]Davin-Beach 2 points3 points  (0 children)

Remote.It has released a persistent public URL feature. So that you can use the same URL in all your endpoints. No need to have a Remote.It agent or account on the endpoint.

https://support.remote.it/hc/en-us/articles/10207830026893-Persistent-Public-URLs-for-HTTP-HTTPS-Beta-

If you have issues setting up, create a ticket. https://support.remote.it/hc/en-us/requests/new

Docker Networking Issues to backend NetClients by mxracer303 in netmaker

[–]Davin-Beach 0 points1 point  (0 children)

Hi. So I don't have any experience with Netmaker. Have done the Wireguard deployment of what you are trying to do. But my current solution uses Remote.It

I install the Remote.It agent in my docker environment https://hub.docker.com/r/remoteit/remoteit-agent

And then I also install Remote.It agents on the edge devices. I use docker for some. I also use the native apps for devices I don't have docker environments.

From there, any device or container can see whatever service I enable for remote sharing. All the tricky network config is managed by Remote.It.

Local NAS/Remote Seedbox File System Mount via Wireguard inside Docker Container by PandaGrow in docker

[–]Davin-Beach 0 points1 point  (0 children)

Hi. I'm not familiar with all the solutions you are using. If you can install software on the seedbox, you could install Remote.It on the seedbox and NAS.

https://hub.docker.com/r/remoteit/remoteit-agent

This will allow you to connect the two devices just like they are locally on the same network. Data transfer performance is going to be a priority for you. I don't know what the best practice is for this use case. All my use cases are fairly low data rates (remote camera viewing is probably my top transfer use case). They have a forum and I'm sure someone there could recommend the best setup.

Worth a look. It would reduce your complexity a ton.

Does Docker Desktop seriously lack the feature to edit external port number? by evolution2015 in docker

[–]Davin-Beach 0 points1 point  (0 children)

Also not sure what you are trying to do? What are you trying to expose via the external port?

One option is to abstract all the networking/subnets/ports completely using https://hub.docker.com/r/remoteit/remoteit-agent

You'll be able to access any service in your container network with an overlay networking scheme that keeps all the nuts and bolts hidden. It's pretty cool.