Configuring the correct primary base URL within Uptime Kuma is essential for its proper operation. This fundamental setting dictates how Uptime Kuma generates URLs for various functions, including status pages, notifications, and internal operations. An improperly configured base URL can lead to broken links, malfunctioning notifications, and an overall degraded monitoring experience.
Understanding the Base URL
The base URL acts as the foundation for all URLs generated by Uptime Kuma. It typically follows the format `http://your-domain.com:port` or `https://your-domain.com:port`. The port is only necessary if Uptime Kuma isn’t running on the standard HTTP (80) or HTTPS (443) ports.
Accessing the Base URL Setting
The base URL can be configured within Uptime Kuma’s settings panel, typically accessible through the web interface.
Using a Reverse Proxy (Nginx, Apache)
When using a reverse proxy, configure the base URL to reflect the external URL users will access, not the internal Uptime Kuma server address.
Docker Deployments
In Docker deployments, the base URL should align with how the container is exposed to the network, considering any port mappings or reverse proxy configurations.
Implications of an Incorrect Base URL
An incorrect base URL can lead to broken links on status pages, preventing users from accessing detailed monitoring information. It can also disrupt notification mechanisms, hindering timely alerts about downtime.
Testing the Configuration
After configuring the base URL, thoroughly test all functionalities, including status page access and notification delivery, to ensure correct operation.
Using Subdirectories
If Uptime Kuma is installed in a subdirectory (e.g., `your-domain.com/uptime-kuma`), include the subdirectory in the base URL.
Security Considerations with HTTPS
Using HTTPS is strongly recommended for security. Ensure your base URL starts with `https://` if you have an SSL certificate installed.
Multiple Instances of Uptime Kuma
Each instance of Uptime Kuma requires its unique base URL, especially if they are publicly accessible.
Tips for Correct Configuration
Double-check the URL for typos, especially in the domain and port number.
Ensure consistency between the base URL and how Uptime Kuma is accessed.
Consult the official Uptime Kuma documentation for specific instructions related to your deployment environment.
If issues persist, review server logs for potential clues and seek community support.
How do I change the base URL after initial setup?
Access the Uptime Kuma settings panel through the web interface and modify the base URL field. A restart may be required for the changes to take effect.
What if I’m using a custom domain?
Enter the custom domain in the base URL setting, ensuring it points to your Uptime Kuma instance.
My notifications aren’t working after changing the base URL. What should I do?
Verify the base URL is correctly configured and test the notification delivery mechanism within Uptime Kuma’s settings. Check server logs for any error messages related to notifications.
Can I use an IP address instead of a domain name for the base URL?
While technically possible, using a domain name is preferred for better readability and compatibility with various services.
Proper configuration of the primary base URL is paramount for maximizing Uptime Kuma’s effectiveness. By following these guidelines, administrators can ensure seamless monitoring and reliable notifications, contributing to a robust and proactive approach to website uptime management.