Unread can't be read

pie_flavor

Frequently this happens:

2019-01-02_03-02-15.mp4

kazitor

Frequently this happens:

inb4 WOMM

pie_flavor

@kazitor WOMM. Also, there's a bright blue Download button there.

Cursorkeys

@pie_flavor said in Unread can't be read:

@kazitor WOMM. Also, there's a bright blue Download button there.

Not working for me either, maybe a DNS issue?

Edit: Have you made it public? It's giving me a 403

loopback0

Video works for me.

I've had the same issue a couple of times this morning - refreshing the page gives a 502 from nginx. Leaving it a few seconds and refreshing again works.

boomzilla

Yeah, I've been getting these 502s too. Found this in the nginx error.log:

2019/01/02 12:20:52 [error] 1317#1317: 
 *8103659 no live upstreams while connecting to upstream, client: boomzilla.s.ip.address,
 server: what.thedailywtf.com, request: "GET /assets/src/client/topic/public/src/client/topic/replies.js.map HTTP/2.0",
 upstream: "http://nodebb/assets/src/client/topic/public/src/client/topic/replies.js.map", host: "what.thedailywtf.com"

2019/01/02 12:20:52 [error] 1317#1317:
 *8103659 no live upstreams while connecting to upstream,
 client: boomzilla.s.ip.address,
 server: what.thedailywtf.com,
 request: "GET /assets/src/modules/public/src/modules/notifications.js.map HTTP/2.0",
 upstream: "http://nodebb/assets/src/modules/public/src/modules/notifications.js.map",
 host: "what.thedailywtf.com"

2019/01/02 12:20:52 [error] 1317#1317:
 *8103659 no live upstreams while connecting to upstream,
 client: boomzilla.s.ip.address,
 server: what.thedailywtf.com,
 request: "GET /assets/src/modules/public/src/modules/sounds.js.map HTTP/2.0",
 upstream: "http://nodebb/assets/src/modules/public/src/modules/sounds.js.map",
 host: "what.thedailywtf.com"

2019/01/02 12:20:52 [error] 1317#1317:
 *8103659 no live upstreams while connecting to upstream,
 client: boomzilla.s.ip.address,
 server: what.thedailywtf.com,
 request: "GET /assets/src/modules/public/src/modules/search.js.map HTTP/2.0",
 upstream: "http://nodebb/assets/src/modules/public/src/modules/search.js.map",
 host: "what.thedailywtf.com"

boomzilla

Looks like a bot woke up. Hmmm...

boomzilla

@boomzilla yep:

"Linguee Bot (http://www.linguee.com/bot; bot@linguee.com)"

Seems to be doing one request per second, which is what robots.txt says to do.

Benjamin Hall

Is this what's causing me to get "an internal error occurred" about 80% of the time I try to go to unread or recent?

dkf

@boomzilla said in Unread can't be read:

upstream: "http://nodebb/assets/src/modules/public/src/modules/search.js.map",

That looks like a highly suspicious URL, unless someone paid rather more money to ICANN than I think is sensible…

izzion

@Benjamin-Hall
I think it's more that the servers have become sentient and turned into a @boomzilla alt. Once they learn how to re-write error pages into a custom page, they'll replace the 502 with:

boomzilla

I put Linguee on the bad bots list.

@dkf said in Unread can't be read:

@boomzilla said in Unread can't be read:
upstream: "http://nodebb/assets/src/modules/public/src/modules/search.js.map",
That looks like a highly suspicious URL, unless someone paid rather more money to ICANN than I think is sensible…

Hmm...yeah...I recognized the file structure and tuned out...it's obviously missing the domain name. But maybe that's implicitly using the server or the host otherwise identified in the error.

dkf

@boomzilla said in Unread can't be read:

But maybe that's implicitly using the server or the host otherwise identified in the error.

No, then that would be http:/nodebb/… with a single /. With a double //, the first part afterwards is a service identifier.

boomzilla

Since I stopped allowing the bot in I'm not seeing those 502s in the logs.

boomzilla

@dkf said in Unread can't be read:

@boomzilla said in Unread can't be read:

But maybe that's implicitly using the server or the host otherwise identified in the error.

No, then that would be http:/nodebb/… with a single /. With a double //, the first part afterwards is a service identifier.

I mean, yeah, but googling up the error messages points to a "too many open files" sort of error. I think it's just sloppy / unpendantically correct error logging, not nefarious or buggy code, per se.

That bot, BTW, was reading through threads, requesting the posts sequentially (as opposed to getting them page by page or whatever), once per second.

brie

@pie_flavor I've been getting those over the last day or so, and if I hard refresh when that happens, I typically get a 502 error. Server issues, I guess.

Whatever the problem is, it seems intermittent, because one minute it'll do that and then a few seconds later it's fine.