Become a Patron!
VU Host timing out constantly
- Thread starter M5amhan
- Start date
wasteyrself
Member For 4 Years
Member For 3 Years
Member For 2 Years
Member For 1 Year
Member For 5 Years
I don't know how VU is hosted, but I've noticed this forum's software does a ton of background AJAX checks to keep you informed of the latest alerts / posts in the thread, which can be very intensive if this is hosted in a shared environment. As the place grows I can see that becoming more of a problem, necessitating the site being moved to a server it has full control over for maximum resources.
I'm not saying that's what's happening here, but it might contribute to it.
I'm not saying that's what's happening here, but it might contribute to it.
Assumptions are the mother of all fuck ups-- This is a problem on your side the VU has not been timing out at all I attach from many different sources
I would check your web browser if thats not the problem call your ISP its on your side
Simply use Ping and figure out the route times.
yes I was going to say use traceroute and see if there are any bottle necks at any of the access points but I made the assumption woops
that the op was not savvy
wasteyrself
Member For 4 Years
Member For 3 Years
Member For 2 Years
Member For 1 Year
Member For 5 Years
Yeah, if you did a traceroute to vapingunderground.com from your computer you're having trouble with, it would identify if the issue exists on your end or the site's end.
http://www.mediacollege.com/internet/troubleshooter/traceroute.html
http://www.mediacollege.com/internet/troubleshooter/traceroute.html
How helpfull you are I was too lazy to get a web based traceroute link
I have been bad again
Thanks for the help. Tried what was suggested got results but don't understand them. As follows
Tracing route to vapingunderground.com [162.159.249.230]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 16 ms 17 ms 13 ms tl11bu.wp.shawcable.net [64.59.178.225]
4 11 ms 9 ms 11 ms rc2nr-hge0-19-0-0.wp.shawcable.net [66.163.73.19
7]
5 32 ms 34 ms 43 ms 66.163.76.22
6 34 ms 34 ms 37 ms 66.163.66.58
7 32 ms 33 ms 31 ms gw-cloudflare.torontointernetxchange.net [206.10
8.34.208]
8 36 ms 31 ms 31 ms 162.159.249.230
Trace complete.
Tracing route to vapingunderground.com [162.159.249.230]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 16 ms 17 ms 13 ms tl11bu.wp.shawcable.net [64.59.178.225]
4 11 ms 9 ms 11 ms rc2nr-hge0-19-0-0.wp.shawcable.net [66.163.73.19
7]
5 32 ms 34 ms 43 ms 66.163.76.22
6 34 ms 34 ms 37 ms 66.163.66.58
7 32 ms 33 ms 31 ms gw-cloudflare.torontointernetxchange.net [206.10
8.34.208]
8 36 ms 31 ms 31 ms 162.159.249.230
Trace complete.
wasteyrself
Member For 4 Years
Member For 3 Years
Member For 2 Years
Member For 1 Year
Member For 5 Years
Since the site is hidden completely behind CloudFlare, we won't be able to tell for sure if it's just an issue with the CloudFlare node you get redirected to (which is very much a possibility, as we all get sent through different nodes dependent on our geographic location and thus might not experience the same issue), or if it's a problem with your ISP, or if the issue actually lies with the VU hosting beyond the CloudFlare wall of fire. Regardless, there's not much you or anyone else can do about it I believe, it would take some investigation from the backends of each service to identify the true culprit.
I have no issue here, tried a traceroute from the US and it's fast.
I tried from Germany and it locked up just before SF in Cloudflare's servers. Perhaps they filter users outside of the USA differently?
Or, a peering issue..Shaw is rather crappy... ;-)
I tried from Germany and it locked up just before SF in Cloudflare's servers. Perhaps they filter users outside of the USA differently?
Or, a peering issue..Shaw is rather crappy... ;-)
wasteyrself
Member For 4 Years
Member For 3 Years
Member For 2 Years
Member For 1 Year
Member For 5 Years
Ugh. Having really awful flashbacks to BGP issues in the NOC. The network engineers who keep us all connected don't get enough credit.
wasteyrself
Member For 4 Years
Member For 3 Years
Member For 2 Years
Member For 1 Year
Member For 5 Years
Yeah, that would help troubleshoot for sure. Same with trace routing from online services like CaFF just did.
If you aren't in the USA, try this proxied version, see if it helps.
https://www.bypassable.com/browse.php/L5UIxcK6/MVUDDeSj/dvsfS8MM/V0zhXy87/b4/fnorefer
If you are on a cell phone..well that another can of worms altogether.
https://www.bypassable.com/browse.php/L5UIxcK6/MVUDDeSj/dvsfS8MM/V0zhXy87/b4/fnorefer
If you are on a cell phone..well that another can of worms altogether.
Ya, that was just the edge routers..so on a consumer level it wouldn't help much. I just wanted to see if there was a router down.
A lotta shit has to go just right in order for anything to work on the Internet.
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out. Thats the issue, right after your local address of 192.168.0.1, it times out
3 16 ms 17 ms 13 ms tl11bu.wp.shawcable.net [64.59.178.225]
Are you running a local firewall or firewall on your cable router?
2 * * * Request timed out. Thats the issue, right after your local address of 192.168.0.1, it times out
3 16 ms 17 ms 13 ms tl11bu.wp.shawcable.net [64.59.178.225]
Are you running a local firewall or firewall on your cable router?
Just setup openvpn on us1 located in washington. Connects perfect. Wow you realize how well this site really works till it doesn't.
Must be something wrong with the node to VU server I was defaulting to. This will work for me. Just have to diasble for peer2peer
Must be something wrong with the node to VU server I was defaulting to. This will work for me. Just have to diasble for peer2peer
wasteyrself
Member For 4 Years
Member For 3 Years
Member For 2 Years
Member For 1 Year
Member For 5 Years
No, in a trace route it's okay if intermediate steps in a trace time out, some of these routers we hit on the way to our endpoint don't respond to ping packets but still pass on our traffic, and since the ping doesn't respond it gets registered as a timeout even though it continues on just fine. It's similar to how when you measure packet loss between two points, all the packet loss in between the beginning and the end is irrelevant as long as the last hop has no packet loss. IT can be weird like that.
"Just have to disable for peer2peer". That might be the issue with your local isp possibly blocking p2p connections.
No What I mean is the free vpn doesn't allow P2P downloading so if i wanted to do some I would have to disable the vpn first. Otherwise I'm surfin invisible from washington.
CJ
VU Webmaster
Staff member
VU Senior Leadership
VU Senior Administrator
VU Administrator
Senior Moderator
VU Donator
Platinum Contributor
ECF Refugee
Member For 5 Years
Reddit Exile
VU Patreon
Just wanted to chime in and say we're not on a re-seller setup or shared hosting.
I appreciate the 'tech' savvy ones replying and they were correct as we've not had any downtime's since the first few days of VU *knock on wood*
I appreciate the 'tech' savvy ones replying and they were correct as we've not had any downtime's since the first few days of VU *knock on wood*