ANGIE(8)

✨ ANGIE(8) ✨

okay so bestie, buckle up — this is the ANGIE(8) page from the System Manager's Manual, and it's honestly kind of a serve. it's the manual for the angie binary itself, the main character of the whole operation. let's get into it 💅

---

🌸 NAME 🌸

Angie — HTTP and reverse proxy server, mail proxy server 🦋

---

🎀 SYNOPSIS 🎀

angie [-?hqTtVvmM] [-c file] [-e file] [-g directives] [-p prefix]
      [-s signal] [--help] [--build-env] [--log-level=level]

---

💖 DESCRIPTION 💖

Angie is an HTTP and reverse proxy server, a mail proxy server, and a generic TCP/UDP proxy server. it's literally known for being high performance, stable, stupidly feature-rich, easy to configure, and it barely eats any resources. lowkey the whole package. 🔥

The options are as follows, and yes, we're going through all of them:

• -?, -h, --help — print help. that's it, that's the vibe 🫶
• -c file — use an alternative configuration file.
• -e file — use an alternative error log file. the special value stderr means "just send it to standard error, bestie."
• -g directives — set global configuration directives. peep EXAMPLES below for how this actually looks.
• -p prefix — set the prefix path. the default value is %%PREFIX%%.
• -q — suppress non-error messages while testing the configuration. quiet luxury ✨
• -s signal — send a signal to the master process. the signal argument can be one of: stop, quit, reopen, reload. here's the mapping, no cap:
  • stop → SIGTERM
  • quit → SIGQUIT
  • reopen → SIGUSR1
  • reload → SIGHUP
• -m — show built-in modules and exit.
• -M — show built-in and loaded modules, then exit. the extra-M stands for "more", obviously 💀
• -T — same as -t, but it also dumps the configuration files to standard output. two-for-one.
• -t — don't actually run anything, just test the configuration file. Angie checks the configuration file syntax, then tries to open the files referenced in the configuration file, including binding to the configured listen addresses. it's a whole vibe check for your config 🔍
• -V — print the Angie version, the compiler version, and the configure script parameters.
• -v — print the Angie version. (yes, lowercase. yes, it's a different thing. iykyk)
• --build-env — show the build environment and exit.
• --log-level= level — set the initial error log level.

---

🌈 SIGNALS 🌈

The master process of Angie can handle the following signals:

• SIGINT, SIGTERM — shut down quickly. like, quickly quickly.
• SIGHUP — reload configuration, start the new worker process with the new configuration, and gracefully shut down the old worker processes. a full glow-up 🦋
• SIGQUIT — shut down gracefully. soft launch of an exit.
• SIGUSR1 — reopen log files.
• SIGUSR2 — upgrade the Angie executable on the fly. iconic, honestly.
• SIGWINCH — shut down worker processes gracefully.

so normally there's no need to explicitly control worker processes, but they do support some signals too:

• SIGTERM — shut down quickly.
• SIGQUIT — shut down gracefully.
• SIGUSR1 — reopen log files.

---

🧚 DEBUGGING LOG 🧚

to enable a debugging log, you gotta reconfigure Angie to build with debugging:

./configure --with-debug ...

and then set the debug level of the error_log:

error_log /path/to/log debug;

you can also enable debugging for one particular IP address, which is kind of a niche flex but ok:

events {
        debug_connection 127.0.0.1;
}

---

⭐ ENVIRONMENT ⭐

• ANGIE — this environment variable is used internally by Angie and should not be set directly by the user. hands off, bestie 🙈

---

💜 FILES 💜

• %%PID_PATH%% — contains the process ID of Angie. the contents of this file are not sensitive, so it can be world-readable.
• %%CONF_PATH%% — the main configuration file.
• %%ERROR_LOG_PATH%% — the error log file.

---

🍓 EXIT STATUS 🍓

exit status is 0 on success, or 1 if the command fails. simple as that. 💅

---

👑 EXAMPLES 👑

test the configuration file ~/myangie.conf with global directives for the PID and the quantity of worker processes:

angie -t -c ~/myangie.conf \
        -g "pid /var/run/myangie.pid; worker_processes 2;"

look at that. -t for the test, -c for the file, -g for the global directives. we ate. 🔥

---

💀 SEE ALSO 💀

for online documentation, technical support, and bug reports, please refer to https://en.angie.software. that's the one link, go off.

---

🌸 HISTORY 🌸

on 27 of July 2022, a group of former nginx developers registered LLC "Web Server" in order to create and maintain a new fork of nginx called Angie. and that's the origin story, main character energy from day one. ✨

---

🫶 AUTHORS 🫶

this manual page was originally written by Sergey A. Osokin <osa@FreeBSD.org.ru> 💖

---

so yeah, that's literally the whole ANGIE(8) page. every flag, every signal, every path — all of it. slay. 🎀

and one last cute sign-off: this beauty ships from Debian, dated January 21, 2026. periodt. 💅⭐