Which reverse proxy do you use/recommend?

Comments

• Shimitar@downonthestreet.eu ⁨1⁩ ⁨year⁩ ago

  I use and love nginx.

  Maybe a bit more old fashioned than more modern solutions, but steady solid and versatile. I use it as reverse proxy ad well as proxy for php stuff and more.

  source
• Dirk@lemmy.ml ⁨1⁩ ⁨year⁩ ago

  but I’d like to give Nginx Proxy Manager a try, it seems easier to manage stuff not in docker.

  NPM is pretty agnostic. If it receives a request for a specific address and port combination it just forwards the traffic to another specific address and port combination. This can be a docker container, but also can be a physical machine or any random URL.

  It also has Let’s Encrypt included (but that should be a no-brainer).

  source
• Kusimulkku@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Caddy is really simple and easy. Just werks and gives you https

  source

  • HurlingDurling@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Honest noob question. I currently connect to my self hosted server using Twingate. How would this be different? can you give me an Eli5 what a proxy manager would make my setup better?

    source
  • sxan@midwest.social ⁨1⁩ ⁨year⁩ ago

    I mean, the basic config file for Caddy is 1 line, and gives you Let’s Encrypt by default. The entire config file for a reverse proxy can be as few as 3 lines:

    my.servername.net {
       reverse_proxy 127.0.0.1:1234
    }
    

    It’s a single executable, and a single 3-line file. Caddy is an incredible piece of software.

    source

    • merthyr1831@lemmy.ml ⁨1⁩ ⁨year⁩ ago

      Ive got a basic workflow for nginx proxy manager now so this isnt super useful but good god that’s exactly what i wish nginx was.

      source
    • Kusimulkku@lemm.ee ⁨1⁩ ⁨year⁩ ago

      When I was researching reverse proxies I first stumbled upon nginx and traefik and especially nginx seemed a bit intimidating. As someone who hadn’t done it before I was worried if I’d do it right. Then I found caddy and yeah just used a threeliner like that in config and that was that. Simple and easy to get it right.

      I’ve since switched to having my stuff behind wireguard instead of reverse proxy, but I keep caddy around so I can just spin it back up if I want to access Jellyfin on someone’s tv or something.

      source
• snekerpimp@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I use the caddy plugin in opnsense. Used nginx proxy manager from Proxmox helper scripts before that, which was relatively easy and helped me understand the whole proxy thing. Moved to caddy on opnsense a few months ago, just because, and have had no good reason to change yet.

  source

  • tofuwabohu@slrpnk.net ⁨1⁩ ⁨year⁩ ago

    I was thinking about putting it from its dedicated VM to opnsense as well. I just don’t know yet what the security implications are and also my firewall hardware isn’t too beefy so I have to play around with it for a bit.

    source
  • EarMaster@lemmy.world ⁨1⁩ ⁨year⁩ ago

    I recently switched a bunch of nginx configs to the opnsense Caddy plugin. It is easy to configure, but in my opinion it lacks the ability to change settings beyond the basics. It isn’t helpful either that the plugin developer fails to recognize any other use case than the basics. It disqualifies the plugin for everyone with a little bit more complex setups.

    source
• 0x0@programming.dev ⁨1⁩ ⁨year⁩ ago

  freenginx

  source
• mbirth@lemmy.ml ⁨1⁩ ⁨year⁩ ago

  it seems easier to manage stuff not in docker

  Read into Traefik’s dynamic configuration. Adding something outside of Docker is as easy as adding a new config file in the dynamic configuration folder. E.g. jellyfin.yml:

  http:
  
    routers:
  
      jellyfin:
        rule: Host(`jellyfin.example.org`)
        entrypoints: websecure
        tls:
          certResolver: le
        service: jellyfin
  
    services:
  
      jellyfin:
        loadbalancer:
          servers:
            - url: "http://192.168.1.5:8096/"
  

  The moment you save that file it will be active and working in Traefik.

  source
• reddwarf@feddit.nl ⁨1⁩ ⁨year⁩ ago

  I use NPM in a docker container. It could not be easier in my opinion but then again, I did not use any of the alternatives so I might be missing out on something, who knows. I did manage a couple of proxy servers in the past based on Apache and I can tell you that NPM is much easier and logical to me than that.

  Just create a compose file and start it. Create DNS records pointing to your NPM IP address/exposed IP and make a host in NPM sending traffic to the right container IP:port. The compose file is super simple, could not be easier. Here’s mine for example:

  services:
    nginx-proxy-manager:
      container_name: nginx-proxy-manager
      image: 'jc21/nginx-proxy-manager:latest'
      restart: always
      ports:
        - '80:80'
        - '443:443'
      volumes:
        - ./data:/data
        - ./letsencrypt:/etc/letsencrypt
  
  

  I just make sure ports 443 and 80 are exposed on my router so DNS records can point to that IP adrdess. All traffic on port 80 gets re-routed to 443.

  I’m probably stating all the obvious things here 😀

  source

  • Tiritibambix@lemmy.ml ⁨1⁩ ⁨year⁩ ago

    I mean yes, that seems obvious now that I’ve learned this.

    But I wish I read this comment 3 years ago when I was starting to dive into self hosting. Would have saved me a bunch of time. So always assume some piece of knowledge is not obvious for someone out there and share ᕕ( ᐛ )ᕗ

    source

    • reddwarf@feddit.nl ⁨1⁩ ⁨year⁩ ago

      So always assume some piece of knowledge is not obvious for someone out there and share

      You just described a thing of mine I cannot help but do; explain the ever loving crap out of things
      I need to be careful with that though as relatives start to complain and push back on me telling things over and over.
      Thing is, until I see a full comprehension on the other side on what I try to convey I just keep explaining in variations, keep finding metaphors and keep pestering you until you ‘get it’. Some say it is a virtue, some say it is a hindrance.

      I have had therapy on this… 😂

      source

      • -> View More Comments
• lorentz@feddit.it ⁨1⁩ ⁨year⁩ ago

  Nginx for my intranet because configuration is fully manual and I have complete control over it.

  Caddy for the public services on my vps because it handles cert renewal automatically and most of its configuration is magic which just works.

  It is unbelievable how shorter caddy configuration is, but on my intranet:

  1. I don’t want my reverse proxy to dial on internet to try to fetch new SSL certs. I know it can be disabled, but this is the default.
  2. I like to learn how stuff works, Nginx forces you to know more details but it is full of good documentation so it is not too painful compared to Caddy.

  source

  • x00z@lemmy.world ⁨1⁩ ⁨year⁩ ago

    You can easily get automatic renewal for nginx using certbot.

    source

    • lorentz@feddit.it ⁨1⁩ ⁨year⁩ ago

      Yes, but it is a different cron job that needs to run, and you need to monitor it for failures. Caddy does everything out of the box, including retries.

      source
  • Oisteink@feddit.nl ⁨1⁩ ⁨year⁩ ago

    I switched to caddy just for the certs. I get trusted certs on all my internal subdomains without maintenance.

    I use haproxy, nginx and caddy at work including a caddy instance with internal CA. 4 lines in config and its signed by our normal CA, so its trusted by all our devices.

    source
• hendrik@palaver.p3x.de ⁨1⁩ ⁨year⁩ ago

  In my experience, all the 3 big ones work just fine. Caddy, Traefik, Nginx. I use Nginx.

  source

  • starshipwinepineapple@programming.dev ⁨1⁩ ⁨year⁩ ago

    I have had the same experience. Have used all three at some point but mostly use nginx for new servers

    source
• traches@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  I’ve been using caddyserver for awhile and love it. Config is nicely readable and the defaults are very good.

  source
• JASN_DE@lemmy.world ⁨1⁩ ⁨year⁩ ago

  I use both, Traefik on my docker host that’s also used for trying out new stacks, and NPM at work for a config that won’t change (ever, probably).

  Yes, the NPM web ui is somewhat easier in regard to proxying targets outside Docker.

  source