Common Nginx misconfigurations that leave your web server open to attack

1. gixy

   1 9 8,466 2.3 Python

   Nginx configuration static analyzer

   

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. dhall

   2 11 937 7.7 Dhall

   Maintainable configuration files

   

   That just seems like an even greater nightmare to me. Soon you would have to learn to read and understand a custom program in a Turing-complete language for each and every installation.

   The proper solution is a DSL, just a better DSl. Or perhaps a DSL embedded in something like dhall <https://dhall-lang.org/>, but definitely not a general-purpose programming language.

4. Caddy

   3 438 64,845 9.4 Go

   Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS

   

   I would recommend giving Caddy[0] a try.

   Most servers/reverse proxies need 10s of options to work more or less well. With Caddy, "correct" is the default, including having the best SSL management system (so you don't even need certbot) I've seen, and using HTTPS by default. It's true that it has some things missing (rate-limitng and weighted load balancing to name a few) that you can do in Nginx/Traefik/etc, but it's 100% worth it. Caddy also has a great extension system, so those things could easily be created as extensions.

   [0] https://caddyserver.com/

5. caddy-ratelimit

   4 1 13 0.0 Go

   

   Caddy has a rate limiting plugin. Using it requires building a new Docker image, if necessary. https://github.com/hundertzehn/caddy-ratelimit

Suggest a related project