# When a connection stops working > If InfraNest can't reach one of your provider accounts, it tells you once, keeps trying in the background, and tells you again when it's fixed — it will not… Source: https://infranest.io/docs/when-a-connection-stops-working Last updated: 2026-10-26 --- If one of your connected provider accounts stops working, InfraNest handles the alerting for you — this article explains what happens and what to do about it. It's for anyone who connects providers like Cloudflare, DigitalOcean or Hetzner to InfraNest. ## Overview - Every connection syncs on a schedule. When syncs start failing, InfraNest opens one incident for that connection and figures out what kind of problem it is. - A rejected key needs you to act. A provider having temporary trouble usually clears up on its own. - One connection means one incident, even if it affects several things at once — you won't get separate alerts for each. > [!NOTE] > InfraNest tells you once when something breaks, keeps trying quietly in the background, and tells you again when it's fixed. It will not email you on every failed attempt. ## What you'll receive - **One email when it opens** — it explains what broke in plain words, whether you need to do anything, which of your data is now out of date, how long it's been failing, and how many attempts have been made. The provider's own error message is included at the bottom. - **Occasional reminders if it stays broken** — after about an hour, then six hours, then once a day. These are headed "is still failing" so you can tell them apart from a new problem. - **One email when it recovers**, telling you how long it was down. InfraNest waits until the connection has stayed healthy before sending this. The bell inside InfraNest and the banner on the connection's page always show the current state, even when no email has been sent. ## When a connection isn't syncing at all Some states stop syncing completely until you act: - **The connection is disabled** — you or a teammate switched it off. - **Its key isn't verified** — it was never checked, or editing the connection cleared the check. - **It needs to be reconnected** — for a connection made with a **Connect** button, the provider has stopped accepting InfraNest's access. - **The provider refused its key** — refused once, then refused again when InfraNest checked. InfraNest stops calling the provider with that key and checks it once a day, starting again automatically once the key works. Updating the key, or pressing **Check**, brings it back straight away. The domains, DNS zones, servers, volumes, load balancers, firewalls and networks that belong to such a connection stay where they are. Nothing is deleted, but they stop updating, so InfraNest says so: - **In a list**, the row shows something like "Not syncing · last synced 3 days ago." Hover over it to see why. - **On the detail page**, a banner explains what happened, with a button that takes you to the fix. > [!NOTE] > A domain can renew at the registrar while its connection is off, and InfraNest won't see it. You'll still get the expiry warning, with a note that the date isn't confirmed, why, when it was last checked, and how to fix it. ## See what's wrong 1. Open **Integrations** in the sidebar. 2. Pick the connection that's affected. 3. Read the banner at the top of the page. It shows the same message on the Integrations list, the integration's page and the account's own page, and includes: - what happened, for example "Cloudflare stopped accepting the sign-in for Main account"; - what it means — what's out of date, and that your services at the provider aren't affected; - anything paused because of it, on one line rather than as a second warning; - one button: **Sign in to {provider} again** for a connection you signed in with, **Update the API key** for one with a key, or a fix button that walks you through it step by step. 4. Open **Technical details** if support needs the provider's own error message. ![When a connection stops working](/media/fb67e639-0259-4647-9d67-ba56a286fd90) ## Fix a rejected key 1. Open **Integrations** and select the connection. 2. Use **Update key** (or **Edit**) on the connection. 3. Enter the new key and select **Save changes**. 4. Wait for the next sync — the incident closes itself once that sync succeeds, no extra confirmation needed. > [!WARNING] > A new key must be for the same provider account. If it belongs to a different account, InfraNest will say so and save nothing, so your domains and servers stay linked to the original. To manage the other account as well, connect it as a new integration. ## Mute or stop the emails 1. To mute for a day, select **Mute for 24 hours** in the alert email, or open the connection and use the same button in the **Alerts** panel. 2. To check how long a mute has left, or end it early, open the **Alerts** panel and select **Unmute**. 3. To turn error emails off completely, use the permanent switch in the **Alerts** panel — this is separate from the 24-hour mute. In-app alerts still appear either way. ## Tips - Muting a connection mutes both halves of the conversation — you won't get the "recovered" email either. - The mute applies per connection, not per provider, so two accounts with the same provider are muted separately. ## Troubleshooting - **No email arrived for a brief outage** — this is by design. A short provider hiccup often produces no email at all, since InfraNest waits out a quiet period before alerting. If a banner says nobody's been emailed yet, the incident is still inside that waiting period. - **Re-authorising signs in to the wrong account** — if you're logged in to a different account in your browser for that provider, InfraNest will say so and change nothing, keeping your domains and servers linked to the original account. Sign in to the right account and try again, or connect the other account as a new integration if you meant to add it. - **The key still won't be accepted** — InfraNest checks a refused key once a day on its own; you don't need to keep retrying manually. Fixing it at the provider and pressing **Check** (or updating the key) brings syncing back immediately instead of waiting for the daily check.