8

Troubleshooting

Louis Lam edited this page 2025-05-19 18:40:15 +08:00

Table of Contents

• Uptime Kuma reports DOWN, but the service can be accessed
• IPv6

Uptime Kuma reports DOWN, but the service can be accessed

Tip

In case you did not know: docker has more than one network type with only some of them allowing access to the local network and some not even allowing access to remote networks

If your Uptime Kuma reports DOWN of your service, knowing if it is a bug of Uptime Kuma / a docker network misconfiguration or a firewall is a good start to fixing the issue.

To debug this, go into your container's bash via

docker exec -it uptime-kuma bash

Install curl

apt update && apt --yes install curl

Then you can debug this issue with commands like ping, curl, ... Examples:

curl https://google.com
ping google.com

IPv6

If you are running Uptime Kuma on top of Docker and the service can only be access via IPv6. Please follow the Docker's official wiki to enable IPv6 support.
IPv6 are not supported out of the box on Docker.

• Home
• Troubleshooting

Installation & Configuration

• 🔧 How to Install
• 🆙 How to Update
• Environment Variables
• (Beta) Migration from v1 to v2

Features

• Reset Password via CLI
• Status Page
• Notification Methods
• Badge
• How to Monitor Docker Containers
• Maintenance
• 3rd Party Addons/Apps
• API Keys

Network

• Reverse Proxy
• Reverse Proxy with Cloudflare Tunnel
• Cloudflare Side Note

Integrations

• Prometheus Integration
• Systemd Unit File
• OpenRC Script

Development & Contributions

• CONTRIBUTING Rules & Guide
• How to Translate
• Setup Development Environment
• Test Pull Requests
• Development Side Notes
• API Documentation

More

• Supported Versions
• MIT License
• Videos By Youtubers

Edit this page