> Markdown version of https://getuptimely.com/integrations/dokploy — the page itself is the canonical copy. Integrations × # Dokploy × Uptimely Connect Uptimely to Dokploy Community Edition once, then add uptime, [SSL certificate](https://getuptimely.com/features/ssl-certificate-monitoring) and domain monitors to any application, compose stack or database from its Monitoring tab, and watch the 30-day timeline without leaving Dokploy. [Start monitoring free →](https://app.getuptimely.com/accounts/register)[Get Dokploy Community](https://dokploy-community.devino.ca) How it works ## Connect, monitor, watch 1. ### 1Connect Uptimely once In Dokploy Community, open Settings → Integrations and press Connect Uptimely. Paste a project API key and the project ID (Test connection can fill the ID in for you). The Base URL already points at Uptimely. An optional status page slug shows a public status badge on each monitored service.  2. ### 2Monitor a service Open an application, compose stack or database and go to its Monitoring tab. The Uptime by Uptimely panel is opt-in: nothing is created until you press Monitor with Uptimely. You can add a path such as /health, and a reachability check shows each URL's HTTP status first.  3. ### 3Watch uptime The same panel then shows a status pill and a 30-day timeline for every monitor, with an Open in Uptimely link on each one. Uptimely checks every 5 minutes from outside your server.  What gets monitored ## Website, SSL, domain and port checks ### Website monitor One per HTTPS domain on an application or compose stack. Wildcard domains and preview-deployment domains are skipped. If you set a path to check, it is added to each domain. ### SSL certificate monitor Optional. Tick Also add SSL certificate and domain monitors and each distinct HTTPS host gets one. ### Domain monitor Optional, from the same checkbox: one per distinct HTTPS host, tracking the domain registration. ### Port monitor Databases get one on their external port. Expose the database on an external port first, or there is nothing to monitor. Uptimely checks the exact URL, so a path that answers 404 shows as Offline even when the rest of the site is up. This is what that looks like, and why the form has an optional Path to check.  Requirements ## What you need - Dokploy Community Edition. The integration is built into it; stock Dokploy does not have it. - An Uptimely project and one of its project API keys, created under Settings → API Keys in Uptimely. A key is locked to a single project. - An HTTPS domain on the service (or an external port on a database), so there is something to check. ### Limits to know about - Monitors cannot be deleted from Dokploy, because Uptimely's API has no monitor delete. Unlink only makes Dokploy forget the link. Delete the monitors in Uptimely. - One Uptimely project is connected per Dokploy organization. - Monitors that already exist for the same target are not created twice. FAQ ## Questions ### Does Dokploy have built-in uptime monitoring? Dokploy Community Edition does, through this integration. Connect Uptimely once under Settings → Integrations and every application, compose stack or database gets an opt-in Uptime by Uptimely panel on its Monitoring tab. Stock Dokploy does not include it. ### What does Uptimely create in my account? Press Monitor with Uptimely on a service and it creates one Website monitor per HTTPS domain. An optional checkbox adds an SSL certificate monitor and a Domain monitor for each host, and a database gets a Port monitor on its external port. Nothing is created until you press the button, and a monitor that already exists for the same target is not created twice. ### Why does my monitor show Offline when the site works? Uptimely checks the exact URL, which is the domain's host plus its path. A Website monitor is Offline unless that URL answers 2xx or 3xx, so a root path that returns 404 shows as Offline even when the rest of the site is fine. Unlink the service and monitor it again with a Path to check such as /health. The reachability check shows each URL's HTTP status before you create anything. ### Why does creating monitors fail? Check that the API key belongs to the project you linked and that the project has not reached its plan's monitor limit. Reading status works either way. ### Can I remove monitors from Dokploy? No. Uptimely's API has no monitor delete, so Dokploy cannot remove them. Unlink only makes Dokploy forget the monitors for that service, and disconnecting the integration removes the stored API key and every link. In both cases the monitors keep running in Uptimely until you delete them there. ### Can I connect more than one Uptimely project? Not per Dokploy organization. Each organization connects one Uptimely project, using a project API key that is locked to that project. Go further ## Setup guide and source [Full setup guide](https://dokploy-community.devino.ca/integrations/#uptimely-uptime-ssl-and-domain-monitoring) · [Dokploy Community on GitHub](https://github.com/DevinoSolutions/dokploy-community) · [All Uptimely integrations](https://getuptimely.com/integrations) [Start monitoring free →](https://app.getuptimely.com/accounts/register)