Skip Navigation

andscape

@ andscape @feddit.it

帖子
3
评论
28
加入于
3 yr. ago

  • What is a service you host you never knew you needed?

    跳过

  • Understood, thanks. Seems like most people are doing it this way, keeping the app installed. Do you have to restore a backup when you re-log in? I'm always losing messages when that happens

  • Mullvad has partnered with Obscura VPN

    跳过

  • Mullvad already has that. It's called "WireGuard Obfuscation" in the settings. Obscura just seems to have a different implementation based on similar principles.

  • What is a service you host you never knew you needed?

    跳过

  • Ah got it, thanks. It's not an ideal setup tbh, it'd be great to be able to delete the WhatsApp app from my phone, but better than nothing...

  • What is a service you host you never knew you needed?

    跳过

  • Thanks, but I mean how did you set up the external client for it? Did you have a spare phone to use, or did you set up an Android VM?

  • What is a service you host you never knew you needed?

    跳过

  • Good to know, thank you. How did you set up the whatsapp bridge?

  • What is a service you host you never knew you needed?

    跳过

  • Thanks for the report. Do you use the whatsapp bridge? If so, how did you set it up? Emulator?

  • What is a service you host you never knew you needed?

    跳过

  • When I was looking into matrix bridges I heard a bunch of stories about people getting their accounts blocked after using them through the bridges. Is this still an issue?

  • Ditching the VPN and port forwarding the selfhosted way

    跳过

  • Look at the very least you should write in the blogpost clearly which parts are generated by LLMs, so your readers can decide whether to trust them.

  • Ditching the VPN and port forwarding the selfhosted way

    跳过

  • Idk man, it seems pretty irresponsible to me to write a blogpost with stuff that you got from ChatGPT without understanding it. People will assume that if you wrote a blogpost on this then you know what you're doing. ChatGPT gets stuff wrong all the time, and we're talking about firewall configuration here. If it misconfigured some stuff it could leave you and your readers vulnerable to all kinds of shit.

    In this case it seems to me that (luckily) there's just a bunch of redundant routing, but the next time it could be leaking your and your readers' torrent traffic out of the VPN tunnel, leaving you vulnerable to legal repercussions for piracy.

    Please don't authoritatively post stuff that you got from the automatic bullshit generator without understanding it.

  • Ditching the VPN and port forwarding the selfhosted way

    跳过

  • Nice, I recently went through the same struggle of setting up this configuration based on that LinuxServer post. My main nitpick on this is that automating the ip route configuration for the qBittorrent container is a pretty important step which is not explained in the post. Leaving any manual steps in any Docker setup is pretty bad practice.

    Since you're using LinuxServer's QBT image a good way to do this is to make use of their standard custom init scripts. You can just mount a script with the ip route commands to /custom-cont-init.d/my-routes.sh:ro on the container and it will be run automatically on each startup.

    Another nitpick is that the PostDown commands in the wireguard configs are useless since you're running them in Docker.

  • Proxying torrent traffic to homeserver

    跳过

  • Fantastic, thank you

  • Proxying torrent traffic to homeserver

    跳过

  • Wow thank you, this is the most useful reply I've received so far!

    This means I don't need to mess around with QBT's "proxy" settings? I was pretty confused since the only options available are SOCKS/SOCKS5 and HTTP, but I'm guessing that's a different kind of proxy than what I need...

  • Proxying torrent traffic to homeserver

    跳过

  • I indeed have a domain name pointing to the VPS IP, with Caddy managing TLS. Other apps are exposed this way, and I will do the same for the qBittorrent WebUI as well. I like having Caddy as a single gateway where I can apply security configs and monitor all traffic, I was hoping I would be able to pass torrent traffic through it as well but everybody seems very much against it.

    I already have wireguard setup as you describe so I guess I'll just give up on passing torrent traffic through the proxies and just open a localhost port on the qBittorrent container...

  • Proxying torrent traffic to homeserver

    跳过

  • Resetting the "time since last being told I don't know shit on the internet" back to 0 once again...

    I already have an existing and working setup used for other apps, it's close to the one described in this blogpost. Yes, it's complicated and inefficient, but it has reasons to be. I want to keep my qBittorrent configuration as close to this setup as reasonably possible for consistency. If your point is that it's counterproductive to follow this setup then... fair enough. I can just route traffic from the VPS to an exposed port on the local qBittorrent container over Wireguard, but that wasn't my preferred solution.

    Running a torrent client through a proxy doesn’t isolated a process.

    I was talking about network isolation, not process isolation.

    make sure your traffic is routing there properly

    That was pretty much what I was asking for help with.

  • Proxying torrent traffic to homeserver

    跳过

  • I have already set up all of that. My setup is similar to the one in this blogpost and it's already working for various apps that only use HTTP. What I'm trying to do is to also route BitTorrent traffic (TCP/UDP) over the same setup without opening up entirely new paths.

  • Proxying torrent traffic to homeserver

    跳过

  • Yes I already have that set up with Wireguard, what I'm figuring out is how to route traffic through it.

  • Proxying torrent traffic to homeserver

    跳过

  • I'm guessing what you mean is setting up port forwarding in Wireguard...

    The thing is ideally I would want all connections in and out of my homeserver's Docker network to go through the local Caddy proxy, so the app containers are isolated. That still means having at least the local Caddy acting as a TCP proxy, even if the VPS Caddy is bypassed. If that's too much of a hassle though I can instead just expose a port on the qBittorrent container directly to the homeserver's localhost, and forward that with wireguard to the VPS.

  • Proxying torrent traffic to homeserver

    跳过

  • By "set up wireguard to route through the VPS" you mean having wireguard forward a port from the VPS to a port on the homeserver at its wireguard IP address?

    qBittorrent will still need to publish the right IP address to peers though, right? So I will need to configure the proxy VPS's IP address in qBittorrent...

    Also that means binding a port on the qBittorrent container directly to the homeserver localhost. I've managed to keep the app containers isolated so far and it'd be nice to keep that, but if proxying the traffic is too annoying I guess I can just say fuck it and go with it.

  • Selfhosted @lemmy.world
    andscape @feddit.it

    Proxying torrent traffic to homeserver

  • Use a password manager

    跳过

  • Wild ass comment.

    Unless you really really need portability between devices

    Who doesn't??? What do you do, copy 20-char randomly generated passwords manually all the time? That's the whole point of password managers...

    I use firefox's local, inbuilt manager

    Browsers are NOT a secure storage for sensitive data, if you want a local password manager at least please use KeePassXC.

  • Selfhosted @lemmy.world
    andscape @feddit.it

    Hosting a public wishlist

  • Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ @lemmy.dbzer0.com
    andscape @feddit.it

    How To Torrent Software Safely (For Dummies)

    andscape.notion.site /How-To-Torrent-Software-Safely-For-Dummies-6819f8653be64a7b908ca8a64d7464c4