[Technical Issue] Small problem

Anduril

Kage in the Making 👑
Legendary
Joined
Mar 17, 2011
Messages
12,892
Reaction score
909
I keep getting this "error: connection timedout" message while browsing NB.

This has been happening for the past few hours I guess. I thought it was an issue with my browser and so I did all the usual tuning up like clearing the cache and all, after that I visited some other sites and forums, they were loading just fine.

My browser is chrome. Also sometimes the page loads but somewhat like this,

You must be registered for see images


You must be registered for see images


You must be registered for see images


This happens when I am going from one thread /section to another or from one page to another in a thread.
And once this error code is displayed it reloads almost instantly (sometimes).

P.S: Hell I cannot even edit my post without getting this message now.
 
Last edited:

iNotorious

Sage of Six Posts 🔮
Immortal
Joined
Dec 6, 2012
Messages
80,546
Reaction score
4,116
I also experienced the same thing in my laptop, the way i fixed it was clearing the cookies. Delete your web browser cookies and try again.
 

Trúth

Kage in the Making 👑
Legendary
Joined
Mar 23, 2014
Messages
12,293
Reaction score
1,518
Happens to me all the time. It either fixes itself in a few hours or once, a couple of days.
 

Torche

Sage of Six Posts 🔮
Immortal
Joined
May 15, 2013
Messages
58,956
Reaction score
3,171
I get this too... Usually if I just stop the loading and try again within a few seconds to minutes it works.

Your's sounds quite severe though.
 

Anduril

Kage in the Making 👑
Legendary
Joined
Mar 17, 2011
Messages
12,892
Reaction score
909
I also experienced the same thing in my laptop, the way i fixed it was clearing the cookies. Delete your web browser cookies and try again.

Already did that as I stated.

Happens to me all the time. It either fixes itself in a few hours or once, a couple of days.

And now its back to normal lol

I get this too... Usually if I just stop the loading and try again within a few seconds to minutes it works.

Your's sounds quite severe though.

I think its fixed now.

Thread can be closed I guess. :wesobi:
 
Top