AutoKuma is a utility that automates the creation of Uptime Kuma monitors based on Docker container labels. With AutoKuma, you can eliminate the need for manual monitor creation in the Uptime Kuma UI.
MIT License
312
stars
15
forks
source link
CA certificates bundle is missing from the container causing Error during connect #34
Connecting to an uptime-kuma instance being a reverse proxy that serves a TLS certificate, it is not able to connect unless you install certificate bundles inside the container.
By default, if you launch AutoKuma with AUTOKUMA__KUMA__URL set to "wss://uptime-kuma.example.com" (a TLS (https) connection instead of a plaintext WS (http) connection) it will fail using a generic "Error during connect" message.
When you install the CA Bundles inside the container by running:
It instantly resolves and is able to connect to the Uptime Kuma instance. I would suggest to add this to the Dockerfile or some other solution where the CA bundles are part of the container so that TLS connections can be used as well
Error when trying to connect to an uptime kuma instance being a reverse proxy.
ERROR [kuma_client::util] Error during connect
DEBUG [kuma_client::client] Waiting for connection
DEBUG [kuma_client::client] Connection opened!
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
DEBUG [kuma_client::client] Waiting for Kuma to get ready...
WARN [kuma_client::client] Timeout while waiting for Kuma to get ready...
ERROR [kuma_client::util] Error during connect
Connecting to an uptime-kuma instance being a reverse proxy that serves a TLS certificate, it is not able to connect unless you install certificate bundles inside the container.
By default, if you launch AutoKuma with
AUTOKUMA__KUMA__URL
set to"wss://uptime-kuma.example.com"
(a TLS (https) connection instead of a plaintext WS (http) connection) it will fail using a generic "Error during connect" message.When you install the CA Bundles inside the container by running:
It instantly resolves and is able to connect to the Uptime Kuma instance. I would suggest to add this to the Dockerfile or some other solution where the CA bundles are part of the container so that TLS connections can be used as well
Error when trying to connect to an uptime kuma instance being a reverse proxy.