Hello, My website `https://sale-php.rf.gd` was working fine last week, but now I’m getting a “This

[Chheang-Socheata]

Hello,

My website https://sale-php.rf.gd was working fine last week, but now I’m getting a “This site can’t be reached / ERR_CONNECTION_TIMED_OUT” error.

I checked:

• The site is up on https://downforeveryoneorjustme.com
• DNS records are resolving correctly on https://dnschecker.org
• My InfinityFree account is active
• Hosting IP: 185.27.134.224

I can’t access the site from my home network or browser (tested multiple), but it works for others.

[jaikrishna.t]

Welcome to the forum!
Your website loads fine for me.

You probably need to maybe:

• Clear your browser cache
• Clear DNS cache on your OS
• Restart router
• Try to access from different network or device

Try these and let us know the results.

[Chheang-Socheata]

it work when test on Mobile Network. but wifi is not.

[jaikrishna.t]

Probably your wifi provider is blocking the website or some bad cached records… try accessing in a private tab or different browser or clearing DNS cache on your computer:
Windows (Command Prompt):

ipconfig /flushdns

Mac/Linux (Terminal):

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

then try to access your website

[Frank419]

@jaikrishna.t

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

I hope you do realize this is a macOS only command. Yes, both macOS and Linux is Unix-like, but this doesn’t mean all of the commands are interchangable.

On Linux (systemd) there’s

sudo resolvectl flush-caches

I admit that I haven’t touched non-systemd Linux, so I cannot tell the command for other systems.

[Admin]

@Frank419

On Linux (systemd) there’s

sudo resolvectl flush-caches

I admit that I haven’t touched non-systemd Linux, so I cannot tell the command for other systems.

systemd-resolved is probably most common by now. Before the big systemd takeover, you had a hodgepodge of different resolvers, but dnsmasq was quite common for personal use. But I remember that at least Ubuntu didn’t have a local DNS resolver at all, so there was no local cache to begin with.