The plan, the usage text and the docs all said --proxy snippets writes configuration for the web server already on the machine. Nothing did. Now it writes:
<dir>/proxy/nginx-inbuxa.conf:
The server's names, the console and the webmail are passed to 127.0.0.1:8081, :8082 and :8080.
X-Forwarded-For is set to the client's address, since the server trusts it.
Push streams aren't buffered and have a 1-hour read timeout.
On port 80, the mail server's own certificate challenges go to the server and everything else redirects to HTTPS.
The ssl_certificate paths follow a pattern (/etc/ssl/inbuxa/<name>.fullchain.pem) for the operator to fill or edit.
<dir>/proxy/Caddyfile.fragment: the same for Caddy. It has no global block, so it imports beside other sites. It leaves HTTP-01 for the server's names to the server, as the managed Caddy does.
That web server becomes the proxy, so it's treated the way the managed Caddy is: the server trusts its X-Forwarded-For and exempts its address from the auto-ban. That address is 127.0.0.1 for a server on the host. For a server in a container it's also the project network's gateway (.1), since a request to a published loopback port reaches the container from there.
Nothing is loaded or reloaded. The summary names the directory, and the log says to turn on the mail server's own certificates in the console once the file is loaded. A re-run rewrites it for what's installed at that point. The interface's Reach screen now offers it alongside Caddy and "nothing in front", and the README drops the "not built" note.
Tests
The snippets render for each shape and leave out what isn't installed. The generated files pass real nginx -t and caddy validate.
e2e/cases/proxy-snippets.sh, 13/13: installs nginx, installs the suite behind it, loads the generated file with self-signed certificates, and reaches the server (307), the console and the webmail through nginx on 443. Port 80 passes a challenge through to the server (its JSON 404, not nginx's page) and redirects the console. A re-run converges and rewrites the file.
The first run "failed" because the test checked port 80 the instant systemctl reload nginx returned, while nginx's old workers were still answering; a 3-second settle fixed it.
interface, install-local, install-host, install-public, status-export and topology pass on this branch.
The plan, the usage text and the docs all said `--proxy snippets` writes configuration for the web server already on the machine. Nothing did. Now it writes:
- **`<dir>/proxy/nginx-inbuxa.conf`**:
- The server's names, the console and the webmail are passed to 127.0.0.1:8081, :8082 and :8080.
- `X-Forwarded-For` is set to the client's address, since the server trusts it.
- Push streams aren't buffered and have a 1-hour read timeout.
- On port 80, the mail server's own certificate challenges go to the server and everything else redirects to HTTPS.
- The `ssl_certificate` paths follow a pattern (`/etc/ssl/inbuxa/<name>.fullchain.pem`) for the operator to fill or edit.
- **`<dir>/proxy/Caddyfile.fragment`**: the same for Caddy. It has no global block, so it imports beside other sites. It leaves HTTP-01 for the server's names to the server, as the managed Caddy does.
That web server becomes the proxy, so it's treated the way the managed Caddy is: the server trusts its `X-Forwarded-For` and exempts its address from the auto-ban. That address is 127.0.0.1 for a server on the host. For a server in a container it's also the project network's gateway (`.1`), since a request to a published loopback port reaches the container from there.
Nothing is loaded or reloaded. The summary names the directory, and the log says to turn on the mail server's own certificates in the console once the file is loaded. A re-run rewrites it for what's installed at that point. The interface's Reach screen now offers it alongside Caddy and "nothing in front", and the README drops the "not built" note.
**Tests**
- The snippets render for each shape and leave out what isn't installed. The generated files pass real `nginx -t` and `caddy validate`.
- **`e2e/cases/proxy-snippets.sh`, 13/13:** installs nginx, installs the suite behind it, loads the generated file with self-signed certificates, and reaches the server (307), the console and the webmail through nginx on 443. Port 80 passes a challenge through to the server (its JSON 404, not nginx's page) and redirects the console. A re-run converges and rewrites the file.
- The first run "failed" because the test checked port 80 the instant `systemctl reload nginx` returned, while nginx's old workers were still answering; a 3-second settle fixed it.
- interface, install-local, install-host, install-public, status-export and topology pass on this branch.
The plan, the usage text and the docs all said --proxy snippets writes
configuration for the web server already on the machine; nothing did. Now
it writes <dir>/proxy/nginx-inbuxa.conf and <dir>/proxy/Caddyfile.fragment:
the server's names, the console and the webmail passed to their loopback
ports, X-Forwarded-For set to the client's address, the webmail's and the
server's push streams unbuffered, port 80 passing the mail server's own
certificate challenges to it and redirecting the rest. The fragment has no
global block, so it imports beside other sites, and leaves HTTP-01 for the
server's names to the server, as the managed Caddy does.
That web server becomes the proxy, so it is treated as Caddy is: the
server trusts its X-Forwarded-For and exempts the address its requests
arrive from -- loopback for a server on the host, the project network's
gateway too for one in a container, where a published loopback port is
reached from there. Nothing is loaded or reloaded; the summary names the
directory, and the mail server's own certificates are turned on in the
console once the file is loaded. A re-run rewrites it for what is
installed then.
The interface's Reach screen offers it, beside Caddy and nothing in front.
Tests: the snippets render for each shape and leave out what isn't
installed; they pass `nginx -t` and `caddy validate`.
e2e/cases/proxy-snippets.sh installs nginx, installs behind it, loads the
written file and reaches the server, console and webmail through it on
443, with port 80 passing a challenge to the server and redirecting the
console: 13/13. interface, install-local, install-host, install-public,
status-export and topology pass unchanged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The plan, the usage text and the docs all said
--proxy snippetswrites configuration for the web server already on the machine. Nothing did. Now it writes:<dir>/proxy/nginx-inbuxa.conf:X-Forwarded-Foris set to the client's address, since the server trusts it.ssl_certificatepaths follow a pattern (/etc/ssl/inbuxa/<name>.fullchain.pem) for the operator to fill or edit.<dir>/proxy/Caddyfile.fragment: the same for Caddy. It has no global block, so it imports beside other sites. It leaves HTTP-01 for the server's names to the server, as the managed Caddy does.That web server becomes the proxy, so it's treated the way the managed Caddy is: the server trusts its
X-Forwarded-Forand exempts its address from the auto-ban. That address is 127.0.0.1 for a server on the host. For a server in a container it's also the project network's gateway (.1), since a request to a published loopback port reaches the container from there.Nothing is loaded or reloaded. The summary names the directory, and the log says to turn on the mail server's own certificates in the console once the file is loaded. A re-run rewrites it for what's installed at that point. The interface's Reach screen now offers it alongside Caddy and "nothing in front", and the README drops the "not built" note.
Tests
nginx -tandcaddy validate.e2e/cases/proxy-snippets.sh, 13/13: installs nginx, installs the suite behind it, loads the generated file with self-signed certificates, and reaches the server (307), the console and the webmail through nginx on 443. Port 80 passes a challenge through to the server (its JSON 404, not nginx's page) and redirects the console. A re-run converges and rewrites the file.systemctl reload nginxreturned, while nginx's old workers were still answering; a 3-second settle fixed it.