Not in Linux containers, not that i could get working. If you have a working config could you please share it.
I tried for two days and gave up, it’s (or was ) non conventional with some cli that did not work in an alpine container or arch. AirVpn worked immediately.
They claim to have port forwarding, something i learned was untrue after purchasing. They also don’t offer refunds.
For torrents i recommend airvpn. For privacy i recommend Tor / Tails.
That’s right, one should. However, I’m using this only as an internal documentation tool, There’s no port forward and it’s not public. I am literally using it to take notes on a few things I’m developing.
It’s actually really nice being able to drop a whole bunch of links and have them threaded and linked between each other. It works quite well.
Yeah, without a doubt, it’s just an oversight.
There’s nothing malicious here.
I should have read the docker compose a bit closer when I was trying to figure it out but There’s only so many hours in the day, and sometimes you rush.
Yeah this hit me as well and it was very confusing until I found that lemmy.ml
I can’t find it on the main branch so I didn’t raise am issue
Click the link, you’ll see it is indeed the first heading under Criticism
Set up wireguard in a docker container and then forward the port to wireguard, the default container on docker hub is fairly straightforward and you can always ask me for help if you need :).
However, If you are using ipv4, you need to make sure that you’re not behind a CG-NAT (If you think you might be, call your ISP and tell them you have security cameras that need to get out or something like that).
You could also try tailscale which is built using wireguard with nat-busting features and a bit easier to configure (I dont personally use it as wireguard is sufficient for me).
After that Caddy + DNSMasq will simply allow you to map different URLs to IP addresses
dnsmasq
my_computer -> 192.168.1.64http://dokuwiki.my_computer -> http://my_computer:8080http://dokuwiki.192.168.1.64 -> http://192.168.1.64:8080/Caddy and DNSmasq are superfluous, if you’ve got a good memory or bookmarks, you don’t really need them.
VPN back into home is a lot more important. You definitely do not want to be forwarding ports to services you are running, because if you don’t know what you’re doing this could pose a network security risk.
Use the VPN as the entry point, as it’s secure. I also recommend running the VPN in a docker / podman container on an old laptop dedicated just to that, simply to keep it as isolated as you can.
Down the line you could also look into VLan If your router supports that.
I personally would not bother with SSL If you’re just going to be providing access to trusted users who already have access to your home network.
If you are looking to host things, just pay for a digital droplet for $7 a month, It’s much simpler, You still get to configure everything but you don’t expose your network to a security risk.
If you’re just going to VPN in to your home network, I’ve found caddy to be the simplest.
That was the issue i hit. I torrent in containers so that was a big deal for me.