Odd bug

[You_are_a_cunt]

So I was on a 4-day weekend and I wanted to reply to some threads and post a couple status updates (and my $10 smartwatch review) and I noticed I couldn't do, well, anything.

Logging in via Steam, posting new topic, replying, posting status update or replying to a status would cause the page to hang, eventually throwing a 520 error.

 

I've tried logging in on Chrome (private tab) and Edge, both ending up in a 520

Currently at work and posting (obviously) seems to work.

 

I've cleared cache, renewed DNS, rebooted router and firewall, reset ISP connection (the usual) and nothing seems to have worked.

Any ideas as to why this is happening? Seems to be a localized issue (other machines were unavailable at the time to test a working theory that it's something related to my machine specifically)

[You_are_a_cunt]

Update:

Tried replying to a status update from my phone (Lumia 640 using Edge) and it throws the same 520 error after hanging for about 30 seconds.

 

@W-L  @Windspeed36 @GoodBytes

 

hepl.

[LogicalDrm]

26 minutes ago, revsilverspine said:

Update:

Tried replying to a status update from my phone (Lumia 640 using Edge) and it throws the same 520 error after hanging for about 30 seconds.

 

hepl.

Mortis is the one who knows what to do, and maybe ixi too. But no need to tag them, they will read when they got time for it. Meantime, did you use same connection or mobile data? 520 is Cloadflare error which means your IP is flagged.

[You_are_a_cunt]

1 minute ago, LoGiCalDrm said:

Mortis is the one who knows what to do, and maybe ixi too. But no need to tag them, they will read when they got time for it. Meantime, did you use same connection or mobile data? 520 is Cloadflare error which means your IP is flagged.

Phone's using my mobile carrier, PC is using my ISP. Different providers, different IPs, different IP ranges.

 

Haven't gotten any notices from the staff about my IP(s) or account being restricted and I suppose if it were something I'd done I'd have had the IP at work flagged aswell.

 

Odd that I can still access the forum, though.

[GoodBytes]

8 minutes ago, revsilverspine said:

Update:

Tried replying to a status update from my phone (Lumia 640 using Edge) and it throws the same 520 error after hanging for about 30 seconds.

 

@W-L  @Windspeed36 @GoodBytes

 

hepl.

Which build of Windows 10 Mobile do you have?

[You_are_a_cunt]

44 minutes ago, GoodBytes said:

Which build of Windows 10 Mobile do you have?

Latest. 10.0.15063.297

Also latest version of Edge.

 

Same for PC

Windows 10 Pro, up to date

Chrome up to date

Edge up to date

 

 

Apparently using TunnelBear let me post, so it seems something's screwy with my IP(s).

[GoodBytes]

Ah, so it happens to other places. Very good. 'cause I tried it and it worked.

[You_are_a_cunt]

1 minute ago, GoodBytes said:

Ah, so it happens to other places. Very good. 'cause I tried it and it worked.

I assume it has something to do with Cloudflare's protection, doesn't it?

[GoodBytes]

7 minutes ago, revsilverspine said:

I assume it has something to do with Cloudflare's protection, doesn't it?

I don't know. I just wanted to suggest some settings in Edge or/and build, as it works for me, and well, we are the few with such device.

 

[You_are_a_cunt]

Problem persists. Currently unable to log in from home, but forum access is still there.

Tried logging in from multiple machines with the same problem across 3 different networks (2xMobile and 1x ISP)

[You_are_a_cunt]

Issue seems to have resolved itself

[colonel_mortis]

On 08/06/2017 at 8:12 PM, revsilverspine said:

Issue seems to have resolved itself

If it happens again, reply here. I should be around a lot more for the next few months, so I should be able to debug it if it happens again.

[You_are_a_cunt]

51 minutes ago, colonel_mortis said:

If it happens again, reply here. I should be around a lot more for the next few months, so I should be able to debug it if it happens again.

As far as I can tell, it's Cloudflare refusing to forward packages, forcing the forum to throw a 520 error.

It resolved itself, somehow (which reinforces my Cloudflare theory). If it happens again I'll try to find a method to post here (assuming I'm locked out from both at work and while using TunnelBear)