Bug #16143
closedIs Commons site down?
Added by scott voth almost 2 years ago. Updated almost 2 years ago.
0%
Description
I notice that both the Commons and CBOX are down. Went down at 3:06 PM.
Related issues
Updated by Raymond Hoh almost 2 years ago
- Status changed from New to Reporter Feedback
It's up for me. Is it working for you now, Scott? If so, downtime might have been temporary.
Updated by scott voth almost 2 years ago
Still down for me on all browsers. And on my phone.
Updated by Raymond Hoh almost 2 years ago
Can you pass your IP address, Scott? You can find your IP address on https://whatismyipaddress.com/.
Recently, Lihua added some IP blocking for users that hit more than 30 403/404 pages in less than an hour. The IP block would be in effect for a day. I'm guessing your IP might be on there.
Scott, have you tried surfing the Commons with your phone's cellular network instead of wi-Fi as that should provide a different IP address?
Updated by scott voth almost 2 years ago
When I turned off WI Fi on phone I can reach the Commons.
Updated by scott voth almost 2 years ago
- Priority name changed from High to Normal
Demoted this to Normal. Maybe we should watch for this in the future. It could be that the Commons went down briefly, and then I tried a bunch of times on different browsers, and then got the IP Block.
Updated by Raymond Hoh almost 2 years ago
Scott, I can confirm that your IP was on the banned IP list.
We might want to tweak Lihua's algorithm so it is a little bit more lenient.
Updated by Boone Gorges almost 2 years ago
I'm working on an email to Lihua right now. For reference, Scott's issue comes somehow from the flat-bootstrap theme:
$ grep "68\.129\.167\.158" ssl_access.log-20220522 | grep " 40[34] " 68.129.167.158 - - [21/May/2022:14:57:41 -0400] "GET /wp-content/themes/flat-bootstrap/wp-content/themes/flat-bootstrap/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 295 "https://help.commons.gc.cuny.edu/wp-content/themes/flat-bootstrap/css/editor-style.css?wp-mce-49110-20201110" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:100.0) Gecko/20100101 Firefox/100.0" 105212 help.commons.gc.cuny.edu 68.129.167.158 - - [21/May/2022:14:57:41 -0400] "GET /wp-content/themes/flat-bootstrap/wp-content/themes/flat-bootstrap/font-awesome/css/font-awesome.min.css HTTP/1.1" 404 301 "https://help.commons.gc.cuny.edu/wp-content/themes/flat-bootstrap/css/editor-style.css?wp-mce-49110-20201110" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:100.0) Gecko/20100101 Firefox/100.0" 101251 help.commons.gc.cuny.edu 68.129.167.158 - - [21/May/2022:14:57:41 -0400] "GET /wp-content/themes/flat-bootstrap/wp-content/themes/flat-bootstrap/style.css HTTP/1.1" 404 273 "https://help.commons.gc.cuny.edu/wp-content/themes/flat-bootstrap/css/editor-style.css?wp-mce-49110-20201110" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:100.0) Gecko/20100101 Firefox/100.0" 105212 help.commons.gc.cuny.edu
There are a few dozen more entries just like this. When I visit this URL it works https://help.commons.gc.cuny.edu/wp-content/themes/flat-bootstrap/css/editor-style.css?wp-mce-49110-20201110, and the file has been present in the filesystem since May 2021. So I'm not sure why the 404s are happening.
Updated by Boone Gorges almost 2 years ago
Sorry, I just realized that I've misread the log entries. The problematic requests are to URLs like this:
/wp-content/themes/flat-bootstrap/wp-content/themes/flat-bootstrap/bootstrap/css/bootstrap.min.css
which originates from this file https://github.com/cuny-academic-commons/cac/blob/1.19.x/wp-content/themes/flat-bootstrap/css/editor-style.css#L12= The latter file uses incorrect relative paths.
I'll work on an immediate fix for this theme bug (and report to the theme author if possible) but I'll leave the ticket open for the moment while we have a team discussion about the new fail2ban rules.
Updated by Boone Gorges almost 2 years ago
- Target version set to 1.19.10
In https://github.com/cuny-academic-commons/cac/commit/6a654e8d78b8002017829a092b040fd81312f294 I've changed the relative import paths so that they resolve properly. This has been deployed to the site as a hotfix.
A similar issue was reported some time ago to the theme author but there's been no response: https://wordpress.org/support/topic/editor-css-error-since-wordpress-4-8/ There's also been no updates to the theme in about a year, so I assume that none are coming in the near future.
Updated by Raymond Hoh almost 2 years ago
but I'll leave the ticket open for the moment while we have a team discussion about the new fail2ban rules.
For the fail2ban rules, Lihua is using this to ignore certain requests:
ignoreregex =.*(robots.txt|favicon.ico|jpg|png)
Perhaps we can also add in CSS and JS filetypes to this rule. If that were in place, Scott wouldn't have been IP-banned.
Updated by Boone Gorges almost 2 years ago
- Status changed from Reporter Feedback to Staged for Production Release
You're right, Ray. Let's wait to see if Lihua's threshold change (from 40/hr to 120/hr) makes a difference. A file-extension change like you've suggested should be our next request.
Updated by Boone Gorges almost 2 years ago
- Status changed from Staged for Production Release to Resolved
Updated by Raymond Hoh almost 2 years ago
- Related to Support #16278: Commons Down added
Updated by Raymond Hoh almost 2 years ago
- Related to Bug #16294: CAC is down added