[08:38:50] Hi, how can I get with the API all existing "Discussion" threads of a namespace? [10:54:59] Hi. Is there a way to get an email notification when my wiki isn't running as it should? [11:11:29] Marekatt: You'd have to use an external tool to monitor your wiki and send those emails [11:12:27] Vulpix: Do you have any suggestions or experience with that? Does it require a lot of know-how? [11:14:19] I don't have experience with this. Sorry. Some monitoring tools may just try to fetch a page and tell if the server is down. However, "a wiki running as it should" is very broad and there are some aspects that can cause failures, like inability to upload files because the disk is full, a problem with an extension causing edits to be rejected, etc [11:22:38] Ah, yes that is a bit too broad indeed. I was thinking more about huge errors like mysql not running and people not being able to access at all. [17:23:31] Marekatt: try netdata https://www.netdata.cloud/ [17:25:03] Hi, I'm trying to install mediawiki software on my raspberry pi to host over the Tor network as an onion site. I'm using lighttpd but I'm a little confused as to what exactly it is I need to do differently to the standard installation guide as well as the specific modifications I need to make to the lighttpd.lighttpd.conf file seeing as I'm trying to host it over the Tor network. As the Tor browser [17:25:09] cannot be used to access localhost and the config page can only be accessed throug h a web browser and onion sites can only be accessed through the Tor browser :/ [17:32:26] I've been searching but I haven't been able to find any information online about setting up mediawiki installations on tor [17:32:49] I've seen a few onion sites use mediawiki so I know it's possible though [17:37:24] burning, personally I'd solve this one problem at a time. get it working, and then get it exposed on tor. [17:39:28] I can access the html.index file I've made in the directory through tor just fine [17:39:49] It's just the mediawiki directory I untarred that seems to not be interfacing with the webserver properly [17:40:21] I'm just unsure whether the root of the problem itself is the webserver config or something else [17:40:43] sorry, I mean whether it's the webserver or if you just can't run the config page through Tor [17:42:02] This is also my first time trying to setup a web server of any kind, so I guess I'd like to know, would it be possible for me to run the config page on localhost through a different browser and then move the configured mediawiki into my Tor website directory? [17:43:04] I've tried all the different possible url's listed in the manual installation guide but they all error 404 [17:43:26] only thing that works is the index.html file [17:44:15] oh, it just ocurred to me! Am I meant to point my web server to the mediawiki directory itself? not the directory containing the mediawiki dir? [17:46:27] because atm, I have /var/lib/mediawiki symlinked into /var/www/html/my_wiki/mediawiki but my tor site is setup to use /var/www/html/my_wiki [17:50:14] burning: Web servers map a URL to a physical directory: For example, http://localhost/something to /var/www/html/something. Usually only the root path is mapped, but you can add additional mappings, like for example pointing http://localhost/mediawiki/ to /var/lib/mediawiki [17:50:41] each web server software has its own way to do such things [17:57:20] I just don't understand why I can't get the config page up. I can access the index.html file stored in /var/www/html/my_wiki perfectly fine by entering the site's hostname into my Tor browser. The mediawiki directory is symlinked to that directory as well so it'd make sense that doing /config would work to bring up the config page but it doesn't seem to. and /mediawiki/config [17:57:26] doesn't work either [17:57:29] it just 404's [17:59:28] MediaWiki starts on the index.php page. You should explicitly put index.php in the URL [18:00:07] unless you have the "default document" directive set up, telling the server to open index.php automatically if it exists when navigating to a folder [18:03:23] I have it set so it looks for the index.php page first, then the index.html page [18:05:05] but seeing as the index.php is one directory deeper than the server root document I'd assume that's why [18:05:48] my server.document-root is set to be /var/www/html/my_wiki [18:06:14] that directory contains the receiving end of a symlink to my /var/lib/mediawiki directory [18:06:46] so in essence, my mediawiki directory is itself within the /var/www/html/my_wiki directory [18:07:45] I'll try /mediawiki/index.php and see if that works [18:09:36] ah, it gives an error 403, forbidden [18:11:27] any idea why that might be? [20:13:07] if you do localhost, can anyone on your LAN access that website? or is it just local to the machine itself? [20:44:32] burning: localhost is only accessible to your own computer. You'll need to specify at least your host name or IP address accessible from the LAN [21:13:13] Vulpix: Oh ok, I thought that's how it worked, I just wanted to check [21:14:02] I'm trying to setup my mediawiki site on a headless raspberry pi, so I can't access the config page unless it'd be available on the site itself [21:14:24] but whenever I try to access the mediawiki/index.php page it gives me an error 403 [21:14:53] I can access the index.html file I have outside of the /mediawiki directory though [21:15:00] any idea why that is? [21:43:07] is php installed and enabled on the webserver? [21:43:27] first, check permissions. PHP files must be readable by the webserver [21:43:48] but maybe if php is not installed, the webserver is denying access to prevent leaking the code [22:08:34] php is installed [22:08:41] latest version i think [22:09:05] though how would I check that php is readable by the web server? [22:09:45] Actually, I think I set up a user specifically for lighttpd, I think it's the www user [22:10:17] Have you enabled PHP in your webserver/vhost? [22:12:03] I'd think so [22:12:16] It's more helpful if you know so [22:12:17] hold on, give me a moment to check my lighttpd config file [22:16:04] From reading the config file, the only things I'd assume have any bearing on whether PHP is enabled would be index-file.names which lists index.php and index.html; and the static-file.exclude-extensions bit which lists .php , .pl , and .fcgi [22:16:23] simplest test is create an index.php where your index.html works [22:16:29] contents ofc, I'll try that now [22:18:44] would I need closing tags after that first line? I have some minimal past experience with html and CSS but I'm rather unfamiliar with php [22:19:45] Generally closing tags are nto needed [22:37:51] ah, trying to access the index.php file gives an error 403 [22:38:04] so I take it that PHP isn't enabled? [22:39:28] /configured correctly in lighttpd [22:39:43] check the error log [22:40:45] ok, so it's configured incorrectly in lighttpd? How would I check the error log? [22:41:59] I checked /etc/lighttpd where the lighttpd.conf file is but there isn't an error log there [22:45:40] it'd probably be in /var/log [22:49:43] Trying translate off Left side bar link " User help " -> Help:Contents, which i believe is a Template PD thing. Six boxes with a few links in each. When i hit translate (above, below Languages box at top ) i get only the box headers, not the bullet points inside. [22:51:10] Translate matter. So how do i get INSIDE this template matter, and translate those bullet points ? (forgot this question at my last entry ). [22:53:36] there are only two error logs in my /var/log/lighttpd directory and they're both from july 25th and july 27th respectively [22:53:59] @Reedy: none from today [22:54:10] would you say that's normal? [22:54:23] seems strange [22:54:56] depends on logrotate [22:55:09] what are the file names? [22:55:32] error.log and error.log.1 [22:56:29] just did cat on both of them, weirdly enough, log.1 was older, it was from the 25th [22:56:48] the other one only goes up to the 27th [22:57:00] and it just mentions the times i retarted the pi when it was freezing the other day [22:57:01] .1 would be older [22:57:27] I would've thought the number would increase with every log? [22:57:31] that's interesting [22:57:43] nope [22:57:52] it's basically the opposite [22:58:12] error.log -> error.log.1 -> error.log.2.gz etc [22:58:35] that way you don't need to work out which is the right/most recent log [22:58:38] it's always error.log [22:58:43] ah, that's handy [22:59:28] I'll see if the tor error logs mention anything then, if the lighttpd error logs don't help [23:00:02] aaand the tor log directory is empty. Guess it hasn't had any errors to log yet [23:00:46] why would the tor log have anyhting in? [23:01:28] What guide did you follow to setup PHP etc? [23:01:30] I figured it might've mentioned stuff like error 403's if the web server logs didn't bother but i guess it handles more serious stuff than that [23:03:09] I never really did anything past installing php like it said here: https://mediawiki.org/wiki/Manual:Running_MediaWiki_on_Debian_or_Ubuntu [23:03:47] lol [23:03:49] I configured the SQL like it said there [23:04:26] In the same way you have to install libapache2-mod-php5 (or similar) for apache and PHP... [23:04:35] but with the section where it says to configure PHP, I couldn't find any files in /etc relating to it so i figured I'd wait until I got the server working before working on that bit [23:04:51] https://pimylifeup.com/raspberry-pi-lighttpd/ [23:06:07] oh, was i meant to remove apache2 this whole time? [23:06:18] if it's still installed... [23:06:25] they're probably going to fight over port 80 [23:06:31] unless you change the config [23:07:30] I'm removing apache2 now [23:07:41] I had no idea the fact it was on my pi by default would interfere [23:07:52] I assumed it'd just sit there idly, unconfigured [23:08:09] waiting until the day i decided to open it up and use it to serve a website or something [23:09:31] most people don't need multiple webservers.... [23:09:58] ik, I just figured it was an alternative I might want to try out someday for another project or something [23:10:07] so i didn't bother deleting it [23:10:27] You could use MW in apache [23:10:35] just apache is generally considered heavy [23:14:40] thanks for the link, going through it now. Hopefully it'll solve a few things :) [23:19:25] any idea why it wants me to completely remove the bin-path definition? /usr/bin/php-cgi [23:38:46] @Reedy: Ok, after following the guide on that link you sent, it's now giving me an error 503 Service Not Available when I try to access the index.php file with nothing in it but that single line [23:39:08] check the error log again? :P [23:39:26] I tried connecting to the hostname.onion/wikimedia/ and hostname.onion/wikimedia/index.php but that just 404'd [23:39:29] ok, one sec [23:40:51] ah, it says all handlers for /index.php? on .php are down [23:41:37] even though I followed that guide you sent me, I ran every step iirc [23:41:50] I must've gone wrong somewhere? [23:42:07] potentially [23:42:22] I'm pretty sure I followed that guide verbatim [23:43:10] cat /etc/lighttpd/conf-available/15-fastcgi-php.conf [23:43:24] woops, wrong terminal [23:44:12] yeah, I checked the php.conf file, I made the exact modifications that guide said to