Setup
Put it behind a reverse proxy with TLS
The product assumes something in front of it is terminating TLS, because every organization already has an opinion about certificates and none of them want a tool to have its own.
What to do
-
Leave it listening on loopback, which is the default.
-
Point a server block at it, forwarding the host and the original scheme so that redirects and cookies come back right.
-
Allow a generous body size and a long read timeout. Some pages assemble a lot and a scan log is a long response.
-
Set the reachable address in Notifications so that links in Slack and mail point somewhere that works from outside the host.
A tip
If sign in loops, the proxy is not forwarding the original scheme, so the application thinks it is on plain HTTP and refuses to set a secure cookie.
Other guides
Install the editor plugin on Windows
VS Code, Cursor, IntelliJ and Eclipse, from your own server rather than a marketplace.
ReadInstall the editor plugin on macOS or Linux
The same three files, with the paths and the package manager that platform uses.
ReadExclude one credential everywhere it appears
The same test key committed to nine repositories, set aside once.
Read