will224
(Rambling Biped)
1
I’ve been getting the error below since yesterday. I was unable to access the community via the “My Feed” link for about 6 hours during the day yesterday. It works now, but I am still sporadically getting the error every 3 or 4 clicks.
I’m using Google Chrome Version 48.0.2564.109 m (64-bit) running on Windows 10 Pro.

1 Spice up
sarah
(Sarah Crook (Spiceworks))
2
Are you still seeing these issues? We had some pretty bad bugs pop up yesterday, but those should have all been resolved yesterday afternoon.
I hate to ask… but can you clear your cookies and temp cache and reboot your browser?
Hate to ask because you probably already did this…
1 Spice up
will224
(Rambling Biped)
4
Cookies are kill’t and browser restarted. I’ll report back if the issue persists.
will224
(Rambling Biped)
5
And it has persisted… Although, it is nowhere near as bad as yesterday. It seems like it happens randomly and if I hit refresh once or twice everything will load normal.
1 Spice up
sarah
(Sarah Crook (Spiceworks))
6
Where in the community are you seeing these issues? Which pages specifically, and where are you clicking from?
will224
(Rambling Biped)
7
They seem to happen most frequently when I click the “My Feed” link at the top of the page.
will224
(Rambling Biped)
8
I’m still getting these with a fair amount of frequency. Today has been worse than previous days this week.
sarah
(Sarah Crook (Spiceworks))
9
Thanks for the update! I’m going to have our IT team take a look and see if there is a piece of hardware acting up or something.
sarah
(Sarah Crook (Spiceworks))
10
Next time this happens, could you please give me a time stamp of when you see it occur, if you don’t mind? And where you clicked what item to receive the error? We’re having a really tough time tracking this one down.
will224
(Rambling Biped)
11
I just had this happen again at 1:05pm CST. It seems to most frequently happen when I leave a thread by clicking on “My Feed” at the top of the page.
1 Spice up
sarah
(Sarah Crook (Spiceworks))
12
So it turns out that one of our dev teams knows what caused it! And HOPEFULLY we’ll have a fix shipping this week. Sorry for the run-around and thank you for helping us try to figure out what’s going on here!
1 Spice up
will224
(Rambling Biped)
13
No problem, it has only been a very minor inconvenience and I’m glad I could help. Thank you for being so responsive!
1 Spice up
sarah
(Sarah Crook (Spiceworks))
14
Thank YOU for being so responsive! :]
1 Spice up