You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I modified some code to print the details of httpsAgent before submit the request to docker host, and found the httpsAgent has been configured properly.
Is there anything wrong I've done? Or is there any compatible issue between Let's Encrypt's certification and axios?
🛡️ Security Policy
📝 Describe your problem
I've set up a uptime-kuma as a docker container, and everything's well, including monitor the docker host of it.
And then I tried to monitor the remote docker host, which the TLS certifications were generated by acme.sh through Let's Encrypt.
After docker host was set up, I test the TLS connection with below command inside of the uptime-kuma's docker container, and found it works:
But when I clicked the 'Test' button in the "Setup Docker Host" page, the backend printed below logs:
I modified some code to print the details of httpsAgent before submit the request to docker host, and found the httpsAgent has been configured properly.
Is there anything wrong I've done? Or is there any compatible issue between Let's Encrypt's certification and axios?
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.16
💻 Operating System and Arch
Ubuntu 24.04.1 LTS x64
🌐 Browser
Google Chrome
🖥️ Deployment Environment
Runtime:
Server: Docker Engine - Community
Engine:
Version: 27.3.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 41ca978
Built: Fri Sep 20 11:40:59 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.23
GitCommit: 57f17b0a6295a39009d861b89e3b3b87b005ca27
runc:
Version: 1.1.14
GitCommit: v1.1.14-0-g2c9f560
docker-init:
Version: 0.19.0
GitCommit: de40ad0
kuma's image:
louislam/uptime-kuma 1 542ef8cfcae2 6 weeks ago 440MB
Database: sqlite/embedded
Filesystem used to store the database on: SSD
number of monitors: 20
The text was updated successfully, but these errors were encountered: