Waiting for key to get created...

[Silun]

After installing the container via Nextcloud AIO environment variable and stopping/starting all containers, this is all the container writes to the log:

2024-08-22T18:52:53.576355293Z Waiting for key to get created...
2024-08-22T18:52:58.588707514Z Waiting for key to get created...
2024-08-22T18:53:03.594662575Z Waiting for key to get created...
2024-08-22T18:53:08.597343968Z Waiting for key to get created...
2024-08-22T18:53:13.599429891Z Waiting for key to get created...
2024-08-22T18:53:18.602123338Z Waiting for key to get created...
2024-08-22T18:53:23.602920196Z Waiting for key to get created...
2024-08-22T18:53:28.607148151Z Waiting for key to get created...
2024-08-22T18:53:33.610736199Z Waiting for key to get created...
2024-08-22T18:53:38.612016357Z Waiting for key to get created...
2024-08-22T18:53:43.613385833Z Waiting for key to get created...
2024-08-22T18:53:48.617656502Z Waiting for key to get created...
2024-08-22T18:53:53.619140051Z Waiting for key to get created...
2024-08-22T18:53:58.620732931Z Waiting for key to get created...
2024-08-22T18:54:03.622413592Z Waiting for key to get created...
2024-08-22T18:54:08.625044704Z Waiting for key to get created...
2024-08-22T18:54:13.629275519Z Waiting for key to get created...
2024-08-22T18:54:18.629456331Z Waiting for key to get created...

I am not getting anything on port 10003 via my reverse proxy (NPM). It is unclear to me what I should be doing about this.

Is the container just broken or do the instructions miss essential steps?

[docjyJ]

Hi,

Thank you very much for your message!

The private key and certificate for ssl are configured automatically. But it only works with the Caddy Community Container.

I just finished working on a system to disable this configuration. I'll wait a few days to see if I can't find a bug on my server.

There are three options:

• Put your Nextcloud instance in beta to get the update that disables this feature.
• Wait a few days for me to push the update to latest.
• Configure the ssl key pair to the same path as the caddy community container.

See : https://github.com/docjyJ/aio-stalwart#use-your-own-certificate

I should consider adding a clearer message :sweat_smile:

Have a great day

[Silun]

Thank you! The way I understood it, the proxy just had to forward the right subdomain on the correct port, but apparently there is much more going on under the hood.

If I add the caddy container via passed env variable, will it just work, or do I need to configure caddy manually?

[docjyJ]

If you are talking about the AIO_COMMUNITY CONTAINERS variable of the AIO master container, yes it will work without any configuration!