My site URL
http://svitlasvit.great-site.net/
Error Message in browser
ERR_CONNECTION_TIMED_OUT
Other Information
Creation Date of account - 2024-09-01. It’s been more than 2 weeks, but the site is still not working.
Hi and welcome to the forum
Your website redirects to “local” (incorrect address)
otherwise everything is fine with the domain, but some of the code you put for redirection is incorrect
also check the .htaccess code if you have created one
4 Likes
I cleaned the .htaccess and changed all the data in the database from “svitlasvit.local” to “svitlasvit.great-site.net”. The site is not working. There is an ERR_CONNECTION_TIMED_OUT error on the page. There are no errors in the browser console. Note: My site is powered by WordPress
Please clear the browser cache by pressing a few times Ctrl + F5 while viewing your website.
If that doesn’t help (because some browsers are stubborn) then follow these instructions
Or try another browser/device
The online test is here CLICK ME
5 Likes
I cleared the cache and cookies, tried to open the site on another device, but still the site does not appear. The error is the same - ERR_CONNECTION_TIMED_OUT
Try running this command in Powershell, cmd, terminal
tracert svitlasvit.great-site.net
and give us the result
OR
use this
you can help yourself with this and speed things up
P.S. most routers need a restart to pull new settings
3 Likes
The site is displayed via VPN. Could it be a problem with the provider ?
It starts from your computer and there may be a firewall or antivirus blocking the connection
after that, it can be FW in the router
after that it can be FW or AV with your ISP or your ISP leads you to a totally wrong IP (so run that command to see where the traffic is going - tracert)
Try using Cloudflare 1.1.1.1 from my previous post
all websites will open much faster
3 Likes
It’s technically possible. Do you get a different result if you try to visit your site without using a VPN? (With clearing your browser cache)
1 Like
I did not use the VPN with the “tracert” command. I didn’t clear the browser cache before entering the command. I think that there is no need to clean it, since the command is executed in the terminal, and not in the browser.
My apologies, that’s not the post I was replying to. Regardless, using tracert probably doesn’t work because of the security system:
My statement was inaccurate. My apologies for the mistake.
Thank you for sharing it!
This clearly point to an issue at your network provider. The first hop is your own router, then it goes into an endpoint from your ISP, and then it is routed to another internal address. It never leaves the network of your ISP, which could indicate a block at your ISP.
Please contact your ISP about this, they may be able to explain why this happens.
This is irrelevant, because the security system only restricts web requests, not tracerts. Tracerts work with ping, so you’ll be unable to trace the full path. But if you can see in the traceroute that your traffic never reaches our datacenter, then you definitely know something is wrong.
6 Likes
Got it. Thanks for your help.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.