Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Shill Me Your Favorite Reverse Proxy!

2»

Comments

  • itsTomHarperitsTomHarper Member, Megathread Squad

    Good ole nginx

  • NeoonNeoon Community Contributor, Veteran

    tinyproxy if it doesn't crash.

    Thanked by 1szarka
  • Cady has insane performance when it comes to ssl termination.

    Thanked by 2ralf szarka
  • yoursunnyyoursunny Member, IPv6 Advocate

    @philwatcher said:
    Caddy 100%. I have fought long enough to get Apache and nginx to reverse proxy with TLS and it was always annoying. Caddy just does everything automated. Only downside is that you don't have like nginx 10+ years of old forum discussions on how to solve your specific problem, or 100+ years of old grey beards discussing how to get Apache to do what you want. But if you have normal problems and want the obvious, easy solution, it's caddy IMO.

    We use Caddy primarily for TLS termination.
    Other advanced needs are delegated to nginx that runs behind Caddy.
    https://yoursunny.com/t/2021/yoursunny-com-caddy/

    Thanked by 1szarka
  • CLI:
    Feature rich: HAProxy
    Timesaver: Caddy
    Docker, Kubernetes: Traefik

    GUI:
    For beginners: Zaroxy > Nginx Proxy Manager

    Thanked by 1mandala
  • For me I'm used to NPM for all my dockers. Heard good things about Caddy and others but I prefer to have web interface so... :wink:

  • caddy, automatic ssl and fast

  • Caddy +1, easiest to configure, solid performance. Use with caddy-docker-proxy if you run all your apps in Docker.

  • @Neoon said:
    tinyproxy if it doesn't crash.

    That does sound perfect, as long as it doesn't crash.

    Thanked by 1ralf
  • Holy crap! tinyproxy is so frickin' easy to set up.

  • @szarka said:
    Holy crap! tinyproxy is so frickin' easy to set up.

    Well, sort of. Its version of basic auth doesn't quite behave the way I need it to. But, still, a very nice little tool I could use somewhere else, I reckon.

  • emghemgh Member, Megathread Squad

    DIDNT READ BUT CADDY!!!

    Thanked by 1lukast__
  • emghemgh Member, Megathread Squad

    @emgh said:
    DIDNT READ BUT CADDY!!!

    I USE IT

    I LIKE IT

    Thanked by 1lukast__
  • nginx in a rootless container
    with acmed in a rootless container to automatically manage the certs

    NPM is convenient only if you use the simplest configs (which to be fair cover 95% of everything you would normally host), otherwise it's just 100MB RAM wasted.

    Traefik is hot garbage that uses a lot more RAM than nginx and is a lot slower. And traefik's panel is so bad. Although I really like that you can use docker labels to set up the routing for containers.

    Thanked by 1wuck
  • Well, I've got a proof-of-concept running using Caddy. Learning the syntax of a new application is always a PITA.

    Every other Unix app: caddy -v or caddy --version. Caddy: caddy version. WTF, guys?

    Why did I need to know the version? Well, basic_auth wasn't working. But it turns out that the latest Alma package has 2.6.4, so I need to use the deprecated basicauth syntax.

    Anyway, I think this is going to be my solution. Simple and lightweight enough, but enough features that I can continue to use as I move beyond my MVP. :)

    Thanks, all!

  • @szarka said:
    Holy crap! tinyproxy is so frickin' easy to set up.

    But how easy is it to crash?

  • @ralf said:

    @szarka said:
    Holy crap! tinyproxy is so frickin' easy to set up.

    But how easy is it to crash?

    I didn't throw enough traffic at it to find out. LOL

    At least it compiled cleanly.

    Thanked by 1ralf
  • @szarka said:
    I've got a proof-of-concept running using Caddy ... I think this is going to be my solution. Simple and lightweight enough

    Out of curiosity, how much RAM Caddy consumes in your case?

  • @DataRecovery said:

    @szarka said:
    I've got a proof-of-concept running using Caddy ... I think this is going to be my solution. Simple and lightweight enough

    Out of curiosity, how much RAM Caddy consumes in your case?

    Looks like 64 MB. Which is nice, because I want to see just how small of a server I can squeeze this application into to make it accessible to everyone. The web pages it's proxying won't actually get much traffic, and aren't central to the tasks the server is performing, so important to me that it have a small footprint.

    Thanked by 1DataRecovery
  • @szarka said:

    @DataRecovery said:

    @szarka said:
    I've got a proof-of-concept running using Caddy ... I think this is going to be my solution. Simple and lightweight enough

    Out of curiosity, how much RAM Caddy consumes in your case?

    Looks like 64 MB

    Thanks!

    BTW, didn't you happen to notice how much memory Tinyproxy was using?

  • @DataRecovery said:

    @szarka said:

    @DataRecovery said:

    @szarka said:
    I've got a proof-of-concept running using Caddy ... I think this is going to be my solution. Simple and lightweight enough

    Out of curiosity, how much RAM Caddy consumes in your case?

    Looks like 64 MB

    Thanks!

    BTW, didn't you happen to notice how much memory Tinyproxy was using?

    Well, ps reports it as 0.0% on this 32 GB system, so less than Caddy. LOL

    Thanked by 1DataRecovery
  • At first I was like

    @szarka said:
    I want to see just how small of a server I can squeeze this application into

    But then

    @szarka said:
    0.0% on this 32 GB system

    :D

    Thanked by 1szarka
  • I could probably even hack tinyproxy into doing what I want to with a couple of small, ugly changes to the source. But that way lies madness…

  • @lowendtalkxdax said:
    CLI:
    Feature rich: HAProxy
    Timesaver: Caddy
    Docker, Kubernetes: Traefik

    GUI:
    For beginners: Zaroxy > Nginx Proxy Manager

    I was about to comment on this thread, but this is literally exactly what I would've said. Caddy literally takes 30 seconds to download, create config and run it. Due to this it's usually my go-to.

  • Caddy + basic_auth. Simple and fast

  • @ipguru said:
    Caddy + basic_auth. Simple and fast

    Automatic HTTPS looks slick. Need to try that tomorrow.

  • I might try out some of these options based on how easy it is for me to setup. :)

  • fijxufijxu Member
    edited December 2024

    haproxy is insanely good. I mostly use it to expose docker services.
    and NGINX + Openresty for scripting with Lua. With openresty you can recreate NGINX Plus features if you know how they work.

  • 64 mb is too much I prefer cloudflare

    Thanked by 1ralf
  • @kedihacker said:
    64 mb is too much I prefer cloudflare

    I'm willing to spend 64 MB to avoid a centralized point of failure that also leaks privacy.

Sign In or Register to comment.