HTTPS setup broken?

[joepio]

Just tried deploying to staging, noticed that HTTPS setup doesn't work:

2024-01-05T16:38:30.239706Z  INFO atomic_server::appstate: Initializing AppState
2024-01-05T16:38:30.239903Z  INFO atomic_server::appstate: Opening database at "/root/.local/share/atomic-data/store"
2024-01-05T16:38:30.323941Z  INFO atomic_server::appstate: Setting default agent
2024-01-05T16:38:30.324933Z  INFO atomic_server::appstate: Default Agent is set: http://localhost:9883/agents//SAgBCbY1RSh4QJlQk9d8CHbypvL4J5xHmklgabxVIs=
2024-01-05T16:38:30.325236Z  INFO atomic_server::appstate: Starting search service
2024-01-05T16:38:30.329386Z  INFO atomic_server::appstate: Starting commit monitor
2024-01-05T16:38:30.329805Z  INFO atomic_server::https: Creating LetsEncrypt account with email joep@ontola.io
2024-01-05T16:38:30.982786Z  INFO actix_server::builder: Starting 1 workers
2024-01-05T16:38:30.983209Z  INFO actix_server::server: Actix runtime found; starting in Actix runtime
2024-01-05T16:38:32.983419Z  INFO atomic_server::https: Testing availability of http://staging.atomicdata.dev/.well-known/acme-challenge/h9F69WGj67FfJYc16f39fKnF55j0WXvC8-TW0ncAtKQ
2024-01-05T16:38:32.986161Z  INFO atomic_server::https: Server for HTTP initialization running correctly
2024-01-05T16:38:33.592920Z  INFO atomic_server::https: order is not ready, waiting 500ms
2024-01-05T16:38:34.094915Z  INFO atomic_server::https: order is not ready, waiting 1s
2024-01-05T16:38:35.096500Z  INFO atomic_server::https: order is not ready, waiting 2s
2024-01-05T16:38:37.097279Z  INFO atomic_server::https: order is not ready, waiting 4s
2024-01-05T16:38:41.098415Z  INFO atomic_server::https: order is not ready, waiting 8s
2024-01-05T16:38:49.099691Z  INFO atomic_server::https: order is not ready, waiting 16s

Thoughts:

• There's a message missing: Server temporarily running in HTTP mode. This is a warning called in the very start of cert_init_server.
• The Server for HTTP initialization running correctly message means that the well known URL was working at some point
• Perhaps the server stopped? Seems odd, it should log that.

[joepio]

The .well-known URL is available.

And the acme challenge has a status of "valid" at some point:

https://acme-v02.api.letsencrypt.org/acme/chall-v3/302755283156/8VVuyg

But the order is not "valid" on my end.. Why?

related: djc/instant-acme#13

[joepio]

Various things were wrong with the example code. Works now!