tjarco

PLEASE take screenshots / archive.fo pages and submit this to https://voat.co/v/pizzagate/1482030

betadynamique

Wikileaks is the no-man's land between trenches now. Good times.

rush22

I'm getting this on Chrome and also "Bad Gateway". I think it is under attack right now.

It should be back soon hopefully. The site is moving all over the Internet at the moment. Same thing was happening a few weeks ago.

BethesdaDC

Use... yandex.ru

ZalesMcMuffin

Possibly related: I've gone to WL a few times in the past couple months (haven't we all, by now?) and never had trouble. Earlier today there was one time I tried to follow a link there and my browser took probably at least a minute before finally connecting. This was using the same browser on the same OS as all previous visits to WL.

Could be nothing. shrug

xeemee

So is the other site a mirror or a fake?

no - look at the domain - that's all that matters

as far as the blocking, that may have something to do with their ssl cert, or a recent FF upgrade which introduced a change in the certs

did you update FF recently?

badintense

Firefox is constantly doing updates. Doing a whois search says that both wikileaks and couragefound are using the same nameserver of WIKILEAKS.ORG . Maybe that is where the problem is. https://www.networksolutions.com/whois/results.jsp?domain=wikileaks.org https://www.networksolutions.com/whois/results.jsp?domain=couragefound.org

zzzwhat

try palemoon. change your dns. change your vpn server. try from another computer.

if any of those work normally, you are jacked.

badintense

I tried it with IE and it gives me the same warning but lets me ignore the error and connect anyway. And once again adding the www before the addie connects without the error. I see that couragefound is listed on the wikileaks page as a recommended site to visit.

rush22

Yeah it's a bad idea to ignore that error.

Wikileaks actually set it up that way so you would get the error if someone was or could be spoofing the wikileaks site.