Hi, i’m looking for a VPN that:

  • is easily deployable via a docker-compose
  • has an Android App and it doesn’t drain the battery too much
  • hides as regular HTTPS traffic so it’s not blockable by Firewalls. (I don’t need strong censorship resistance; it just has to work in offices and hotel WiFis.)
  • Bonus: A server like caddy can also accept HTTPS traffic for some regular websites next to the VPN server.

https://github.com/TrustTunnel/TrustTunnel sounds interesting, but the PR for docker compose was closed.

Do you know something else?

  • spaghettiwestern@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 hours ago

    Who said anything about China?

    OP: “I don’t need strong censorship resistance; it just has to work in offices and hotel WiFis.”

    • moonpiedumplings@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      37 minutes ago

      Many of the prominent https VPN protocols are for evading the great firewall of China. OP had that as a requirement, so it is not an unreasonable assumption.

      If you are evading less locked down firewalls, then you don’t need as stealthy VPNs.

      • spaghettiwestern@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        20 minutes ago

        Many of the prominent https VPN protocols are for evading the great firewall of China. OP had that as a requirement

        OP said exactly the opposite. Where the fuck do you get this stuff?

        • moonpiedumplings@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          43 seconds ago

          hides as regular HTTPS traffic so it’s not blockable by Firewalls

          From OP’s post, of course. If OP does not need to evade firewalls that are that aggressive, then they should have settled for a less stealthy VPN solution, as many of these HTTPS proxy solutions have performance and usability (can often only proxy TCP traffic) tradeoffs.

          Perhaps they have already tried the wireguard on port 443 solution, and it didn’t work for them. My high school would auto detect and block wireguard to any port. Perhaps they are in a similar situation.