Help for owners
My website opens for me but customers say it does not
Short answer
A site can work for you and fail for others because of caching, DNS changes that have not reached everyone, a certificate problem, or a block based on country or network. Ask a customer for a screenshot, device, network and time. Do not change settings until you know who is affected.
Does this sound like your situation?
- It loads on my office computer, but a customer sees an error.
- It works on my phone and not on theirs.
- Customers in one country or on one network cannot open it.
- The problem began after a domain, host or security change.
- I only test while logged in.
Why does this happen?
DNS changes reach people at different times
Cloudflare explains that a record's TTL controls how long it is cached and so how long updates take to reach users. It adds that local DNS caches may take longer than five minutes to update. After a move, some people see the new site and some the old.
Confirmed by developers.cloudflare.com
A certificate problem shows only on some devices
An incomplete certificate chain can pass on one browser and fail on another.
Technical detail: The site looks fine in a browser but its SSL chain is incomplete
Your own browser remembers the old page
Your computer can keep a saved copy, or stay logged in, so you do not see what a new visitor sees.
A firewall or security rule blocks some visitors
A rule meant to stop attackers can block a country, a network or a phone carrier.
What can I do about it today?
- Ask the customer for four thingsA screenshot of the error, their device and browser, their country or network, and the time it happened.
- Test it as a stranger wouldOpen the site on mobile data with wifi off, and in a private window.
- Do not change DNS, hosting or security settings yetChanges made without knowing who is affected can make it worse.
- Recall what changed recentlyA new host, certificate, plugin, firewall rule or domain edit. Write down the date.
- Count how many people are affectedA few complaints or many, and whether they share a place or a device.
When should I bring someone in?
- Customers cannot buy or log in.
- You cannot see the error yourself.
- The problem started after a migration.
How do I handle it?
- Reproduce it from different placesI test the site from other networks and devices, and read the DNS and certificate as they are published.
- Compare what different people receiveI check whether the answers differ by place, device or cache.
- Find the one differenceA record, a certificate, a rule or a cache is the cause, and I fix that one.
- Confirm with the customerI ask the customer who reported it to check again, and add a monitor from outside.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is the problem on the customer's side?
Sometimes, but I check it from several places before saying so.
How long do DNS changes take to reach everyone?
It depends on the record's TTL and local caches. Cloudflare says local caches may take longer than five minutes.
Should I clear my cache?
It is harmless and worth a try, but it does not help customers.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.