Troubleshooting

Most issues come down to one of a handful of causes. Find your symptom below - and if you're still stuck at the end, we're happy to help.

I can't sign in, or my confirmation email hasn't arrived

New accounts have to confirm their email address before they can be used, so a brand-new signup that hasn't opened its confirmation email yet can't sign in.

• Check your spam folder, and add hello@pro-weather.com to your contacts.
• Ask for a fresh link. Try to sign in with your email and password: if the address is still unconfirmed we say so and offer Resend the link. Links last 24 hours and work once, so an old one won't do.
• Check the address for typos. If you signed up with one, the mail went to an address you don't read - sign up again with the right one.
• Signed up with Google or GitHub? There's nothing to confirm; use the same button on the sign-in page rather than an email and password.

My site shows "Coming soon"

Visitors see "Coming soon - this weather site is not published yet." That page appears whenever a site isn't live, for one of these reasons:

• It hasn't been published. New sites start as drafts. Open your site in the dashboard and choose Publish at the top (it's enabled once a station is connected).
• The free trial ended. Your site went offline when the trial expired. Subscribe to Pro and it comes straight back - your data and settings are kept, nothing is deleted.
• A subscription lapsed. If a payment fails repeatedly or a subscription is cancelled, the site is paused the same way, and reactivates automatically when the subscription is active again.

No readings, or "This site hasn't connected a weather station yet"

• Connect your station if you haven't: see Connect your WeatherLink station.
• Check the key type. Pro Weather needs a WeatherLink v2 API Key and Secret - not a v1 key, and not your weatherlink.com password.
• Check the station is online in WeatherLink. If weatherlink.com shows no current data, Pro Weather can't see any either. Fix the station's own connection first.
• Check the station selection. If your account has several stations, make sure the right one is chosen under Panels → Stations.

Readings look stale

Your site updates about every 5 minutes, and pages are briefly cached for speed, so readings can legitimately be a few minutes old - every page shows an "Updated …" time so visitors can tell. If it's been longer than an hour:

• Confirm the station is still reporting in WeatherLink (batteries and connectivity are the usual suspects).
• On the free WeatherLink Basic plan, stations upload every 15 minutes, so updates are naturally a little slower. See WeatherLink plans & your data.

A tab is missing

Tabs appear only when your station reports that data and the tab is enabled:

• Forecast, Astronomy and severe-weather warnings need your station's coordinates. On WeatherLink, set the location in WeatherLink, then open Connection → Reconnect & rediscover. For pushed hardware, enter the coordinates yourself on the Connection page, in the station card under the upload URL.
• Air quality needs a PM sensor reporting: a Davis AirLink on your WeatherLink account (registered as its own station is fine - it is found there automatically), an Ecowitt WH41/WH45/WH46, or the particulate fields in a weewx / Meteobridge / CumulusMX upload URL - a relay only sends what its URL asks for, so an AirLink it reads still won't appear until the upload URL carries AqPM2.5 and AqPM10. See Air quality.
• Sun needs a solar radiation or UV sensor.
• Almanac appears once your archive holds about a week of complete days, on the Pro plan or trial.
• Everything else: check the tile is ticked under Panels → Overview cards and the tab is on under Panels → Tabs & sections.

Charts won't go further back

Longer ranges unlock as your archive grows - 7 days of charts need about a day and a half of data, a year view needs about three months. See History, records & the almanac for the schedule.

You don't have to guess where you are: the History card on your site's Overview page shows how far back your archive reaches, which ranges that unlocks, when the next one arrives, and whether older readings are still coming in. The two cases that look identical on your public site have opposite answers:

• "Importing your WeatherLink archive" - nothing to do, the longer ranges appear on their own.
• "WeatherLink is not sharing your past readings" - WeatherLink refuses archive access, as the free Basic plan does. No import will ever run. Either upgrade your WeatherLink plan, or import a history file from weewx, CumulusMX or a CSV.

Full explanation of every state: Where your archive stands.

My uploads never arrive ("Nothing has been uploaded to this URL yet")

Your own hardware pushes to a personal upload URL, and the ingest card on the Connection tab tells you whether anything has ever reached it. If it says nothing has:

• Give it one upload interval. A gateway set to 60 seconds needs a minute; nothing appears before the first upload.
• Re-check server, path and port against the values on the card. A trailing slash, a missing /i/ path or the wrong port is the usual cause.
• Ecowitt gateways use port 80 and i.pro-weather.com, plain HTTP, with the short path. The HTTPS URL is for software uploaders like weewx.
• Regenerated the URL? The old one stopped working immediately - update your hardware with the new one.

See Connect other hardware for the per-device settings.

My cloud connection says "Reconnect needed"

An Ecowitt Cloud or Tempest connection shows Reconnect needed when the vendor rejects the stored keys - usually because you regenerated them, changed the account password, or removed the device from the account. Readings stop until you fix it:

• Create fresh keys (Ecowitt: application key + API key at ecowitt.net; Tempest: a personal access token at tempestwx.com) and paste them into the card on the Connection page.
• Everything resumes on the next refresh, including any history import that was still running. Nothing already archived is lost while the connection is down - but readings from the outage itself only come back if the vendor's history holds them.

A weather-network upload is failing

Each service on the Publishing page shows a badge; Failed means the network rejected the last upload. Expand the card to read the exact error it returned:

• Wrong credentials are the usual cause - a station ID or key mistyped, or regenerated at the network's side. We pause retries for an hour after a credential rejection; fix the values and save the card to retry on the next refresh immediately.
• CWOP needs a valid callsign-style station ID; ham callsigns must include their passcode.
• Add the "a weather-service upload is failing" event alert so a failing upload emails you instead of going unnoticed. See Publish to weather networks for per-service details.

Daily totals roll over at the wrong time

If your rain "today" resets at midnight but you report against a 9am observational day (or the other way round), set the weather day under Advanced → Weather day. It decides when one day's totals and records end and the next begin, and changing it re-reads your whole archive. See the weather day.

Severe-weather warnings never show

• The banner only appears while a warning is active for your area - no warnings, no banner.
• Warnings need your station's coordinates and the toggle under Panels → Tabs & sections → Severe-weather warnings.
• Coverage is Europe (MeteoAlarm) and the United States (National Weather Service). Stations elsewhere don't get warnings yet.

Alert emails aren't arriving

• Check your spam folder, and add hello@pro-weather.com to your contacts.
• Alerts go to your account email address - the one you sign in with.
• You get one email per episode: an alert won't fire again until the reading has dropped back out of the alert zone (and at most once every 30 minutes), so a hovering value doesn't flood you.
• Alerts are part of the Pro plan and trial - they pause if a plan lapses.

Webhook deliveries aren't reaching my server

• Use Send test under Alerts → Webhook and watch your receiver while it runs - it sends the same request a real alert does.
• The endpoint must be HTTPS, reachable from the internet (no private or loopback addresses), must not redirect, and must answer within 6 seconds.
• If your receiver verifies signatures, check it computes the HMAC over the raw request body, exactly as described in Alert webhooks - a re-serialised JSON body never matches.
• There is no retry queue: a failed delivery leaves the alert unlatched, so the next refresh (about 5 minutes) tries again while the condition still holds. A receiver that was briefly down misses nothing that is still true.

My history import reported failed rows

The weewx, CumulusMX and CSV importers read your file in the browser and report how many rows were imported and how many were skipped:

• A few skipped rows are normal - rows with no readings, impossible values, or timestamps that repeat are dropped individually, never the whole file.
• Skipped as duplicates means those moments are already in your archive - imports never overwrite a stored reading, so re-running a file is safe and reimports nothing.
• Whole file rejected: check you picked the right file (weewx wants weewx.sdb, Cumulus the monthly logs from its data folder) and, for CSV, that you mapped a timestamp column and at least one reading.

A new station or sensor doesn't show up

Added hardware in WeatherLink after connecting? Open Connection and choose Reconnect & rediscover - new stations and sensors (including AirLink) are picked up then, not automatically.

My custom domain isn't going live

See the dedicated custom domain troubleshooting - the usual causes are a missing A record, a record pointing at the wrong IP address, or Cloudflare's proxy (orange cloud) being enabled.

Google Analytics shows no visitors

See Add Google Analytics - most often it's the cookie banner (analytics only loads after a visitor accepts) or a GTM-/UA- ID pasted where a G- measurement ID belongs.