[00:22:58] <c3bolla>	 what does this mean? "Note that the python3 binary must be installed in the execution PATH of the PHP interpreter."
[00:23:19] <c3bolla>	 what is my interpreter?
[00:25:12] <c3bolla>	 oo probably mod_php
[00:44:24] <c3bolla>	 nope. no idea
[01:16:29] <c3bolla>	 welp it's fucking working now. Must be that damn resource loader again
[12:07:16] <Ajit7825>	 Hello All , while installing the 1.35.1 media wiki , i see below error while setting up the database Cannot connect to database mediawiki: Cannot access the database: pg_connect(): Unable to connect to PostgreSQL server: could not connect to server: Permission denied Is the server running on host "dapintdbsdb01.dap" (172.18.1.140) and accepting
[12:07:16] <Ajit7825>	 TCP/IP connections on port 5432?
[12:07:41] <Ajit7825>	 but in the backend I can connect to the databse with the correct user , 
[12:07:47] <Ajit7825>	 could someone help ?
[12:08:23] <Reedy>	 There is no MW 1.35.1
[12:08:25] <Ajit7825>	 Correction : 1.31.5
[12:08:29] <Reedy>	 :)
[12:10:24] <Reedy>	 I'm not familiar with postgresql's security etc... But it..
[12:12:09] <Reedy>	 I'm not familiar with postgresql's security etc... But it sounds a lot like grants/permissions
[12:12:15] <Reedy>	 Is it on a separate host?
[12:17:49] <Ajit7825>	 yes its in the separate host and the permissions are ok , like i said i could connect from backend (wiki server) to data base 
[12:19:01] <Reedy>	 permissions don't sound ok if it's getting permission deniedd
[12:22:39] <Ajit7825>	 this is the proof permission is ok : https://dpaste.de/PtPC
[12:23:46] <Reedy>	 [root@dapwikisdb01 includes]# psql -h dapintdbsdb01.dap -d mediawiki -U mediawiki_usr
[12:23:52] <Reedy>	 You're connecting to the DB from the same host that the DB is on
[12:24:03] <Reedy>	 So that proves nothing if mediawiki is running on a different server
[12:26:54] <Ajit7825>	 it was the selinux issue 
[12:27:02] <Ajit7825>	 fixed it by deactoivation the selinux 
[12:27:11] <Ajit7825>	 not true what you said Reedy 
[12:27:18] <Ajit7825>	 but fixed :)  
[12:27:53] <Reedy>	 Well, it is true
[12:28:01] <Reedy>	 Either you're running your MW on db server
[12:28:08] <Reedy>	 Or your pastebin doesn't prove what you said it proves
[12:29:23] <Ajit7825>	 no check the server names , they look same but they are different 
[17:01:30] <faceface>	 hi
[17:01:48] <faceface>	 The installer is telling me, "Warning: Your default directory for uploads /var/www/html/mediawiki/images/ is vulnerable to arbitrary scripts execution.
[17:02:09] <faceface>	 But I've set and tested the Direcory config as suggested
[17:03:12] <faceface>	 How is that test performed?
[17:06:29] <Skizzerz>	 did you reboot apache or your webserver after changing the config?
[17:06:54] <faceface>	 Yeah, and I can see a .html file in images that is being sent back as text, not rendered
[17:07:05] <Skizzerz>	 it's talking about .php files
[17:07:19] <faceface>	 OK, I'll try a simple php
[17:07:34] <Skizzerz>	 do "<?php phpinfo(); ?>" as a test
[17:07:37] <faceface>	    AddType text/plain .html .htm .shtml .phtml .php .php3 .php4 .php5 .php7
[17:07:38] <Skizzerz>	 without the quotes obv
[17:07:41] <faceface>	 sure
[17:08:57] <faceface>	 Yup, renders as text, not interpreted
[17:10:40] <faceface>	 also renders as text if I use AddType text/plain .html .htm .shtml .phtml, because of php_admin_flag engine off
[17:11:16] <faceface>	 if I comment that out and drop .php from the AddType, it executes the function. So my config is being respected and is working
[17:12:26] <faceface>	 actually the AddType alone doesn't stop it rendering, but it does stop the .html from rendering...
[17:12:55] <Skizzerz>	 yeah AddType doesn't do anything for PHP. Not sure what it's checking then, lemme dig it up
[17:14:31] <faceface>	 thanks Skizzerz 
[17:14:48] <faceface>	 I'll remove it from the docs there (it's confusing enough wihtout errors)
[17:17:00] <JeroenDeDauw>	 Did the MW_VERSION constant get removed in some recent MW version? 
[17:20:15] <faceface>	 hi JeroenDeDauw 
[17:21:52] <JeroenDeDauw>	 hi faceface 
[17:34:57] <faceface>	 Skizzerz: I 'fixed' the directory permissions and the warning has gone away!
[17:35:03] <faceface>	 I acually made them less strict
[17:35:08] <faceface>	 so I didn't expect that to fix it
[17:35:13] <Skizzerz>	 erm...
[17:35:28] <Skizzerz>	 it'd be better to have a secure setup with the warning than doing something arbitrary which makes the warning go away
[17:35:36] <Skizzerz>	 (sorry haven't had time to actually look into the code yet, doing 300 other things atm)
[17:35:47] <faceface>	 https://www.mediawiki.org/wiki/Manual:Configuring_file_uploads says the /images folder (or the /uploads folder in previous versions) to have permission "755":
[17:36:14] <faceface>	 Skizzerz: it's not totes arbitrary, it lets other users see the contents, just not upload 
[17:36:47] <faceface>	 I had set it to go-rwx
[17:36:52] <faceface>	 or x I think
[17:37:57] <faceface>	 If the server doesn't allow to set or override directives in .htaccess files, accessing any file under that folder may result in a generic "HTTP 500 error". If that's the case, you should comment-out the lines, and apply those directives directly on the server configuration files
[17:38:24] <faceface>	 The setup explicitly tells you to turn off over rides, so I gues I should copy the contents to the config?
[17:44:26] <Skizzerz>	 faceface: checked the code, it tries to execute PHP in the directory by first writing a .php file there and then fetching it via HTTP to see if it is executed
[17:44:39] <Skizzerz>	 so, if it's giving the warning, it's definitely allowing execution somehow
[17:44:55] <faceface>	 weird
[17:45:01] <faceface>	 Are you sure it stops there?
[17:46:00] <faceface>	 hmm... I tightened up the perms again and reloaded the page, no warning
[17:46:09] <faceface>	 could be a caching issue?
[17:46:13] <Skizzerz>	 quite possibly
[17:46:15] <faceface>	 I'm ctrl-r reloading
[17:46:20] <faceface>	 (always)
[17:47:17] <faceface>	 restarted installation... no warning
[17:47:18] <faceface>	 sigh