cross-posted from: https://feddit.de/post/10554932

I am looking something to connect to my server from outside my local network.

I am on a shared IP and my ISP doesn’t have port forwarding.

  • solberg@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    7 months ago

    If you’re the only one connecting to the server, I would recommend something like Tailscale. Everything will be encrypted and you won’t need to forward any ports to the public internet.

    If other people need to access it, an option might be https://hoppy.network. I haven’t tried it myself, but it looks like it would be pretty slick if it works well.

  • towerful@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 months ago

    I can recommend rathole ( https://github.com/rapiz1/rathole ).
    All it does is port forwarding. Easy to configure, easy to reason about, easy to dockerise.
    If you need reverse proxying, you have to set that up either on the public server, or on local infra (chances are, you already have reverse proxy locally so rathole just needs to forward 80/443).

    If its only for personal access (ie, you dont want services actually accessible by the internet) i can recommend tailscale for that. Its an auto-configuring wireguard VPN whose main selling point is NAT traversal. Very easy to set up, and very reliable.

    • Shimitar@feddit.it
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      Why rathole and not ssh tunneling? The latter exposes only one port (that you are already exposing anyway) while the former requires an additional port.

      What is the actual benefit of rathole? I an asking genuinely.

      • towerful@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        Hmm, fair.
        I liked it cause i could dockerise it next to nginx and do SNI forwarding.
        It had obvious and declarative config, which helped me get a redundant tunnel set up. Its great at auto-reconnecting.
        I have never used ssh tunnels. Maybe its just as easy as using rathole. Learning ssh tunnels might have been a better path for me.
        But rathole clicked, has been rock solid with 0 tinkering or tweaking, the config files make sense, its easy to in a docker container…

        So, i cant really answer your question.

        • Shimitar@feddit.it
          link
          fedilink
          English
          arrow-up
          2
          ·
          7 months ago

          Fair, setting up ssh tunnels with autoreconnect and such is indeed more complex.

      • towerful@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        I think 1 big advantage is that rathole can work over a websocket connection.
        So, if obfiscating, having to go via HTTP proxies, or whatever… rathole will still work.

  • Decronym@lemmy.decronym.xyzB
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    7 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    HTTP Hypertext Transfer Protocol, the Web
    HTTPS HTTP over SSL
    NAT Network Address Translation
    SSL Secure Sockets Layer, for transparent encryption
    UDP User Datagram Protocol, for real-time communications
    VPN Virtual Private Network
    nginx Popular HTTP server

    [Thread #646 for this sub, first seen 31st Mar 2024, 17:45] [FAQ] [Full list] [Contact] [Source code]