Lila: McAfee blocking lichess1.org

[Waelder64]

the problem I want to report is this:

1. after login only a html text appears.
2. I use the computer since the first login
3. until today everything was okay (yesterday everything was okay)
4. the same address (https://lichess.org/) works on the mobile phone without problems. Login okay.
5. my operating system is Windows 10 and up-to-date
   6 I work with current Firefox browser. With microsoft Edge the error also occurs.
   Who can help me?

Translated with www.DeepL.com/Translator (free version)

[niklasf]

Can you please try to access https://lichess1.org/assets/_egzM5G/compiled/lichess.site.min.js on your computer and report how it looks like?

It's expected to be a minified script:

/*! jQuery v3.2.2-pre | (c) jQuery Foundation | jquery.org/license | hacked for lichess.org on https://github.com/ornicar/jquery/tree/lila */
!function(e,t){"use strict";t(e)}("undefined"!=typeof window?window:this,function(C){"use strict";var e=[],S=C.document,r=Object.getPrototypeOf,s=e.slice,v=e.concat,c=e.push,i=e.indexOf,n={},o=n.toString,g=n.hasOwnProperty,a=g.toString,u=a.call(Object),l={},y=function e(t){return null!=t&&t===t.window};function m(e,t){var n=...

[Waelder64]

Tank you for your quick help, but my english is top Bad.that means i can
Follower

Niklas Fiekas [e-mail] schrieb am Fr., 22. Mai 2020,
20:31:

Can you please try to access
https://lichess1.org/assets/_egzM5G/compiled/lichess.site.min.js on your
computer and report how it looks like?

It's expected to be a minified script:

/*! jQuery v3.2.2-pre | (c) jQuery Foundation | jquery.org/license | hacked for lichess.org on https://github.com/ornicar/jquery/tree/lila */
!function(e,t){"use strict";t(e)}("undefined"!=typeof window?window:this,function(C){"use strict";var e=[],S=C.document,r=Object.getPrototypeOf,s=e.slice,v=e.concat,c=e.push,i=e.indexOf,n={},o=n.toString,g=n.hasOwnProperty,a=g.toString,u=a.call(Object),l={},y=function e(t){return null!=t&&t===t.window};function m(e,t){var n=...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-632842703, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCJVAMH2QJHHBAGROX3RS3AJ7ANCNFSM4NIBF3GA
.

[daniel-b-reid]

Same problem: Windows 10, Firefox, Chrome and IE all showing HTML "old-school" webpage rather than sophisticated web interface. I usually play on an app on my tablet - which is still working so the web-interface is broken. Not sure when it stated.

[niklasf]

We've had some related reports, with users confirming that McAffee firewall is responsible for the breakage.

[Waelder64]

Thanks for the Message. I can confirm that I'm using Mc Affee. Now what
does that mean? Do you have a solution yet? I'll be happy to wait to hear
from you!

Niklas Fiekas [e-mail] schrieb am So., 24. Mai 2020,
09:22:

We've had some related reports, with users confirming that McAffee
firewall is responsible for the breakage.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-633191380, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCLLEB2YUCFLNHEBCJ3RTDDM5ANCNFSM4NIBF3GA
.

[Waelder64]

Hello,
I'm going to answer you again from a different e-mail address.
I found the following message in McApe's log. Please look at the screenshot
I sent with it. Maybe this is helpful in finding a solution. Thanks again
for your help!

---------- Forwarded message ----------
From: Edmund Rosenthal [email protected] [e-mail]
>
To: [email protected] [e-mail]
Cc:
Bcc:
Date: Sun, 24 May 2020 09:49:52 +0200
Subject: Fwd: [ornicar/lila] Login Problem mit Windows 10 (#6682)

---------- Forwarded message ---------
Von: Edmund Rosenthal [email protected] [e-mail]
>
Date: So., 24. Mai 2020, 09:34
Subject: Re: [ornicar/lila] Login Problem mit Windows 10 (#6682)
To: ornicar/lila <
[email protected]

>

Thanks for the Message. I can confirm that I'm using Mc Affee. Now what
does that mean? Do you have a solution yet? I'll be happy to wait to hear
from you!

Niklas Fiekas <[email protected] [e-mail]

schrieb am So., 24. Mai 2020, 09:22:

We've had some related reports, with users confirming that McAffee
firewall is responsible for the breakage.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-633191380 , or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCLLEB2YUCFLNHEBCJ3RTDDM5ANCNFSM4NIBF3GA
.


[niklasf]

Looks like GitHub does not upload e-mail attachments. Can you please upload directly on GitHub?

[Waelder64]

Hello,
I would like to ask if there is already a solution to my problem? Glad to hear from you! Thanks a lot.
Waelder64

[KarimOurrai]

Just to note here, my work computer has McAfee and McAfee firewall, and lichess works just fine

[niklasf]

My current theory is that McAfee is not blocking the domain, but blocking some edge IP of the cloudflare CDN, which would be regional and could be shared with other websites.

Options are uninstalling McAfee and other snakeoil, or finding the IP(s) of lichess1.org and whitelisting them.

[Waelder64]

Also with me Lichess has worked with Mc Affee Firewall for more than 8
weeks, as far as is the comment from Karim Ourrai is to be understood.
Note: in the security history of Mc Affee the IP of Lichess does not
appear. I have the IP ping 37.187.205.99
I'm a little helpless and don't know what to do. I don't really want to do
a deinstallation of Mc Affee. So I ask me what coud be the next steps.
many thanks for the Help!

Am Di., 26. Mai 2020 um 21:13 Uhr schrieb Niklas Fiekas <
[email protected]>:

My current theory is that McAffee is not blocking the domain, but blocking
some edge IP of the cloudflare CDN, which would be regional and could be
shared with other websites.

Options are uninstalling McAffee and other snakeoil, or finding the IP(s)
of lichess1.org and whitelisting them.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-634222510, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCJWZG6LUJZOA5U5LE3RTQIHNANCNFSM4NIBF3GA
.

[niklasf]

With the root cause hopefully figured out (Edge IP theory confirmed), McAfee customer support replied surprisingly quickly:

Thank you for sending this URL to us for review. Upon review, the rating will be adjusted in the next GTI Database release. Please allow up to a few hours for the rating to be updated.

I hope they unbanned the entire range as requested, not just 104.26.6.98. We'll see ...

[niklasf]

104.26.6.98 confirmed "High Risk" -> "Unverified".

Contacted them again for 104.26.7.98, which is still "High Risk".

I also again asked for Cloudflare's entire IP ranges (https://www.cloudflare.com/ips/) to be whitelisted, but they may not be able to do that. So we should keep asking people running into this issue for their region and host lichess1.org or nslookup lichess1.org.

[Waelder64]

Thanks for the news, but what does that mean to me now? I understand I have
to wait, okay, I can do that. But I also understand your mail today
(08:32h) that there may be no remedy at all. That would not be nice, but
life is hard 😊! One more question I have: why did this problem (Mc Affee
accepted this address for several weeks) occur only after a few weeks.

Thanks again, I look forward to hearing more from you.

Am Do., 28. Mai 2020 um 08:32 Uhr schrieb Niklas Fiekas <
[email protected]>:

104.26.6.98 confirmed "High Risk" -> "Unverified".

Contacted them again for 104.26.7.98, which is still "High Risk".

I also again asked Cloudflare's entire IP ranges (
https://www.cloudflare.com/ips/) to be whitelisted, but they may not be
able to do that. So we should keep asking people running into this issue
for their region and host lichess1.org.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-635135644, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCMKJT3IBVBPQBYO26TRTYAPRANCNFSM4NIBF3GA
.

[Waelder64]

It's me again. Maybe I have more bad news. This morning I logged in to my
tablet (WLan, Android system and also protected by Mc Affee) at lichess. It
works, but after logging in I only saw the "text version" for a fraction of
a second, so no graphics. That was, as I said, only very short. But I guess
that this problem will appear soon on the Android system. Why do I suspect
that? Now since I can't use the program in Windows anymore, I play on the
tablet (is very small) which is not comfortable. It seems that there is
also a time problem here, that is, Mc Affee accepts this address and at
some point no longer accepts it. I wanted to share this information with
them. Maybe it will help you.

Am Do., 28. Mai 2020 um 09:09 Uhr schrieb Edmund Rosenthal <
[email protected]>:

Thanks for the news, but what does that mean to me now? I understand I
have to wait, okay, I can do that. But I also understand your mail today
(08:32h) that there may be no remedy at all. That would not be nice, but
life is hard 😊! One more question I have: why did this problem (Mc Affee
accepted this address for several weeks) occur only after a few weeks.

Thanks again, I look forward to hearing more from you.

Am Do., 28. Mai 2020 um 08:32 Uhr schrieb Niklas Fiekas <
[email protected]>:

104.26.6.98 confirmed "High Risk" -> "Unverified".

Contacted them again for 104.26.7.98, which is still "High Risk".

I also again asked Cloudflare's entire IP ranges (
https://www.cloudflare.com/ips/) to be whitelisted, but they may not be
able to do that. So we should keep asking people running into this issue
for their region and host lichess1.org.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-635135644, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCMKJT3IBVBPQBYO26TRTYAPRANCNFSM4NIBF3GA
.

[Waelder64]

I have very good news. I have just tried the LOGIN again. What can I say,
it works! Coincidence, or thanks to your support and help? I do not know,
but I am very happy about it! Of course I hope that it now always works.
Thanks a lot!!!

Am Do., 28. Mai 2020 um 09:50 Uhr schrieb Edmund Rosenthal <
[email protected]>:

It's me again. Maybe I have more bad news. This morning I logged in to my
tablet (WLan, Android system and also protected by Mc Affee) at lichess. It
works, but after logging in I only saw the "text version" for a fraction of
a second, so no graphics. That was, as I said, only very short. But I guess
that this problem will appear soon on the Android system. Why do I suspect
that? Now since I can't use the program in Windows anymore, I play on the
tablet (is very small) which is not comfortable. It seems that there is
also a time problem here, that is, Mc Affee accepts this address and at
some point no longer accepts it. I wanted to share this information with
them. Maybe it will help you.

Am Do., 28. Mai 2020 um 09:09 Uhr schrieb Edmund Rosenthal <
[email protected]>:

Thanks for the news, but what does that mean to me now? I understand I
have to wait, okay, I can do that. But I also understand your mail today
(08:32h) that there may be no remedy at all. That would not be nice, but
life is hard 😊! One more question I have: why did this problem (Mc
Affee accepted this address for several weeks) occur only after a few weeks.

Thanks again, I look forward to hearing more from you.

Am Do., 28. Mai 2020 um 08:32 Uhr schrieb Niklas Fiekas <
[email protected]>:

104.26.6.98 confirmed "High Risk" -> "Unverified".

Contacted them again for 104.26.7.98, which is still "High Risk".

I also again asked Cloudflare's entire IP ranges (
https://www.cloudflare.com/ips/) to be whitelisted, but they may not be
able to do that. So we should keep asking people running into this issue
for their region and host lichess1.org.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ornicar/lila/issues/6682#issuecomment-635135644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APV3VCMKJT3IBVBPQBYO26TRTYAPRANCNFSM4NIBF3GA
.

[niklasf]

104.26.7.98 has also been reviewed/reclassified.

That's all affected IPs we know about so far, so I assume this is fixed for everyone now.