FAQ & Troubleshooting
Find answers to common questions and solutions to frequent issues.
Account & Login
How do I add a passkey?
Sign in, open Account → Security, and click Add passkey. Enter a name, click Create passkey, and follow your browser's prompt. See the passkey setup guide.
Can I still use my password after adding a passkey?
Yes. You can still sign in with your email and password or use Forgot password? to reset your password.
What if my passkey is unavailable or I lose my device?
Use another registered passkey or sign in with your email and password. If needed, select Forgot password? to reset your password using your account email. Once signed in, remove the unavailable passkey under Account → Security. See passkey recovery and troubleshooting.
Does removing a passkey delete it from my password manager?
No. Removing it in UptimeObserver prevents you from signing in with it. Delete the saved entry from your device or password manager separately. See removing a passkey.
Monitor Setup
"A friendly name is required."
Every monitor needs a name. Enter a descriptive name in the Friendly Name field so you and your team can identify it later.
"URL is required." / "URL is invalid."
For HTTP monitors, you must enter a valid URL. Make sure:
- The URL starts with https:// or http://
- For HTTPS monitoring, the URL must match the pattern https://.+
"Hostname is required."
For Ping and Port monitors, enter the target hostname or IP address (e.g., example.com or 1.1.1.1).
"Port is required."
Port monitors need a port number. Enter the port you want to check (e.g., 443 for HTTPS, 25 for SMTP).
"Expected Value is required."
DNS monitors with certain record types require an expected value to validate against the actual DNS response.
"Retries is required."
For HTTP, DNS, Port, and Ping monitors, set Retries from 0 to 5. This is a consecutive-failure threshold, not a count of immediate extra requests. See the retry table for the exact behavior. Heartbeat monitors apply a different retry rule to overdue checks after their expected ping interval and grace period.
Plan Limits
"Free accounts are limited to 5-minute monitoring intervals."
Minimum check intervals are 5 minutes on Free, 1 minute on Indie, and 30 seconds on Pro. See plans and limits.
"Free accounts are limited to 15-second request timeout."
Free has a maximum request timeout of 15 seconds. Paid plans support timeout controls up to 5 minutes. See monitoring controls.
"Free accounts are limited to a single monitoring region."
Free can select one monitoring region. Paid plans support up to four. See monitoring controls.
"This feature requires a premium plan. Please upgrade your plan."
You're attempting to use a paid-plan feature (for example, Slack setup, SSL-expiry checks, Heartbeat, or alert retrigger). Check plans and limits, including known differences between pricing and the dashboard, before upgrading.
"Indie Plan accounts are limited to 1-minute monitoring intervals."
Indie allows intervals as low as 1 minute; Pro allows 30 seconds. See advertised capacities.
False Downtime Alerts
If your monitor reports downtime but your site is working:
- Check firewall rules — Your firewall or WAF may be blocking UptimeObserver. See Bot Documentation for monitoring IPs to allow
- Verify from outside your network — Ensure the URL is accessible from external locations
- Check for geo-restrictions — Your site may be blocking requests from our monitoring regions
- Review rate limiting — Your server may be rate-limiting our monitoring requests, causing intermittent failures
Allow UptimeObserver on Cloudflare
Integration Issues
Slack
Token refresh failures (TOKEN_REFRESH_FAILED status): Re-authorize the Slack integration. Go to Integrations → Slack and click "Add Slack Configuration" to refresh the token.
NOT_INVITED status:
The UptimeObserver bot needs to be invited to your channel. Type /invite @uptimeobserver_bot in the Slack channel.
"No email configurations found. Add an email configuration to receive notifications..." You selected email alerts on a monitor but haven't configured an email integration yet. Go to Integrations → Email and add an email address first.
"No email settings configured yet. Add one in Integrations → Email." This warning appears in the alert type dropdown when no email configuration exists. Add one before assigning email alerts to monitors.
Data Display
"Not enough data. Monitor is new, check back soon"
New monitors need time to collect data before charts and metrics become available. Check back after a few monitoring cycles.
"No incidents to show" / "Great Job! No incidents to show"
Your monitor hasn't experienced any downtime since creation. This is expected for healthy services.
"Some domain extensions do not display expiry dates in WHOIS lookups."
Certain domain TLDs don't expose expiration dates via WHOIS. Domain monitoring may be unable to track expiry for these extensions.
DNS Propagation
DNS changes (such as setting up a custom domain for your status page) can take time to propagate:
- Typical propagation: A few minutes to a few hours
- Maximum: Up to 24 hours globally
- Verification: Use
digornslookupto check if your DNS records have propagated
Cloudflare & Firewalls
Cloudflare warning during HTTPS monitor creation
"If your website is running behind Cloudflare, please make sure to whitelist our IP addresses"
Cloudflare can block or challenge monitoring checks. Find the blocked request in Security Events, then follow the guide below to configure an exception for the feature responsible.
Allow UptimeObserver on Cloudflare
Does Web Bot Auth mean Cloudflare automatically allows the bot?
Not necessarily. UptimeObserver is a Cloudflare verified bot and signs HTTP checks automatically, but custom security rules and origin firewalls can still block requests. If Cloudflare blocks your checks, follow the Cloudflare configuration guide.
Do I need to enable Web Bot Auth in my monitor?
No. UptimeObserver signs all HTTP checks automatically, including retries and requests following redirects. You do not need to add signature headers. See Web Bot Auth for details.
Do I still need API credentials for a protected endpoint?
Yes. Web Bot Auth identifies the bot; it does not replace your application's authentication. Configure the required credentials in the HTTP monitor's request headers.
Still need help?
If your issue isn't covered here, reach out using the "Need Help?" button on the bottom right corner or email us at support@uptimeobserver.com.