Bonus Mastodon Documentation
  • Introduction
  • Mental Health
  • Basics
    • Rules and Culture / Terms of Service
    • Cloud Servers (VMs)
    • Cloud Media Storage (S3 Buckets)
      • Media SubDomain
    • Cloud Email (SMTP)
      • ZeptoMail by Zoho
      • AWS SES
    • Static Content CDN
      • Bunny.net CDN (Pull Zone)
    • Backups
    • Monitoring / Alerting
  • Advanced
    • OS Tuning
    • NGINX Tuning (Reverse Proxy)
    • NGINX Trouble Shooting
    • PostgreSQL 14 Tuning
    • Web (Puma) Tuning
    • Sidekiq Tuning
    • ElasticSearch Tuning
    • Redis Tuning
  • Other
    • Reading Material
    • OS Monitoring
Powered by GitBook
On this page
  • Not enough worker processes
  • cache file has too long header
  • Monitor the active connections
  1. Advanced

NGINX Trouble Shooting

PreviousNGINX Tuning (Reverse Proxy)NextPostgreSQL 14 Tuning

Last updated 2 years ago

Not enough worker processes

  • Keep your eyes on the /var/log/nginx/errors.log Problem: Not enough worker processes (Tells you the problem/solution)

Solution: Increase worker processes.

cache file has too long header

  • 2022/11/30 08:18:38 [crit] 1392615#1392615: *4208360 cache file "/var/cache/nginx/8/aa/d974f05ff7f54ab0f4b21dbba7861aa8" has too long header, client: x.x.x.x, server: aus.social, request: "GET /api/v1/instance HTTP/2.0", host: "X.social"

Solution: ??

Monitor the active connections

  • Consider installing the status module to keep an eye on the active connections.

Output of https://x.com/nginx_status

TODO: Investigate the Nginx virtual host traffic status module

https://github.com/vozlt/nginx-module-vts
Code Block from my instance conf