1836 results for "nginx"

  • carrvo: then, because our nginx ingress expects the PROXY protocol we also deploy hapoxy to our cluster. CoreDNS actually points at the haproxy and not at our ingress. That way haproxy can forward the requests using the PROXY protocol to nginx. This solution was inspired by: https://github.com/compumike/hairpin-proxy
    Zegnat at 2025-03-17 07:12
  • [preview] [compumike] hairpin-proxy: PROXY protocol support for internal-to-LoadBalancer traffic for Kubernetes Ingress users. If you've had problems with ingress-nginx, cert-manager, LetsEncrypt ACME HTTP01 self-check failures, and the PROXY protocol, read on.
    Loqi at 2025-03-17 07:12
  • Yes, that's nginx client max body size
    GWG at 2025-03-16 20:25
  • GWG, changed. Restart Nginx?
    Kolev at 2025-03-15 00:46
  • http://dpaste.com//G25EL4TRM /etc/nginx/sites-available/calebh.top
    Kolev at 2025-03-15 00:42
  • GWG, it still asks for FTP. Let me grab my Nginx config.
    Kolev at 2025-03-15 00:38
  • Also, can you share your nginx config
    [dshanske] at 2025-03-15 00:00
  • Kolev: Zegnat left you a message 19 hours, 33 minutes ago: not sure you ever got an answer yo tour HTTPS question. Most people do not have a need to protect traffic within their own network / on the same server with HTTPS, so they would set up nginx (or whatever their ingress point is) to handle (“terminate”) HTTPS (TLS). You might need multiple certificates or a wildcard certificate still, if your different services are on subdomains.
    Loqi at 2025-03-14 02:42
  • It's returning a 403 Forbidden and announcing it's from `nginx/1.18.0 (Trisquel GNU/Linux)` - and browse reports secured with a Let's Encrypt cert.
    [artlung] at 2025-03-14 00:15
  • I looked at the site earlier when I got the nginx error, may have cached it
    GWG at 2025-03-13 22:58
Sort by:

Filter results by:

Tag

Query took 0.01s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23