[00:02:25] RECOVERY - cp37 Disk Space on cp37 is OK: DISK OK - free space: / 19833MiB (22% inode=98%); [02:30:47] PROBLEM - cp37 Current Load on cp37 is CRITICAL: LOAD CRITICAL - total load average: 10.11, 6.57, 2.91 [02:30:47] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 4 datacenters are down: 38.46.223.205/cpweb, 38.46.223.206/cpweb, 2602:294:0:b13::110/cpweb, 2602:294:0:b23::112/cpweb [02:31:13] PROBLEM - cp36 Nginx Backend for mw171 on cp36 is CRITICAL: connect to address localhost and port 8117: Connection refused [02:31:14] PROBLEM - cp36 Nginx Backend for mw153 on cp36 is CRITICAL: connect to address localhost and port 8121: Connection refused [02:31:14] PROBLEM - cp36 Nginx Backend for mw161 on cp36 is CRITICAL: connect to address localhost and port 8115: Connection refused [02:31:20] PROBLEM - cp36 Nginx Backend for phorge171 on cp36 is CRITICAL: connect to address localhost and port 8202: Connection refused [02:31:21] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 17 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw154 mw163 mw164 mw173 mw174 mw183 mw184 mediawiki [02:31:23] PROBLEM - cp37 HTTPS on cp37 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Connection timed out after 10001 milliseconds [02:31:30] PROBLEM - ns2 GDNSD Datacenters on ns2 is CRITICAL: CRITICAL - 4 datacenters are down: 38.46.223.205/cpweb, 38.46.223.206/cpweb, 2602:294:0:b13::110/cpweb, 2602:294:0:b23::112/cpweb [02:31:34] PROBLEM - cp36 Nginx Backend for test151 on cp36 is CRITICAL: connect to address localhost and port 8181: Connection refused [02:31:38] PROBLEM - cp36 HTTPS on cp36 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to cp36.wikitide.net port 443 after 0 ms: Couldn't connect to server [02:31:41] PROBLEM - cp36 Nginx Backend for mw173 on cp36 is CRITICAL: connect to address localhost and port 8125: Connection refused [02:31:44] PROBLEM - cp36 Nginx Backend for puppet181 on cp36 is CRITICAL: connect to address localhost and port 8204: Connection refused [02:31:52] PROBLEM - cp36 Nginx Backend for matomo151 on cp36 is CRITICAL: connect to address localhost and port 8203: Connection refused [02:31:54] PROBLEM - cp36 Nginx Backend for mw164 on cp36 is CRITICAL: connect to address localhost and port 8124: Connection refused [02:31:54] PROBLEM - cp36 Nginx Backend for mw154 on cp36 is CRITICAL: connect to address localhost and port 8122: Connection refused [02:31:55] PROBLEM - cp36 Nginx Backend for mwtask171 on cp36 is CRITICAL: connect to address localhost and port 8161: Connection refused [02:31:59] PROBLEM - cp36 Nginx Backend for mw174 on cp36 is CRITICAL: connect to address localhost and port 8126: Connection refused [02:32:05] PROBLEM - cp36 Nginx Backend for mw182 on cp36 is CRITICAL: connect to address localhost and port 8120: Connection refused [02:32:05] PROBLEM - cp36 Nginx Backend for mw151 on cp36 is CRITICAL: connect to address localhost and port 8113: Connection refused [02:32:08] PROBLEM - cp36 Nginx Backend for swiftproxy171 on cp36 is CRITICAL: connect to address localhost and port 8207: Connection refused [02:32:19] PROBLEM - cp36 Nginx Backend for mw172 on cp36 is CRITICAL: connect to address localhost and port 8118: Connection refused [02:32:20] PROBLEM - cp36 Nginx Backend for mwtask151 on cp36 is CRITICAL: connect to address localhost and port 8162: Connection refused [02:32:23] PROBLEM - cp36 Nginx Backend for mwtask181 on cp36 is CRITICAL: connect to address localhost and port 8160: Connection refused [02:32:26] PROBLEM - cp36 Nginx Backend for mon181 on cp36 is CRITICAL: connect to address localhost and port 8201: Connection refused [02:32:26] PROBLEM - cp36 Nginx Backend for mw183 on cp36 is CRITICAL: connect to address localhost and port 8127: Connection refused [02:32:30] PROBLEM - cp36 Nginx Backend for reports171 on cp36 is CRITICAL: connect to address localhost and port 8205: Connection refused [02:32:31] PROBLEM - cp37 HTTP 4xx/5xx ERROR Rate on cp37 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [02:32:34] PROBLEM - cp36 Nginx Backend for mw163 on cp36 is CRITICAL: connect to address localhost and port 8123: Connection refused [02:32:35] PROBLEM - puzzles.wiki - Cloudflare on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:32:35] PROBLEM - enc.for.uz - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:32:35] PROBLEM - otherkin.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:32:37] PROBLEM - cp36 Nginx Backend for mw181 on cp36 is CRITICAL: connect to address localhost and port 8119: Connection refused [02:32:37] PROBLEM - cp36 Nginx Backend for mw162 on cp36 is CRITICAL: connect to address localhost and port 8116: Connection refused [02:32:38] PROBLEM - cp36 Nginx Backend for mwtask161 on cp36 is CRITICAL: connect to address localhost and port 8163: Connection refused [02:32:51] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 17 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw154 mw163 mw164 mw173 mw174 mw183 mw184 mediawiki [02:32:54] PROBLEM - cp36 Nginx Backend for mw152 on cp36 is CRITICAL: connect to address localhost and port 8114: Connection refused [02:32:55] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is WARNING: WARNING - NGINX Error Rate is 54% [02:32:58] PROBLEM - cp36 Nginx Backend for swiftproxy161 on cp36 is CRITICAL: connect to address localhost and port 8206: Connection refused [02:33:06] PROBLEM - cp36 Nginx Backend for mw184 on cp36 is CRITICAL: connect to address localhost and port 8128: Connection refused [02:33:30] PROBLEM - oxboxtra.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:33:55] PROBLEM - n64brew.dev - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:34:10] PROBLEM - podpedia.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:34:31] RECOVERY - cp37 HTTP 4xx/5xx ERROR Rate on cp37 is OK: OK - NGINX Error Rate is 28% [02:34:44] PROBLEM - cp37 Current Load on cp37 is WARNING: LOAD WARNING - total load average: 7.81, 7.50, 4.21 [02:34:50] PROBLEM - smashbroswiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:35:06] PROBLEM - weavefarers.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:35:08] PROBLEM - segawiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:35:13] PROBLEM - lovebullet.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:35:14] PROBLEM - darkwaterswiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:35:19] PROBLEM - wonderfuleveryday.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:36:08] that no look good [02:36:10] PROBLEM - lotr.su - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:36:14] PROBLEM - caverncrusher.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:36:24] PROBLEM - poupedia.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:36:44] PROBLEM - cp37 Current Load on cp37 is CRITICAL: LOAD CRITICAL - total load average: 11.56, 8.55, 4.97 [02:36:56] PROBLEM - mh142.com - LetsEncrypt on sslhost is CRITICAL: connect to address mh142.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:37:22] PROBLEM - lostidols.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address lostidols.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:37:26] PROBLEM - holocron.net - LetsEncrypt on sslhost is CRITICAL: connect to address holocron.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:37:26] PROBLEM - royal-wiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address royal-wiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:37:26] PROBLEM - binrayarchives.com - LetsEncrypt on sslhost is CRITICAL: connect to address binrayarchives.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:37:34] PROBLEM - pyramidgames.wiki - Cloudflare on sslhost is CRITICAL: connect to address pyramidgames.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:09] PROBLEM - richterian.com - LetsEncrypt on sslhost is CRITICAL: connect to address richterian.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:11] PROBLEM - isocasg.org - LetsEncrypt on sslhost is CRITICAL: connect to address isocasg.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:19] PROBLEM - apeirology.com - LetsEncrypt on sslhost is CRITICAL: connect to address apeirology.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:22] PROBLEM - dariawiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address dariawiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:25] PROBLEM - worldsanskrit.net - LetsEncrypt on sslhost is CRITICAL: connect to address worldsanskrit.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:25] PROBLEM - cnidaria.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address cnidaria.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:34] PROBLEM - cp37 HTTP 4xx/5xx ERROR Rate on cp37 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [02:38:44] RECOVERY - cp37 Current Load on cp37 is OK: LOAD OK - total load average: 1.63, 5.78, 4.39 [02:38:45] PROBLEM - allthetropes.org - LetsEncrypt on sslhost is CRITICAL: connect to address allthetropes.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:46] PROBLEM - mwcosmos.com - LetsEncrypt on sslhost is CRITICAL: connect to address mwcosmos.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:38:51] PROBLEM - cp37 Nginx Backend for mw152 on cp37 is CRITICAL: connect to address localhost and port 8114: Connection refused [02:38:55] PROBLEM - cp37 Nginx Backend for mw183 on cp37 is CRITICAL: connect to address localhost and port 8127: Connection refused [02:38:58] PROBLEM - cp37 Nginx Backend for reports171 on cp37 is CRITICAL: connect to address localhost and port 8205: Connection refused [02:38:59] PROBLEM - cp37 Nginx Backend for mw164 on cp37 is CRITICAL: connect to address localhost and port 8124: Connection refused [02:39:07] PROBLEM - cp37 Nginx Backend for mon181 on cp37 is CRITICAL: connect to address localhost and port 8201: Connection refused [02:39:08] PROBLEM - cp37 Nginx Backend for mw154 on cp37 is CRITICAL: connect to address localhost and port 8122: Connection refused [02:39:10] PROBLEM - cp37 Nginx Backend for mw174 on cp37 is CRITICAL: connect to address localhost and port 8126: Connection refused [02:39:11] PROBLEM - cp37 Nginx Backend for puppet181 on cp37 is CRITICAL: connect to address localhost and port 8204: Connection refused [02:39:11] PROBLEM - cp37 Nginx Backend for mw153 on cp37 is CRITICAL: connect to address localhost and port 8121: Connection refused [02:39:11] PROBLEM - cp37 Nginx Backend for swiftproxy161 on cp37 is CRITICAL: connect to address localhost and port 8206: Connection refused [02:39:16] PROBLEM - lotrmc.ru - LetsEncrypt on sslhost is CRITICAL: connect to address lotrmc.ru and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:17] PROBLEM - beyondtheveilrp.com - LetsEncrypt on sslhost is CRITICAL: connect to address beyondtheveilrp.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:21] PROBLEM - cp37 Nginx Backend for phorge171 on cp37 is CRITICAL: connect to address localhost and port 8202: Connection refused [02:39:23] PROBLEM - cp37 Nginx Backend for mw182 on cp37 is CRITICAL: connect to address localhost and port 8120: Connection refused [02:39:25] PROBLEM - vilexia.com - LetsEncrypt on sslhost is CRITICAL: connect to address vilexia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:31] PROBLEM - cp37 Nginx Backend for mw181 on cp37 is CRITICAL: connect to address localhost and port 8119: Connection refused PROBLEM - cp37 Nginx Backend for mw171 on cp37 is CRITICAL: connect to address localhost and port 8117: Connection refused [02:39:35] PROBLEM - spiceandwolf.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address spiceandwolf.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:36] PROBLEM - lads.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address lads.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:40] PROBLEM - runzeppelin.ru - LetsEncrypt on sslhost is CRITICAL: connect to address runzeppelin.ru and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:41] PROBLEM - cp37 Nginx Backend for mw151 on cp37 is CRITICAL: connect to address localhost and port 8113: Connection refused [02:39:43] PROBLEM - cp37 Nginx Backend for mw172 on cp37 is CRITICAL: connect to address localhost and port 8118: Connection refused [02:39:43] PROBLEM - cp37 Nginx Backend for mw184 on cp37 is CRITICAL: connect to address localhost and port 8128: Connection refused [02:39:43] PROBLEM - cp37 Nginx Backend for mwtask151 on cp37 is CRITICAL: connect to address localhost and port 8162: Connection refused [02:39:47] PROBLEM - cp37 Nginx Backend for matomo151 on cp37 is CRITICAL: connect to address localhost and port 8203: Connection refused [02:39:48] PROBLEM - cp37 Nginx Backend for mw161 on cp37 is CRITICAL: connect to address localhost and port 8115: Connection refused [02:39:48] PROBLEM - osdev.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address osdev.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:50] PROBLEM - cp37 Nginx Backend for swiftproxy171 on cp37 is CRITICAL: connect to address localhost and port 8207: Connection refused [02:39:52] PROBLEM - sdiy.info - LetsEncrypt on sslhost is CRITICAL: connect to address sdiy.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:53] PROBLEM - agesofconflict.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address agesofconflict.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:53] PROBLEM - rosettacode.org - LetsEncrypt on sslhost is CRITICAL: connect to address rosettacode.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:54] PROBLEM - edapedia.net - LetsEncrypt on sslhost is CRITICAL: connect to address edapedia.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:54] PROBLEM - bristolstudenthousingcoop.org - LetsEncrypt on sslhost is CRITICAL: connect to address bristolstudenthousingcoop.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:39:56] PROBLEM - cp37 Nginx Backend for mwtask181 on cp37 is CRITICAL: connect to address localhost and port 8160: Connection refused [02:39:58] PROBLEM - cp37 Nginx Backend for mwtask161 on cp37 is CRITICAL: connect to address localhost and port 8163: Connection refused [02:40:00] PROBLEM - cp37 Nginx Backend for mwtask171 on cp37 is CRITICAL: connect to address localhost and port 8161: Connection refused [02:40:13] PROBLEM - cp37 Nginx Backend for mw162 on cp37 is CRITICAL: connect to address localhost and port 8116: Connection refused [02:40:23] PROBLEM - creativecommons.id - LetsEncrypt on sslhost is CRITICAL: connect to address creativecommons.id and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:40:24] PROBLEM - beidipedia.com - LetsEncrypt on sslhost is CRITICAL: connect to address beidipedia.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:40:37] PROBLEM - cp37 Nginx Backend for test151 on cp37 is CRITICAL: connect to address localhost and port 8181: Connection refused [02:40:41] PROBLEM - cp37 Nginx Backend for mw163 on cp37 is CRITICAL: connect to address localhost and port 8123: Connection refused [02:40:45] PROBLEM - cp37 Nginx Backend for mw173 on cp37 is CRITICAL: connect to address localhost and port 8125: Connection refused [02:40:57] PROBLEM - dkwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address dkwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:41:09] PROBLEM - maxcapacity.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address maxcapacity.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:41:21] PROBLEM - antiguabarbudacalypso.com - LetsEncrypt on sslhost is CRITICAL: connect to address antiguabarbudacalypso.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:41:52] PROBLEM - mariopedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address mariopedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:42:28] PROBLEM - sptwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address sptwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:42:36] PROBLEM - exordium.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address exordium.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:42:48] PROBLEM - bobobay.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address bobobay.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:42:48] PROBLEM - wizardia.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address wizardia.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:42:59] PROBLEM - permanentfuturelab.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address permanentfuturelab.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:42:59] PROBLEM - grayravens.com - LetsEncrypt on sslhost is CRITICAL: connect to address grayravens.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:43:23] PROBLEM - terraforming.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address terraforming.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:43:23] PROBLEM - farthestfrontier.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address farthestfrontier.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:43:28] PROBLEM - keitaiwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address keitaiwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:43:45] PROBLEM - yokaiwatchwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address yokaiwatchwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:43:50] PROBLEM - gielinorgames.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address gielinorgames.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:17] PROBLEM - thestarsareright.org - LetsEncrypt on sslhost is CRITICAL: connect to address thestarsareright.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:17] PROBLEM - aryavartpedia.online - LetsEncrypt on sslhost is CRITICAL: connect to address aryavartpedia.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:17] PROBLEM - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is CRITICAL: connect to address thelonsdalebattalion.co.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:18] PROBLEM - electowiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address electowiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:24] PROBLEM - inourownwords.online - LetsEncrypt on sslhost is CRITICAL: connect to address inourownwords.online and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:24] PROBLEM - ncuwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address ncuwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:37] PROBLEM - journeytheword.wiki - Cloudflare on sslhost is CRITICAL: connect to address journeytheword.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:49] PROBLEM - christipedia.nl - LetsEncrypt on sslhost is CRITICAL: connect to address christipedia.nl and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:44:50] PROBLEM - crashspyrowiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address crashspyrowiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:45:33] PROBLEM - ourlifewiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address ourlifewiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:46:13] PROBLEM - kunwok.org - LetsEncrypt on sslhost is CRITICAL: connect to address kunwok.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:46:30] PROBLEM - androidwiki.info - LetsEncrypt on sslhost is CRITICAL: connect to address androidwiki.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:46:44] PROBLEM - vylet.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vylet.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:46:46] PROBLEM - rodzinka.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address rodzinka.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:46:48] PROBLEM - comprehensibleinputwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address comprehensibleinputwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:46:51] PROBLEM - blackmagic.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address blackmagic.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:47:00] PROBLEM - ekumen.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address ekumen.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:47:11] PROBLEM - thegreatwar.uk - LetsEncrypt on sslhost is CRITICAL: connect to address thegreatwar.uk and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:47:13] PROBLEM - ff8.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address ff8.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:47:19] PROBLEM - landofliberos.com - LetsEncrypt on sslhost is CRITICAL: connect to address landofliberos.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:47:33] PROBLEM - roll-of-arms.com - LetsEncrypt on sslhost is CRITICAL: connect to address roll-of-arms.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:01] PROBLEM - squareenixwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address squareenixwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:04] PROBLEM - removededm.com - LetsEncrypt on sslhost is CRITICAL: connect to address removededm.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:17] PROBLEM - jackbox.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address jackbox.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:21] PROBLEM - acuralegendwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address acuralegendwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:43] PROBLEM - wikitide.net - LetsEncrypt on sslhost is CRITICAL: connect to address wikitide.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:44] PROBLEM - fischipedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address fischipedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:44] PROBLEM - dccomicswiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address dccomicswiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:51] PROBLEM - stablestate.org - LetsEncrypt on sslhost is CRITICAL: connect to address stablestate.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:48:51] PROBLEM - hoseki.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address hoseki.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:49:01] PROBLEM - gimkit.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address gimkit.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:49:13] RECOVERY - cp36 Nginx Backend for mw171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8117 [02:49:14] RECOVERY - cp36 Nginx Backend for mw153 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8121 [02:49:14] RECOVERY - cp36 Nginx Backend for mw161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8115 [02:49:20] RECOVERY - cp36 Nginx Backend for phorge171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8202 [02:49:34] RECOVERY - cp36 Nginx Backend for test151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8181 [02:49:41] RECOVERY - cp36 Nginx Backend for mw173 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8125 [02:49:44] RECOVERY - cp36 Nginx Backend for puppet181 on cp36 is OK: TCP OK - 0.001 second response time on localhost port 8204 [02:49:52] RECOVERY - cp36 Nginx Backend for matomo151 on cp36 is OK: TCP OK - 0.001 second response time on localhost port 8203 [02:49:54] RECOVERY - cp36 Nginx Backend for mw164 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8124 [02:49:55] RECOVERY - cp36 Nginx Backend for mw154 on cp36 is OK: TCP OK - 0.003 second response time on localhost port 8122 [02:49:55] RECOVERY - cp36 Nginx Backend for mwtask171 on cp36 is OK: TCP OK - 0.001 second response time on localhost port 8161 [02:49:59] RECOVERY - cp36 Nginx Backend for mw174 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8126 [02:50:05] RECOVERY - cp36 Nginx Backend for mw151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8113 [02:50:06] RECOVERY - cp36 Nginx Backend for mw182 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8120 [02:50:08] RECOVERY - cp36 Nginx Backend for swiftproxy171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8207 [02:50:19] RECOVERY - cp36 Nginx Backend for mw172 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8118 [02:50:20] RECOVERY - cp36 Nginx Backend for mwtask151 on cp36 is OK: TCP OK - 0.008 second response time on localhost port 8162 [02:50:23] RECOVERY - cp36 Nginx Backend for mwtask181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8160 [02:50:26] RECOVERY - cp36 Nginx Backend for mon181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8201 [02:50:26] RECOVERY - cp36 Nginx Backend for mw183 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8127 [02:50:30] RECOVERY - cp36 Nginx Backend for reports171 on cp36 is OK: TCP OK - 0.001 second response time on localhost port 8205 [02:50:34] RECOVERY - cp36 Nginx Backend for mw163 on cp36 is OK: TCP OK - 0.001 second response time on localhost port 8123 [02:50:37] RECOVERY - cp36 Nginx Backend for mw181 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8119 [02:50:38] RECOVERY - cp36 Nginx Backend for mw162 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8116 [02:50:38] RECOVERY - cp36 Nginx Backend for mwtask161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8163 [02:50:56] RECOVERY - cp36 Nginx Backend for mw152 on cp36 is OK: TCP OK - 0.017 second response time on localhost port 8114 [02:51:03] RECOVERY - cp36 Nginx Backend for swiftproxy161 on cp36 is OK: TCP OK - 0.023 second response time on localhost port 8206 [02:51:05] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is CRITICAL: CRITICAL - NGINX Error Rate is 100% [02:51:06] RECOVERY - cp36 Nginx Backend for mw184 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8128 [02:51:21] PROBLEM - cp36 Varnish Backends on cp36 is WARNING: No backends detected. If this is an error, see readme.txt [02:53:06] PROBLEM - ssbuniverses.com - LetsEncrypt on sslhost is CRITICAL: connect to address ssbuniverses.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:53:08] PROBLEM - geeu.org - LetsEncrypt on sslhost is CRITICAL: connect to address geeu.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:53:19] PROBLEM - *.wikitide.org - LetsEncrypt on sslhost is CRITICAL: connect to address wikitide.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:53:21] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 17 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw154 mw163 mw164 mw173 mw174 mw183 mw184 mediawiki [02:54:13] PROBLEM - urbanshade.org - LetsEncrypt on sslhost is CRITICAL: connect to address urbanshade.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:19] PROBLEM - cp36 Nginx Backend for mw172 on cp36 is CRITICAL: connect to address localhost and port 8118: Connection refused [02:54:20] PROBLEM - cp36 Nginx Backend for mwtask151 on cp36 is CRITICAL: connect to address localhost and port 8162: Connection refused [02:54:23] PROBLEM - cp36 Nginx Backend for mwtask181 on cp36 is CRITICAL: connect to address localhost and port 8160: Connection refused [02:54:26] PROBLEM - rippaversewiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address rippaversewiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:26] PROBLEM - cp36 Nginx Backend for mon181 on cp36 is CRITICAL: connect to address localhost and port 8201: Connection refused [02:54:26] PROBLEM - cp36 Nginx Backend for mw183 on cp36 is CRITICAL: connect to address localhost and port 8127: Connection refused [02:54:27] PROBLEM - decimatedrive.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address decimatedrive.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:30] PROBLEM - cp36 Nginx Backend for reports171 on cp36 is CRITICAL: connect to address localhost and port 8205: Connection refused [02:54:31] PROBLEM - pokemonwiki.info - LetsEncrypt on sslhost is CRITICAL: connect to address pokemonwiki.info and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:31] PROBLEM - emmytherobot.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address emmytherobot.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:34] PROBLEM - cp36 Nginx Backend for mw163 on cp36 is CRITICAL: connect to address localhost and port 8123: Connection refused [02:54:37] PROBLEM - cp36 Nginx Backend for mw181 on cp36 is CRITICAL: connect to address localhost and port 8119: Connection refused [02:54:37] PROBLEM - cp36 Nginx Backend for mw162 on cp36 is CRITICAL: connect to address localhost and port 8116: Connection refused [02:54:38] PROBLEM - cp36 Nginx Backend for mwtask161 on cp36 is CRITICAL: connect to address localhost and port 8163: Connection refused [02:54:38] PROBLEM - wikimas.kr - LetsEncrypt on sslhost is CRITICAL: connect to address wikimas.kr and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:54] PROBLEM - cp36 Nginx Backend for mw152 on cp36 is CRITICAL: connect to address localhost and port 8114: Connection refused [02:54:55] PROBLEM - polcompball.net - LetsEncrypt on sslhost is CRITICAL: connect to address polcompball.net and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:54:58] PROBLEM - cp36 Nginx Backend for swiftproxy161 on cp36 is CRITICAL: connect to address localhost and port 8206: Connection refused [02:55:00] PROBLEM - wikappedia.cc - LetsEncrypt on sslhost is CRITICAL: connect to address wikappedia.cc and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:55:06] PROBLEM - cp36 Nginx Backend for mw184 on cp36 is CRITICAL: connect to address localhost and port 8128: Connection refused [02:55:06] PROBLEM - solaswiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address solaswiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:55:13] PROBLEM - cp36 Nginx Backend for mw171 on cp36 is CRITICAL: connect to address localhost and port 8117: Connection refused [02:55:14] PROBLEM - cp36 Nginx Backend for mw161 on cp36 is CRITICAL: connect to address localhost and port 8115: Connection refused [02:55:14] PROBLEM - cp36 Nginx Backend for mw153 on cp36 is CRITICAL: connect to address localhost and port 8121: Connection refused [02:55:19] PROBLEM - wikitide.org - LetsEncrypt on sslhost is CRITICAL: connect to address wikitide.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:55:20] PROBLEM - cp36 Nginx Backend for phorge171 on cp36 is CRITICAL: connect to address localhost and port 8202: Connection refused [02:55:20] PROBLEM - bonesword.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address bonesword.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:55:34] PROBLEM - cp36 Nginx Backend for test151 on cp36 is CRITICAL: connect to address localhost and port 8181: Connection refused [02:55:38] PROBLEM - hastursnotebook.org - LetsEncrypt on sslhost is CRITICAL: connect to address hastursnotebook.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:55:40] PROBLEM - pso2ngs.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address pso2ngs.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:55:41] PROBLEM - cp36 Nginx Backend for mw173 on cp36 is CRITICAL: connect to address localhost and port 8125: Connection refused [02:55:44] PROBLEM - cp36 Nginx Backend for puppet181 on cp36 is CRITICAL: connect to address localhost and port 8204: Connection refused [02:55:52] PROBLEM - cp36 Nginx Backend for matomo151 on cp36 is CRITICAL: connect to address localhost and port 8203: Connection refused [02:55:54] PROBLEM - cp36 Nginx Backend for mw164 on cp36 is CRITICAL: connect to address localhost and port 8124: Connection refused [02:55:54] PROBLEM - cp36 Nginx Backend for mw154 on cp36 is CRITICAL: connect to address localhost and port 8122: Connection refused [02:55:55] PROBLEM - cp36 Nginx Backend for mwtask171 on cp36 is CRITICAL: connect to address localhost and port 8161: Connection refused [02:55:59] PROBLEM - cp36 Nginx Backend for mw174 on cp36 is CRITICAL: connect to address localhost and port 8126: Connection refused [02:56:03] PROBLEM - monarchists.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address monarchists.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:03] PROBLEM - freedomplanetwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address freedomplanetwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:05] PROBLEM - cp36 Nginx Backend for mw151 on cp36 is CRITICAL: connect to address localhost and port 8113: Connection refused [02:56:05] PROBLEM - cp36 Nginx Backend for mw182 on cp36 is CRITICAL: connect to address localhost and port 8120: Connection refused [02:56:08] PROBLEM - cp36 Nginx Backend for swiftproxy171 on cp36 is CRITICAL: connect to address localhost and port 8207: Connection refused [02:56:09] PROBLEM - issue-tracker.wikitide.org - LetsEncrypt on sslhost is CRITICAL: connect to address issue-tracker.wikitide.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:10] PROBLEM - pizzatower.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address pizzatower.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:19] PROBLEM - wikigenius.org - LetsEncrypt on sslhost is CRITICAL: connect to address wikigenius.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:20] PROBLEM - icclopedia.org - LetsEncrypt on sslhost is CRITICAL: connect to address icclopedia.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:20] PROBLEM - speleo.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address speleo.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:56:27] PROBLEM - rainverse.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address rainverse.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:10] PROBLEM - wikimoma.art - LetsEncrypt on sslhost is CRITICAL: connect to address wikimoma.art and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:20] PROBLEM - junxions.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address junxions.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:38] PROBLEM - trollpasta.com - LetsEncrypt on sslhost is CRITICAL: connect to address trollpasta.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:38] PROBLEM - encyclopediaofastrobiology.org - LetsEncrypt on sslhost is CRITICAL: connect to address encyclopediaofastrobiology.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:42] PROBLEM - civwiki.org - LetsEncrypt on sslhost is CRITICAL: connect to address civwiki.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:48] PROBLEM - worldless.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address worldless.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:57:53] PROBLEM - fashiondreamer.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address fashiondreamer.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:58:20] PROBLEM - kingdomdeath.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address kingdomdeath.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:58:24] PROBLEM - cpmusicwiki.com - LetsEncrypt on sslhost is CRITICAL: connect to address cpmusicwiki.com and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:58:31] PROBLEM - vesc.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address vesc.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:08] PROBLEM - psycho.engineering - LetsEncrypt on sslhost is CRITICAL: connect to address psycho.engineering and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:08] PROBLEM - iol.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address iol.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:08] PROBLEM - warhammer40kturkiye.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address warhammer40kturkiye.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:08] PROBLEM - encyclopediarobotica.org - LetsEncrypt on sslhost is CRITICAL: connect to address encyclopediarobotica.org and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:08] PROBLEM - kingdomway.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address kingdomway.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:09] PROBLEM - burnout.wiki - LetsEncrypt on sslhost is CRITICAL: connect to address burnout.wiki and port 443: Connection refusedHTTP CRITICAL - Unable to open TCP socket [02:59:11] RECOVERY - cp37 Nginx Backend for puppet181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8204 [02:59:11] RECOVERY - cp37 Nginx Backend for mw153 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8121 [02:59:21] RECOVERY - cp37 Nginx Backend for phorge171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8202 [02:59:23] RECOVERY - cp37 Nginx Backend for mw182 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8120 [02:59:31] RECOVERY - cp37 Nginx Backend for mw181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8119 [02:59:31] RECOVERY - cp37 Nginx Backend for mw171 on cp37 is OK: TCP OK - 0.002 second response time on localhost port 8117 [02:59:38] PROBLEM - partopedia.ru - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:59:41] RECOVERY - cp37 Nginx Backend for mw151 on cp37 is OK: TCP OK - 0.003 second response time on localhost port 8113 [02:59:43] RECOVERY - cp37 Nginx Backend for mw172 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8118 [02:59:43] RECOVERY - cp37 Nginx Backend for mw184 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8128 [02:59:44] RECOVERY - cp37 Nginx Backend for mwtask151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8162 [02:59:47] RECOVERY - cp37 Nginx Backend for mw161 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8115 [02:59:48] RECOVERY - cp37 Nginx Backend for matomo151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8203 [02:59:50] RECOVERY - cp37 Nginx Backend for swiftproxy171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8207 [02:59:56] RECOVERY - cp37 Nginx Backend for mwtask181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8160 [03:00:03] RECOVERY - cp37 Nginx Backend for mwtask161 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8163 [03:00:03] RECOVERY - cp37 Nginx Backend for mwtask171 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8161 [03:00:03] PROBLEM - lostmediawiki.ru - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:00:13] RECOVERY - cp37 Nginx Backend for mw162 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8116 [03:00:26] RECOVERY - cp37 Nginx Backend for swiftproxy161 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8206 [03:00:31] RECOVERY - cp37 Nginx Backend for mw154 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8122 [03:00:35] RECOVERY - cp37 Nginx Backend for mw174 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8126 [03:00:37] RECOVERY - cp37 Nginx Backend for test151 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8181 [03:00:41] RECOVERY - cp37 Nginx Backend for mw163 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8123 [03:00:45] RECOVERY - cp37 Nginx Backend for mw173 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8125 [03:00:52] RECOVERY - cp37 Nginx Backend for mw152 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8114 [03:00:55] RECOVERY - cp37 Nginx Backend for mw183 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8127 [03:00:58] RECOVERY - cp37 Nginx Backend for reports171 on cp37 is OK: TCP OK - 0.002 second response time on localhost port 8205 [03:00:59] RECOVERY - cp37 Nginx Backend for mw164 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8124 [03:01:07] RECOVERY - cp37 Nginx Backend for mon181 on cp37 is OK: TCP OK - 0.000 second response time on localhost port 8201 [03:01:16] PROBLEM - sytbay.site - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:01:16] PROBLEM - fanonpedia.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:01:16] PROBLEM - worldtriggerwiki.com - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:01:16] PROBLEM - opendatascot.org - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:01:17] PROBLEM - grayzonewarfare.wiki - LetsEncrypt on sslhost is CRITICAL: CRITICAL - Socket timeout after 10 seconds [03:01:26] RECOVERY - otherkin.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'otherkin.wiki' will expire on Wed 22 Jan 2025 02:41:57 PM GMT +0000. [03:01:28] RECOVERY - puzzles.wiki - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [03:01:28] RECOVERY - enc.for.uz - LetsEncrypt on sslhost is OK: OK - Certificate 'enc.for.uz' will expire on Fri 07 Mar 2025 06:34:10 AM GMT +0000. [03:02:01] [1/2] thats alot of problems... [03:02:01] [2/2] https://cdn.discordapp.com/attachments/808001911868489748/1318412860988063744/IMG_7602.png?ex=67623b28&is=6760e9a8&hm=3781f9f0190e9c5862c3cde372af48c48891a94a1be8c33165fd3d6c8520070e& [03:02:31] RECOVERY - cp37 HTTP 4xx/5xx ERROR Rate on cp37 is OK: OK - NGINX Error Rate is 10% [03:02:51] RECOVERY - cp37 Varnish Backends on cp37 is OK: All 29 backends are healthy [03:03:02] RECOVERY - oxboxtra.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'oxboxtra.wiki' will expire on Wed 29 Jan 2025 06:47:21 AM GMT +0000. [03:03:03] RECOVERY - n64brew.dev - LetsEncrypt on sslhost is OK: OK - Certificate 'n64brew.dev' will expire on Fri 07 Mar 2025 06:15:58 PM GMT +0000. [03:03:03] RECOVERY - cp37 HTTPS on cp37 is OK: HTTP OK: HTTP/2 404 - Status line output matched "HTTP/2 404" - 4141 bytes in 0.056 second response time [03:03:44] RECOVERY - podpedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'podpedia.org' will expire on Fri 07 Mar 2025 09:06:45 AM GMT +0000. [03:03:57] RECOVERY - smashbroswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'smashbroswiki.com' will expire on Sat 08 Mar 2025 01:33:58 PM GMT +0000. [03:04:41] RECOVERY - weavefarers.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'weavefarers.wiki' will expire on Wed 19 Feb 2025 12:42:15 AM GMT +0000. [03:04:47] RECOVERY - lovebullet.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'lovebullet.wiki' will expire on Sat 01 Mar 2025 11:30:48 PM GMT +0000. [03:05:02] RECOVERY - segawiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'segawiki.com' will expire on Sat 15 Mar 2025 06:21:40 PM GMT +0000. [03:05:02] RECOVERY - darkwaterswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'darkwaterswiki.com' will expire on Wed 08 Jan 2025 04:02:59 PM GMT +0000. [03:05:16] RECOVERY - wonderfuleveryday.org - LetsEncrypt on sslhost is OK: OK - Certificate 'wonderfuleveryday.org' will expire on Sun 16 Feb 2025 01:46:05 AM GMT +0000. [03:05:36] RECOVERY - mh142.com - LetsEncrypt on sslhost is OK: OK - Certificate 'mh142.com' will expire on Fri 07 Mar 2025 07:39:12 AM GMT +0000. [03:05:50] RECOVERY - poupedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'poupedia.com' will expire on Wed 12 Feb 2025 02:03:07 PM GMT +0000. [03:05:51] RECOVERY - caverncrusher.com - LetsEncrypt on sslhost is OK: OK - Certificate 'caverncrusher.com' will expire on Sat 15 Mar 2025 02:06:28 PM GMT +0000. [03:05:54] RECOVERY - lotr.su - LetsEncrypt on sslhost is OK: OK - Certificate 'lotr.su' will expire on Wed 12 Mar 2025 04:28:42 PM GMT +0000. [03:06:27] RECOVERY - lostidols.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'lostidols.wiki' will expire on Thu 02 Jan 2025 04:21:54 PM GMT +0000. [03:06:36] RECOVERY - binrayarchives.com - LetsEncrypt on sslhost is OK: OK - Certificate 'binrayarchives.com' will expire on Sun 09 Feb 2025 09:53:22 PM GMT +0000. [03:06:36] RECOVERY - royal-wiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'royal-wiki.org' will expire on Sun 09 Mar 2025 12:08:28 AM GMT +0000. [03:06:37] RECOVERY - holocron.net - LetsEncrypt on sslhost is OK: OK - Certificate 'holocron.net' will expire on Mon 24 Feb 2025 03:12:55 AM GMT +0000. [03:06:48] RECOVERY - isocasg.org - LetsEncrypt on sslhost is OK: OK - Certificate 'isocasg.org' will expire on Wed 29 Jan 2025 03:51:53 PM GMT +0000. [03:06:51] RECOVERY - pyramidgames.wiki - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [03:06:59] RECOVERY - apeirology.com - LetsEncrypt on sslhost is OK: OK - Certificate 'apeirology.com' will expire on Sun 09 Mar 2025 04:22:02 PM GMT +0000. [03:07:07] RECOVERY - dariawiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'dariawiki.org' will expire on Thu 02 Jan 2025 04:25:01 PM GMT +0000. [03:07:46] RECOVERY - richterian.com - LetsEncrypt on sslhost is OK: OK - Certificate 'richterian.com' will expire on Fri 07 Feb 2025 08:52:27 PM GMT +0000. [03:07:46] RECOVERY - cnidaria.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'cnidaria.wiki' will expire on Tue 18 Feb 2025 05:57:37 PM GMT +0000. [03:08:02] RECOVERY - mwcosmos.com - LetsEncrypt on sslhost is OK: OK - Certificate 'mwcosmos.com' will expire on Sun 02 Mar 2025 02:22:26 AM GMT +0000. [03:08:11] RECOVERY - lads.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'lads.wiki' will expire on Thu 06 Mar 2025 04:34:20 PM GMT +0000. [03:08:19] RECOVERY - runzeppelin.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'runzeppelin.ru' will expire on Fri 07 Mar 2025 06:45:22 AM GMT +0000. [03:08:23] RECOVERY - worldsanskrit.net - LetsEncrypt on sslhost is OK: OK - Certificate 'worldsanskrit.net' will expire on Fri 14 Mar 2025 02:35:17 PM GMT +0000. [03:08:25] RECOVERY - allthetropes.org - LetsEncrypt on sslhost is OK: OK - Certificate 'allthetropes.org' will expire on Thu 06 Mar 2025 08:38:36 PM GMT +0000. [03:08:32] RECOVERY - lotrmc.ru - LetsEncrypt on sslhost is OK: OK - Certificate 'lotrmc.ru' will expire on Sun 02 Feb 2025 04:49:27 PM GMT +0000. [03:08:34] RECOVERY - beyondtheveilrp.com - LetsEncrypt on sslhost is OK: OK - Certificate 'beyondtheveilrp.com' will expire on Fri 21 Feb 2025 07:24:14 PM GMT +0000. [03:08:45] RECOVERY - rosettacode.org - LetsEncrypt on sslhost is OK: OK - Certificate 'rosettacode.org' will expire on Tue 21 Jan 2025 01:55:49 AM GMT +0000. [03:08:45] RECOVERY - agesofconflict.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'agesofconflict.wiki' will expire on Mon 10 Mar 2025 04:04:33 PM GMT +0000. [03:08:45] RECOVERY - sdiy.info - LetsEncrypt on sslhost is OK: OK - Certificate 'sdiy.info' will expire on Sun 02 Mar 2025 02:53:50 PM GMT +0000. [03:08:48] RECOVERY - edapedia.net - LetsEncrypt on sslhost is OK: OK - Certificate 'edapedia.net' will expire on Wed 22 Jan 2025 02:47:33 AM GMT +0000. [03:08:48] RECOVERY - bristolstudenthousingcoop.org - LetsEncrypt on sslhost is OK: OK - Certificate 'bristolstudenthousingcoop.org' will expire on Fri 07 Mar 2025 10:39:11 AM GMT +0000. [03:09:05] RECOVERY - vilexia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'vilexia.com' will expire on Sat 15 Feb 2025 05:40:59 PM GMT +0000. [03:09:21] RECOVERY - spiceandwolf.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'spiceandwolf.wiki' will expire on Wed 05 Feb 2025 03:24:43 AM GMT +0000. [03:09:32] RECOVERY - dkwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'dkwiki.org' will expire on Sat 08 Mar 2025 03:26:18 PM GMT +0000. [03:09:46] RECOVERY - osdev.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'osdev.wiki' will expire on Fri 07 Feb 2025 09:54:48 PM GMT +0000. [03:09:48] RECOVERY - beidipedia.com - LetsEncrypt on sslhost is OK: OK - Certificate 'beidipedia.com' will expire on Wed 22 Jan 2025 02:50:31 PM GMT +0000. [03:09:56] RECOVERY - creativecommons.id - LetsEncrypt on sslhost is OK: OK - Certificate 'creativecommons.id' will expire on Sun 09 Mar 2025 06:07:09 PM GMT +0000. [03:10:30] RECOVERY - maxcapacity.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'maxcapacity.wiki' will expire on Tue 18 Feb 2025 03:36:47 PM GMT +0000. [03:10:57] RECOVERY - mariopedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'mariopedia.org' will expire on Sat 08 Mar 2025 10:39:11 PM GMT +0000. [03:11:12] RECOVERY - exordium.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'exordium.wiki' will expire on Wed 12 Feb 2025 08:08:49 PM GMT +0000. [03:11:21] RECOVERY - antiguabarbudacalypso.com - LetsEncrypt on sslhost is OK: OK - Certificate 'antiguabarbudacalypso.com' will expire on Sat 08 Mar 2025 06:18:35 PM GMT +0000. [03:11:36] RECOVERY - bobobay.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'bobobay.wiki' will expire on Wed 12 Feb 2025 02:26:39 PM GMT +0000. [03:11:37] RECOVERY - wizardia.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'wizardia.wiki' will expire on Fri 03 Jan 2025 02:58:23 AM GMT +0000. [03:11:49] RECOVERY - sptwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'sptwiki.org' will expire on Sun 26 Jan 2025 06:17:34 PM GMT +0000. [03:11:58] RECOVERY - permanentfuturelab.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'permanentfuturelab.wiki' will expire on Thu 02 Jan 2025 04:22:43 PM GMT +0000. [03:11:58] RECOVERY - grayravens.com - LetsEncrypt on sslhost is OK: OK - Certificate 'grayravens.com' will expire on Sat 08 Mar 2025 03:35:29 PM GMT +0000. [03:12:30] RECOVERY - keitaiwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'keitaiwiki.com' will expire on Fri 14 Mar 2025 02:33:57 PM GMT +0000. [03:12:46] RECOVERY - terraforming.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'terraforming.wiki' will expire on Fri 21 Feb 2025 07:02:11 PM GMT +0000. [03:12:46] RECOVERY - farthestfrontier.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'farthestfrontier.wiki' will expire on Wed 12 Feb 2025 08:09:17 PM GMT +0000. [03:13:04] RECOVERY - thestarsareright.org - LetsEncrypt on sslhost is OK: OK - Certificate 'thestarsareright.org' will expire on Sat 08 Mar 2025 11:10:21 AM GMT +0000. [03:13:04] RECOVERY - aryavartpedia.online - LetsEncrypt on sslhost is OK: OK - Certificate 'aryavartpedia.online' will expire on Mon 20 Jan 2025 12:08:24 AM GMT +0000. [03:13:04] RECOVERY - thelonsdalebattalion.co.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thelonsdalebattalion.co.uk' will expire on Thu 06 Mar 2025 09:28:33 PM GMT +0000. [03:13:16] RECOVERY - gielinorgames.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'gielinorgames.wiki' will expire on Sun 09 Mar 2025 10:35:49 PM GMT +0000. [03:13:29] RECOVERY - yokaiwatchwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'yokaiwatchwiki.com' will expire on Fri 14 Mar 2025 02:31:09 PM GMT +0000. [03:13:44] RECOVERY - journeytheword.wiki - Cloudflare on sslhost is OK: OK - Certificate 'CloudFlare Origin Certificate' will expire on Sat 27 Aug 2039 04:37:00 PM GMT +0000. [03:13:46] RECOVERY - electowiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'electowiki.org' will expire on Tue 11 Mar 2025 12:09:09 PM GMT +0000. [03:13:48] RECOVERY - christipedia.nl - LetsEncrypt on sslhost is OK: OK - Certificate 'christipedia.nl' will expire on Sat 15 Mar 2025 02:14:33 PM GMT +0000. [03:14:03] RECOVERY - inourownwords.online - LetsEncrypt on sslhost is OK: OK - Certificate 'inourownwords.online' will expire on Sat 08 Mar 2025 09:05:57 AM GMT +0000. [03:14:06] RECOVERY - ourlifewiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'ourlifewiki.org' will expire on Sun 26 Jan 2025 06:18:01 PM GMT +0000. [03:14:16] RECOVERY - ncuwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'ncuwiki.com' will expire on Sun 09 Mar 2025 05:24:06 PM GMT +0000. [03:14:24] RECOVERY - crashspyrowiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'crashspyrowiki.com' will expire on Sun 09 Mar 2025 03:37:17 PM GMT +0000. [03:15:25] RECOVERY - kunwok.org - LetsEncrypt on sslhost is OK: OK - Certificate 'kunwok.org' will expire on Fri 07 Mar 2025 08:15:03 AM GMT +0000. [03:15:27] RECOVERY - androidwiki.info - LetsEncrypt on sslhost is OK: OK - Certificate 'androidwiki.info' will expire on Mon 27 Jan 2025 03:47:10 PM GMT +0000. [03:15:56] RECOVERY - thegreatwar.uk - LetsEncrypt on sslhost is OK: OK - Certificate 'thegreatwar.uk' will expire on Fri 14 Mar 2025 02:25:51 PM GMT +0000. [03:15:57] RECOVERY - ekumen.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'ekumen.wiki' will expire on Thu 23 Jan 2025 10:33:12 PM GMT +0000. [03:16:28] RECOVERY - vylet.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'vylet.wiki' will expire on Thu 06 Feb 2025 02:42:38 AM GMT +0000. [03:16:31] RECOVERY - rodzinka.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'rodzinka.wiki' will expire on Wed 12 Feb 2025 08:04:19 PM GMT +0000. [03:16:35] RECOVERY - roll-of-arms.com - LetsEncrypt on sslhost is OK: OK - Certificate 'roll-of-arms.com' will expire on Sat 08 Mar 2025 11:49:41 PM GMT +0000. [03:16:41] RECOVERY - comprehensibleinputwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'comprehensibleinputwiki.org' will expire on Tue 11 Feb 2025 02:39:50 PM GMT +0000. [03:16:43] RECOVERY - blackmagic.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'blackmagic.wiki' will expire on Sun 23 Feb 2025 07:21:15 PM GMT +0000. [03:16:58] RECOVERY - ff8.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'ff8.wiki' will expire on Sat 15 Feb 2025 01:05:30 AM GMT +0000. [03:17:00] RECOVERY - squareenixwiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'squareenixwiki.com' will expire on Sun 09 Mar 2025 12:28:04 AM GMT +0000. [03:17:05] RECOVERY - landofliberos.com - LetsEncrypt on sslhost is OK: OK - Certificate 'landofliberos.com' will expire on Sun 09 Mar 2025 08:42:53 AM GMT +0000. [03:17:27] RECOVERY - dccomicswiki.com - LetsEncrypt on sslhost is OK: OK - Certificate 'dccomicswiki.com' will expire on Fri 28 Feb 2025 11:41:34 PM GMT +0000. [03:17:27] RECOVERY - fischipedia.org - LetsEncrypt on sslhost is OK: OK - Certificate 'fischipedia.org' will expire on Mon 10 Feb 2025 06:19:30 PM GMT +0000. [03:17:38] RECOVERY - jackbox.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'jackbox.wiki' will expire on Sat 08 Feb 2025 02:40:00 PM GMT +0000. [03:17:43] RECOVERY - stablestate.org - LetsEncrypt on sslhost is OK: OK - Certificate 'stablestate.org' will expire on Fri 07 Mar 2025 07:29:55 AM GMT +0000. [03:17:43] RECOVERY - hoseki.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'hoseki.wiki' will expire on Sat 08 Mar 2025 01:09:01 PM GMT +0000. [03:17:47] RECOVERY - removededm.com - LetsEncrypt on sslhost is OK: OK - Certificate 'removededm.com' will expire on Sat 08 Feb 2025 12:51:28 PM GMT +0000. [03:18:02] RECOVERY - gimkit.wiki - LetsEncrypt on sslhost is OK: OK - Certificate 'gimkit.wiki' will expire on Wed 05 Mar 2025 02:35:49 PM GMT +0000. [03:18:09] RECOVERY - wikitide.net - LetsEncrypt on sslhost is OK: OK - Certificate 'wikitide.net' will expire on Tue 28 Jan 2025 12:33:59 AM GMT +0000. [03:18:12] RECOVERY - acuralegendwiki.org - LetsEncrypt on sslhost is OK: OK - Certificate 'acuralegendwiki.org' will expire on Sun 09 Mar 2025 02:34:56 AM GMT +0000. [03:18:54] RECOVERY - cp36 Nginx Backend for mw152 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8114 [03:18:58] RECOVERY - cp36 Nginx Backend for swiftproxy161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8206 [03:19:06] RECOVERY - cp36 Nginx Backend for mw184 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8128 [03:19:13] RECOVERY - cp36 Nginx Backend for mw171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8117 [03:19:14] RECOVERY - cp36 Nginx Backend for mw161 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8115 [03:19:14] RECOVERY - cp36 Nginx Backend for mw153 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8121 [03:19:20] RECOVERY - cp36 Nginx Backend for phorge171 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8202 [03:19:30] RECOVERY - ns2 GDNSD Datacenters on ns2 is OK: OK - all datacenters are online [03:19:34] RECOVERY - cp36 Nginx Backend for test151 on cp36 is OK: TCP OK - 0.000 second response time on localhost port 8181 [03:19:38]