[06:26:53] <icinga-miraheze>	 RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 5375 MB (22% inode=95%);
[06:47:25] <RhinosF1>	 Special:Prefix index and Move aren't showing up with changes to namespaces
[07:00:32] <RhinosF1>	 ^ Fixed
[07:07:15] <RhinosF1>	 Could someone look at my logo on Mobile?
[07:12:33] <Reception123>	 RhinosF1: hi. What is your wiki URL?
[07:14:51] <RhinosF1>	 Reception123: https://quirc.miraheze.org/wiki/Main_Page
[07:14:51] <ZppixBot>	 [ QuIRC ] - quirc.miraheze.org
[07:17:10] <Reception123>	 so what exactly is the issue?
[07:17:45] <RhinosF1>	 Reception 123: Whole thing doesn't show on mobile (fine on desktop)
[07:17:53] <RhinosF1>	 Reception123: ^
[07:19:54] <RhinosF1>	 Mobile in desktop mode**
[07:19:59] <Reception123>	 I will check that
[07:20:13] <RhinosF1>	 Thx
[07:23:20] <Reception123>	 RhinosF1: From what I know, there is not exactly a place for logos on the mobile design
[07:23:27] <Reception123>	 For example, https://meta.m.miraheze.org/wiki/Miraheze
[07:23:28] <ZppixBot>	 [ Meta ] - meta.m.miraheze.org
[07:25:01] <RhinosF1>	 Reception123: Desktop mode on a mobile
[07:25:18] <Reception123>	 RhinosF1: ahh ok I see
[07:26:02] <Reception123>	 RhinosF1: It works for me, I can see the logo fine
[07:26:18] <Reception123>	 RhinosF1: Please try to clear your cache that should fix it
[07:30:25] <RhinosF1>	 Reception123: No change - Chrome for iOS - all up to date - iPhone 8
[07:30:51] <Reception123>	 RhinosF1: so what do you see instead of the logo? 
[07:32:05] <RhinosF1>	 Reception123: Only part of it https://usercontent.irccloud-cdn.com/file/KlNcXJh7/58F34B93-F5F4-492D-8882-E2EC36DF4C05.jpeg
[07:33:02] <Reception123>	 hmm that is strange since the size of the logo is perfectly fine
[07:33:53] <Reception123>	 paladox: ^
[07:37:54] <RhinosF1>	 Zppix was thinking about trying an SVG but never got round to it as I couldn't get a non-B&W converter going.
[07:40:12] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjBd8
[07:40:14] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot 039f5ed18 - BOT: Updating services config for wikis
[07:48:50] <Reception123>	 RhinosF1: That could maybe work
[07:49:11] <ZppixBot>	 Hello juul! If you have any questions feel free to ask and someone should answer soon.
[07:50:05] <juul>	 Hi. I just got approved for a wiki on miraheze (thank you so much!) and I enabled the VisualEditor extension (and other extensions) but the VisualEditor extension doesn't work
[07:50:16] <juul>	 I get: "Error loading data from server: apierror-visualeditor-docserver-http: HTTP 404. Would you like to retry?"
[07:50:50] <juul>	 tried in both firefox and chromium, all browser extension disabled, both logged into the wiki and logged out, same error
[07:52:58] <juul>	 and of course the second i post this here it stops giving the error and now it works
[07:53:03] <juul>	 heh, sorry to bug you all
[07:53:39] <Reception123>	 juul: hi. no problem
[07:53:48] <Reception123>	 juul: It's because it takes a few mins before it works after enabling :)
[07:53:55] <juul>	 oh!
[07:54:27] <juul>	 that makes sense
[07:56:14] <RhinosF1>	 Reception123: The SVG thing? Could you do it? I'm not around a decent computer. Also why is [[User:RhinosF1|RhinosF1 (Staff)]] - <small><sup>[[User talk:RhinosF1|Chat!]]</sup><sub>[[Special:EmailUser/QuIRC|Email us!]]</sub> not allowed as a signature
[07:56:54] <juul>	 btw, as soon as the wiki was approved I changed our A record for wiki.counterculturelabs.org to point to the IP that ccl.miraheze.org points to. I'm not sure where I should submit a request for getting the custom domain working?
[08:01:34] <Reception123>	 RhinosF1: I'll see what I can do
[08:01:59] <Reception123>	 juul: please submit one on https://phabricator.miraheze.org
[08:02:00] <ZppixBot>	 [ Main Page ] - phabricator.miraheze.org
[08:02:20] <juul>	 thanks!
[08:03:20] <RhinosF1>	 Reception123: I'll give you some local rights
[08:03:51] <Reception123>	 RhinosF1: thanks, though I'm not sure I can do anything, image conversion is not my thing
[08:08:03] <RhinosF1>	 Reception123:It might work through a photo app - I'm just on my phone now so can't do it. See your talk page
[08:08:22] <Reception123>	 ok
[08:11:08] <Reception123>	 RhinosF1: The thing is, the quality really decreases when converting
[08:11:09] <Reception123>	 https://static.miraheze.org/quircwiki/9/96/Logo1.svg
[08:13:15] <RhinosF1>	 Reception123: I'll put it up for now until I can mess around more. Can you check my signature that I posted above and work out my it's invalid
[08:18:16] <Reception123>	 RhinosF1: it might be too long
[08:18:35] <Reception123>	 RhinosF1: nevermind, it's because you didn't close the <small> tag
[08:41:34] <Not-7290>	 [02miraheze/ssl] 07Reception123 pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/fjBFO
[08:41:36] <Not-7290>	 [02miraheze/ssl] 07Reception123 034e25cf1 - add wiki.counterculturelabs.org cert
[09:10:13] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/fjBFD
[09:10:14] <Not-7290>	 [02miraheze/services] 07MirahezeSSLBot 03f9eea1e - BOT: Updating services config for wikis
[10:12:35] <paladox>	 Reception123: that’s because logos have to be a certain size.
[12:23:46] <icinga-miraheze>	 PROBLEM - elasticsearch1 Puppet on elasticsearch1 is CRITICAL: CRITICAL: Puppet has 15 failures. Last run 2 minutes ago with 15 failures. Failed resources (up to 3 shown)
[12:23:56] <icinga-miraheze>	 PROBLEM - lizardfs3 Puppet on lizardfs3 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 2 minutes ago with 11 failures. Failed resources (up to 3 shown)
[12:24:05] <icinga-miraheze>	 PROBLEM - lizardfs1 Puppet on lizardfs1 is CRITICAL: CRITICAL: Puppet has 10 failures. Last run 2 minutes ago with 10 failures. Failed resources (up to 3 shown)
[12:24:13] <icinga-miraheze>	 PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 2 minutes ago with 12 failures. Failed resources (up to 3 shown)
[12:24:27] <icinga-miraheze>	 PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:24:29] <icinga-miraheze>	 PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 47 failures. Last run 2 minutes ago with 47 failures. Failed resources (up to 3 shown)
[12:24:34] <icinga-miraheze>	 PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle.
[12:24:36] <icinga-miraheze>	 PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 29 failures. Last run 3 minutes ago with 29 failures. Failed resources (up to 3 shown)
[12:24:42] <icinga-miraheze>	 PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 203 failures. Last run 3 minutes ago with 203 failures. Failed resources (up to 3 shown)
[12:24:44] <icinga-miraheze>	 PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 18 failures. Last run 3 minutes ago with 18 failures. Failed resources (up to 3 shown)
[12:24:45] <icinga-miraheze>	 PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 205 failures. Last run 3 minutes ago with 205 failures. Failed resources (up to 3 shown)
[12:24:48] <icinga-miraheze>	 PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown)
[12:24:50] <icinga-miraheze>	 PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 196 failures. Last run 3 minutes ago with 196 failures. Failed resources (up to 3 shown)
[12:24:57] <icinga-miraheze>	 PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 16 failures. Last run 3 minutes ago with 16 failures. Failed resources (up to 3 shown)
[12:25:04] <icinga-miraheze>	 PROBLEM - lizardfs2 Puppet on lizardfs2 is CRITICAL: CRITICAL: Puppet has 12 failures. Last run 3 minutes ago with 12 failures. Failed resources (up to 3 shown)
[12:25:12] <icinga-miraheze>	 PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 194 failures. Last run 3 minutes ago with 194 failures. Failed resources (up to 3 shown): File[authority certificates],File[/etc/apt/apt.conf.d/50unattended-upgrades],File[/etc/apt/apt.conf.d/20auto-upgrades],File[/root/ufw-fix]
[12:25:17] <icinga-miraheze>	 PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 196 failures. Last run 3 minutes ago with 196 failures. Failed resources (up to 3 shown)
[12:25:34] <icinga-miraheze>	 PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 204 failures. Last run 3 minutes ago with 204 failures. Failed resources (up to 3 shown)
[12:32:49] <icinga-miraheze>	 RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 1 second ago with 0 failures
[12:32:57] <icinga-miraheze>	 RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures
[12:33:03] <icinga-miraheze>	 RECOVERY - lizardfs2 Puppet on lizardfs2 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures
[12:33:39] <icinga-miraheze>	 RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 8 seconds ago with 0 failures
[12:33:55] <icinga-miraheze>	 RECOVERY - lizardfs3 Puppet on lizardfs3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:05] <icinga-miraheze>	 RECOVERY - lizardfs1 Puppet on lizardfs1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:12] <icinga-miraheze>	 RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:27] <icinga-miraheze>	 RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:28] <icinga-miraheze>	 RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:34] <icinga-miraheze>	 RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:36] <icinga-miraheze>	 RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:38] <icinga-miraheze>	 RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:39] <icinga-miraheze>	 RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:43] <icinga-miraheze>	 RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:34:49] <icinga-miraheze>	 RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:35:09] <icinga-miraheze>	 RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 44 seconds ago with 0 failures
[12:35:16] <icinga-miraheze>	 RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[12:53:46] <icinga-miraheze>	 RECOVERY - elasticsearch1 Puppet on elasticsearch1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures
[15:02:10] <paladox>	 !log upgrade phabricator
[15:02:26] <RhinosF1>	 You know reply link by Enterprisey from enwiki - Will that work on my wiki?
[15:02:26] <RhinosF1>	 Also editing logged out says email must be confirmed but IPs should be able to edit Talk Pages
[15:02:27] <MirahezeLogbot>	 Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master
[15:29:03] <icinga-miraheze>	 PROBLEM - www.wikimicrofinanza.it - LetsEncrypt on sslhost is WARNING: WARNING - Certificate 'www.wikimicrofinanza.it' expires in 15 day(s) (Mon 10 Jun 2019 03:25:24 PM GMT +0000).
[15:53:10] * Hispano76 saluda
[15:53:19] <RhinosF1>	 Anyone know why IPs can't edit on my wiki (https://quirc.miraheze.org/wiki/Special:ManageWikiPermissions/*#mw-section-handling) - says email needs confirming
[15:53:20] <ZppixBot>	 [ Manage a wiki's permissions - QuIRC ] - quirc.miraheze.org
[15:53:33] <RhinosF1>	 Hispanso76, hi!
[15:53:44] <RhinosF1>	 Hispano76: hi!
[16:12:39] <RhinosF1>	 Paladox: PM
[16:13:42] <paladox>	 RhinosF1 hi?
[16:19:12] <paladox>	 RhinosF1 ips can edit on your wiki
[16:19:12] <paladox>	 just that the only is the main page and you protected it.
[16:19:12] <paladox>	 If you want to allow ips to create pages you need to grant "createpage" right to *
[16:19:31] <RhinosF1>	 Paladox: I fixed it
[16:39:28] <Hispano76>	 https://commonswiki.miraheze.org/wiki/Miraheze_Commons:Community_noticeboard#Logo No more comments? :)
[16:39:29] <ZppixBot>	 [ Miraheze Commons:Community noticeboard - Miraheze Commons ] - commonswiki.miraheze.org
[16:54:08] <Zppix>	 paladox: is parasoid enabled by default?
[16:54:27] <paladox>	 nope, it's only enabled for the wiki if they enable certain extensions.
[16:57:53] <Zppix>	 paladox: its still possible to manually enable it say if a userscript requires it right?
[16:58:22] <paladox>	 Well, nope. You have to add the wiki to parsoids config.
[16:58:52] <paladox>	 we have a script running on miraheze that automatically updates parsoid config when someone enables an extension that uses parsoid.
[17:00:41] <Zppix>	 paladox: but if i added it to the github it wouldnt get removed by the bot right?
[17:00:52] <paladox>	 It would.
[19:36:33] <Not-7290>	 [02landing] 07PlavorSeol opened pull request 03#3: Translate into Korean - 13https://git.io/fjReK
[21:21:25] <icinga-miraheze>	 PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 5061 MB (20% inode=95%);
[21:22:39] <RhinosF1>	 Paladox: Trying to install twinkle unlink and the TW tab is not there
[21:23:39] <paladox>	 is tinkle for wikipedia pages only?
[21:24:01] * paladox dosn't know what twinkle is.
[21:24:12] <RhinosF1>	 paldox: It's a Gadget
[21:24:34] <RhinosF1>	 Paladox: What are the Namespace numbers for every namespace I have enabled?
[21:25:21] <paladox>	 RhinosF1 https://www.mediawiki.org/wiki/Manual:Namespace#Built-in_namespaces
[21:25:21] <ZppixBot>	 [ Manual:Namespace - MediaWiki ] - www.mediawiki.org
[21:26:16] <RhinosF1>	 Paladox: What about custom?
[21:26:32] <paladox>	 it would be what ever number MWN assigned to them
[21:26:41] <paladox>	 it reveals the ns id in the url
[21:26:47] <RhinosF1>	 Okay
[21:31:03] <RhinosF1>	 Paladox: Still nothing
[21:50:32] <ZppixBot>	 Hello Guest17681! If you have any questions feel free to ask and someone should answer soon.
[22:11:17] <Not-7290>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/fjRfc
[22:11:19] <Not-7290>	 [02miraheze/puppet] 07paladox 0366c8ea0 - Users: Add missing 'gid' param Also fixes puppet type for gid field. (Changes it to an Integer)
[22:11:20] <Not-7290>	 [02puppet] 07paladox created branch 03paladox-patch-3 - 13https://git.io/vbiAS
[22:11:22] <Not-7290>	 [02puppet] 07paladox opened pull request 03#1004: Users: Add missing 'gid' param - 13https://git.io/fjRfC
[22:11:37] <Not-7290>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-3 [+0/-0/±1] 13https://git.io/fjRfW
[22:11:39] <Not-7290>	 [02miraheze/puppet] 07paladox 0352dd273 - Update user.pp
[22:11:40] <Not-7290>	 [02puppet] 07paladox synchronize pull request 03#1004: Users: Add missing 'gid' param - 13https://git.io/fjRfC
[22:12:12] <Not-7290>	 [02puppet] 07paladox edited pull request 03#1004: Users: Add missing 'gid' param - 13https://git.io/fjRfC
[22:14:17] <Not-7290>	 [02puppet] 07paladox closed pull request 03#1004: Users: Add missing 'gid' param - 13https://git.io/fjRfC
[22:14:19] <Not-7290>	 [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±2] 13https://git.io/fjRfR
[22:14:20] <Not-7290>	 [02miraheze/puppet] 07paladox 03e4883b4 - Users: Add missing 'gid' param (#1004) * Users: Add missing 'gid' param Also fixes puppet type for gid field. (Changes it to an Integer) * Update user.pp
[22:14:22] <Not-7290>	 [02puppet] 07paladox deleted branch 03paladox-patch-3 - 13https://git.io/vbiAS
[22:14:23] <Not-7290>	 [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-3
[22:31:36] <icinga-miraheze>	 PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[22:33:00] <MH-Discord>	 <PlavorSeol> https://cdn.discordapp.com/attachments/435711390544560128/581973009133207556/unknown.png
[22:33:21] <MH-Discord>	 <PlavorSeol> Error 503 Backend fetch failed, forwarded for [IP ADDRESS HIDDEN], 127.0.0.1 (Varnish XID 45989953) via cp3.miraheze.org at Sat, 25 May 2019 22:31:29 GMT.
[22:33:25] <MH-Discord>	 <PlavorSeol> What happened?
[22:33:32] <icinga-miraheze>	 RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online
[22:33:53] <RhinosF1>	 PlavorSeol, fine for me
[22:34:45] <paladox>	 hi
[22:35:01] <paladox>	 @PlavorSeol i presume your in south asia?
[22:35:08] <paladox>	 based on PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb
[22:35:08] <MH-Discord>	 <PlavorSeol> Also fine for me now, maybe outage for a few seconds.
[22:35:12] <paladox>	 which leads to cp3
[22:35:13] <MH-Discord>	 <PlavorSeol> South Korea
[22:49:16] <paladox>	 i see some 503's in the logs