|
3 | 3 | Once you have a working Stalwart installation, you'll need to fix up a few things in its configuration to reach a baseline point of normal operation. We won't cover full domain setup here, just enough to get Stalwart stable. |
4 | 4 |
|
5 | 5 |
|
| 6 | +- [Connect to the Stalwart Admin Console](#connect-to-the-stalwart-admin-console) |
6 | 7 | - [Create and Validate an SSL Certificate](#create-and-validate-an-ssl-certificate) |
7 | 8 | - [Export and Format the SSL Certificate for Stalwart](#export-and-format-the-ssl-certificate-for-stalwart) |
8 | 9 | - [Basic Stalwart Network Setup](#basic-stalwart-network-setup) |
9 | 10 | - [Preventing IP Address Blocks](#preventing-ip-address-blocks) |
10 | 11 | - [Resolving IP Address Blocks](#resolving-ip-address-blocks) |
11 | 12 |
|
12 | 13 |
|
| 14 | +## Connect to the Stalwart Admin Console |
| 15 | + |
| 16 | +Stalwart's web admin console is intentionally made generally unavailable. The nginx proxy accomplishes this by intercepting HTTP traffic and returning a 404 for a handful of paths we do not wish to expose. The admin panel is only accessible through Tailscale. General documentation on our Tailscale implementation can be [found here](https://github.com/thunderbird/platform-infrastructure/blob/main/docs/tailscale.md). |
| 17 | + |
| 18 | +- Log into the [Tailscale web console](https://login.tailscale.com). |
| 19 | +- Click the "Machines" tab along the top. |
| 20 | +- Find and click the machine matching the Stalwart installation you want to log into. This will be labeled something like "tb-dev-stalwart-mgmt". |
| 21 | +- Find the "Full domain" property and copy it. |
| 22 | +- With Tailscale installed and running on your machine, open that domain in a web browser. |
| 23 | + |
| 24 | +This should land you on the Stalwart admin panel login page. Log in with credentials found in the relevant `stalwart-recovery-admin` secret in AWS Secrets Manager for that same environment. |
| 25 | + |
| 26 | + |
13 | 27 | ## Create and Validate an SSL Certificate |
14 | 28 |
|
15 | 29 | Determine your domain. For this example, we'll use `mail.example.com`. |
@@ -92,13 +106,6 @@ You can now use this certificate in other Stalwart settings, such as the basic n |
92 | 106 |
|
93 | 107 | ## Basic Stalwart Network Setup |
94 | 108 |
|
95 | | -Log into your Stalwart's admin web console. Here are the known instances: |
96 | | - |
97 | | -- [tb-dev](https://mail.dev-thundermail.com/admin/login) |
98 | | -- [tb-prod](https://mail.tb.email/admin/login) |
99 | | - |
100 | | -You can get the login credentials from the relevant `stalwart-recovery-admin` secret in AWS Secrets Manager. |
101 | | - |
102 | 109 | First, configure a domain. |
103 | 110 |
|
104 | 111 | - Go to Management ⇢ Domains ⇢ Domains. |
|
0 commit comments