Welcome to the MediaWiki Support desk. This is a place where you can ask any questions you have about installing, using or administrating the MediaWiki software.
For issues about the mediawiki.org website, report toVillage Pump instead.
Ask technical questions about Wikimedia websites onmeta:Tech instead.
Post a new question
To help us answer your questions, please indicate which version of MediaWiki you are using, as found on your wiki'sSpecial:Version page:
If possible, add$wgShowExceptionDetails = true;error_reporting( -1 );ini_set( 'display_errors', 1 ); to LocalSettings.php in order to make MediaWiki show more detailed error messages.
Please include theweb address (URL) to your wiki if possible. It's often easier for us to identify the source of the problem if we can see the error directly.
To start a new thread, click the box with the text "Add topic".
Latest comment:9 days ago10 comments3 people in discussion
Myprevious attempt to solve an issue with my wiki made some progress and fixed a few errors, but turned up a new one: "Lua error: bad argument #1 to "get" (not a valid title)." The suggestions in the related threads I found (1,2) mention "JsonConfig", but I've enabled both "JsonConfig" and "JsonConfigLuaSupport" in LocalSettings and have installed the "REL1_43" (1.2.0) version of the former and the error remains. The following is the backtrace:
I tried creating a file named "CommonSettings.php" in the "public_html/w" folder and copy-pasting the code from apage on phabricator into it and adding either "require_once("public_html/w/CommonSettings.php");" or "require_once("CommonSettings.php");" to "LocalSettings.php" based on the instructions onManual:CommonSettings.php, but it didn't work. –Noha307 (talk)04:11, 20 October 2025 (UTC)Reply
I'm suffering from the exact same lue error/backtrace message. I also required TitleBlacklist - which I enabled and fixed it's associated error message - but this hasn't fixed the inital Lua error: bad argument #1 to "get" (not a valid title) error. @Noha307, have you been able to fix the issue?~2025-30174-48 (talk)22:17, 26 October 2025 (UTC)Reply
@~2025-30174-48 I did the same – download and enable TitleBlacklist – and it didn't fix the Lua error either. I haven't had a chance to browse the pages with script errors category in detail yet though. Would it be possible for you to link to your wiki so I could compare? –Noha307 (talk)23:56, 26 October 2025 (UTC)Reply
My wiki looked the exact same as yours with the same errors and backtraces - I've solved the issue by fixing the Json extension config in my LocalSettings.
I changed it to the code below from another support thread on here and the error is resolved:
// Safety: before extension.json, these values were initialized by JsonConfig.php if ( !isset( $wgJsonConfigModels ) ) { $wgJsonConfigModels = []; } if ( !isset( $wgJsonConfigs ) ) { $wgJsonConfigs = []; } $wgJsonConfigEnableLuaSupport = true; // https://www.mediawiki.org/wiki/Extension:JsonConfig#Configuration $wgJsonConfigModels['Tabular.JsonConfig'] = 'JsonConfig\JCTabularContent'; $wgJsonConfigs['Tabular.JsonConfig'] = [ 'namespace' => 486, 'nsName' => 'Data', // page name must end in ".tab", and contain at least one symbol 'pattern' => '/.\.tab$/', 'license' => 'CC0-1.0', 'isLocal' => false, ]; // Enable Tabular data namespace on Commons - T148745 $wgJsonConfigInterwikiPrefix = 'commons'; $wgJsonConfigs['Tabular.JsonConfig']['remote'] = [ 'url' => 'https://commons.wikimedia.org/w/api.php' ];~2025-30174-48 (talk)20:56, 27 October 2025 (UTC)Reply
@~2025-30174-48: Thank you so much! Adding that code seems to have fixed it – or at least the most immediate error anyway. I particularly appreciate you specifying which file it goes in as well.
I'm still getting a "the time allocated for running scripts has expired" error after the reflist template loads 66 references, but at least its getting to that point now. –Noha307 (talk)03:56, 2 November 2025 (UTC)Reply
┌───────────────────────┘ So, according toone thread, I need to change max execution time, which can be found in php.ini. (Although I am suspicious because it seems like it shouldn't take that long to load 66 references. Could there be another cause, such as a missing template or extension that could prolong it?) However, adifferent page seems to suggest that the change can be made to LocalSettings.php. While I do know where the latter file is, I don't how I should change it. What code do I need to add? –Noha307 (talk)01:24, 3 November 2025 (UTC)Reply
@Noha307: Sorry for the late reply, but you should be able to useset_time_limit() in yourLocalSettings.php. If you really want to setmax_execution_time in yourLocalSettings.php, you can do that like so:
Strangely, bothset_time_limit() andmax_execution_time don't seem to change much, if anything. (What's the difference between them? According to athread, it's that one returns an error warning and the other doesn't?) The number of references it loads every time the page is refreshed fluctuates in a roughly single digit range no matter what is entered – and I'm not even sure that's connected. I even tried some ludicrously high values (e.g. 48000) and it didn't help. The only thing that is consistent is that setting the value to "1" gives me a 500 error when I try to load a page.
So, I importedTemplate:Harvard citation Wikipedia, as it was missing from my wiki and at some point thereafterone of the pages stopped having reference errors. (Note: I have never used that template anywhere on my wiki.) However, two others were stuck failing after loading the same number of references as before. After a few more imports, addingTemplate:Kbd finally did the trick. Woohoo! I guess I should have listened to your suggestion to look through the pages with script errors category. My apologies for wasting your time and thank you again for all of your assistance!
One final note: From the beginning I was intent on describing every step in this process in the event it might prove informative to someone with the same problem in the future. I didn't want to be likeDenverCoder9. –Noha307 (talk)07:06, 17 November 2025 (UTC)Reply
Latest comment:6 days ago4 comments2 people in discussion
Hi! I've recently installedhttps://wiki.lilypond.community, a wiki for theLilyPond music typesetter (which is used on Wikipedia throughExtension:Score). Pages consist of small snippets of LilyPond code, with explanatory comments and an image of the result. Is there any way to make the lists of search results (e.g.,this) display these images? This would be very helpful for users to quickly finding snippets when they don't know the proper keywords.Jean Abou Samra (talk)16:35, 31 October 2025 (UTC)Reply
Thanks a lot, this looks like exactly what I need. Unfortunately, it didn't work on my wiki after installingPageImages andSearchThumbs and running the maintenance scriptinitImageData.php fromPageImages as specified in the docs. I strongly suspect it's because the images on this wiki are not inserted with the normal wikitext markup but as inline SVG using<img src="data:image/svg+xml;base64,...">. This is because they're generated by anextension I wrote myself (relevant part of the code here), not MediaWiki'sExtension:Score, because this wiki has somewhat peculiar needs. While writing the extension I found it much simpler to just inline the SVG than figure out how to store the images as files and delete the old images when music inputs change. What do you think is the easiest way out of this?Jean Abou Samra (talk)16:10, 14 November 2025 (UTC)Reply
@Jean Abou Samra: If you are generating the SVGs inline, then it is going to be difficult to show them as part of the search results. So, I'd say that you need to update your work to use separate files or, alternatively, write up what your special needs are that the Score extension doesn't meet.
Latest comment:6 days ago12 comments5 people in discussion
I have just migrated my wiki from an old version to version 1.44. It has all gone well except that I still have a bold red line around my logo and the link for the Main Page. I assume these were there to remind you to change the logo, which I have done, so how do I get rid of the lines? Here is a link to my wiki:JP1 Remotes Wiki Thanks.Robman94 (talk)22:04, 3 November 2025 (UTC)Reply
@Robman94 No, it is not obvious as I cannot see some red line around some logo after clicking on your link. Please be more specific where you see what, provide a screenshot, inspect the problem via your web browser's development tools, etc. Thanks!Malyacko (talk)20:58, 5 November 2025 (UTC)Reply
Are you familiar with what a fresh install of Mediawiki looks like? The default logo and the link to the main page both have think red lines around them, presumably to remind you to change them. The question is, what is supposed to make them go away once you do change them? The fact that you can't see them when you go to my wiki tends to imply that the code that generates the red lines must be stored locally in the cache or something, but I've done ?action=purge already and that didn't clear it. Does anyone here know how that line is generated and how to clear it?Robman94 (talk)13:55, 6 November 2025 (UTC)Reply
I have never seen those red lines before on any new install, and I'm not seeing them in YOUR wiki neither. However, you can try to inspect them with the browser's developer tools (hit the F12 key in your keyboard) and try to locate from which CSS it comes from.Ciencia Al Poder (talk)22:31, 6 November 2025 (UTC)Reply
Yeah, I brought up the wiki on a different browser (Firefox) and I don't see them there either, but I do see them using Chrome and Edge. You can see them on the screenshot thought, right? (talk)02:01, 7 November 2025 (UTC)Reply
Just a quick update to say that I am still struggling with this. I have spent many days with Copilot trying absolutely every suggestion that it can think of, but still the red lines persist. I only see them in Edge and Chrome, not Firefox, but that's because I tested the site in the first 2 browsers before I uploaded my logo. So, my advice for anyone installing a new wiki is, be sure to load your logo before you test the site, or you'll never get rid of these red lines. I've even tried completely uninstalling and re-installing the browser, but that didn't work either. I am currently downloading all of my wiki files so that I can scan them using Notepad++ to try and find where there the "border: 6px solid red !important" text is coming from, so I can delete it.Robman94 (talk)19:00, 18 November 2025 (UTC)Reply
Thanks for the tip, but it turns out that something that we did yesterday must have fixed it, because I don't have any red lines today. I must have spent over 8 hours with Copilot trying every trick it could think of, but sometimes you just have to wait for cache to expire, no matter how much we purged it.Robman94 (talk)19:59, 19 November 2025 (UTC)Reply
Did you actually install theTranslate extension? If not, you should remove all the #translation bits and anything related to it. The version of the doc from the English Wikipedia is much easier to adapt to third party wikis.Tactica (talk)03:30, 13 November 2025 (UTC)Reply
My version Mediawiki is 1.43.1 and Module:Message box:16:31, 2 September 2023 Module:Message box>Pppery 18,558 bytes +18,558
Latest comment:5 days ago8 comments3 people in discussion
I updated from 1.43.1 to 1.44.2 and noticed this message at the end:
PHP Warning: Undefined array key "directory" in /var/www/html/w/includes/filebackend/FileBackendGroup.php on line 133
The wiki seems to be working ok, if maybe a little slower than before. I then went and upgraded PHP from 8.1 to 8.3. The message is still the same. What does this mean?Buster2223 (talk)23:08, 13 November 2025 (UTC)Reply
OK I am fairly sure that this is slowing down the wiki. Images that used to load instantly now take a second, and large pages are delayed by several seconds. My guess is that the primary path to the images doesn't work, then it looks for a fallback and finds it.
Thank you for the information. I found the same errors in my log that the others found. I also have the same problem with thumbnails.
In my opinion this should not be "low priority". It dramatically slows down MediaWiki when pages with more than a few images are loaded. I would discourage anyone from updating from 1.43 to 1.44 until this is fixed.Buster2223 (talk)20:37, 19 November 2025 (UTC)Reply
Very reassuring! But ok, I would hope that this will get sorted out by the time 1.45 is released, which is scheduled for December 2025, and so it should be on everyone's to do list for the next few weeks.Buster2223 (talk)13:11, 20 November 2025 (UTC)Reply
I think I found the problem. It has to do with the recently implemented Wikimedia Foundation User Agent Policy. As far as I can tell, Commons works but the thumbnail directory is being blocked because the User agent needs to be identified. The fix is described here:InstantCommons#Set_custom_user_agent. I changed LocalSettings, ran an update, and the error message is gone. The warnings have also disappeared from the error log.Buster2223 (talk)14:34, 20 November 2025 (UTC)Reply
Latest comment:8 days ago3 comments3 people in discussion
I updated this wiki instance a while back, currently running REL1_43 and the specialpages throw this error;
```
[aRevfSkKRKsH1Ux47UpwvQAAAG4] /go/Special:SpecialPages ArgumentCountError: Too few arguments to function MediaWiki\Specials\SpecialRenameUser::__construct(), 0 passed in /srv/www-sugarlabs/wiki/vendor/wikimedia/object-factory/src/ObjectFactory.php on line 240 and exactly 7 expected
Backtrace:
from /srv/www-sugarlabs/wiki/includes/specials/SpecialRenameUser.php(48)
Latest comment:10 days ago7 comments3 people in discussion
Hi, since I am not familiar with tech-savy stuff and being new to coding in general, I don't know how to run a seperate wiki website. I already downloaded and extracted the file in mobile. I tried to throughly read the process multiple times but it seemed too complicated for me. The thing I need help with is the uploading the files to the web server. Does anyone help me with the basics of installing MediaWiki on Android mobile?VoitieVelocity (talk)01:59, 15 November 2025 (UTC)Reply
Yes, running/hosting a webserver from scratch is indeed complex. I would say that it is very hard to do from a mobile device, i would suggest to use a desktop machine for any serious work where you need lots of information to look at and to enter.
Welp, I tried making articles for a certain specific topic in English Wikipedia, but it takes time for the draft to get accepted into being a full article and some things may not be considered notable. So I might consider making a seperate wiki website, so that the things related to the topic that are not considered notable would get moved to the seperate wiki website instead. I have experience in using Fandom and I would like to say that it is hard to reach a lot of people since many people might not know the existence of other hosting services that hosts wikis besides Wikipedia.VoitieVelocity (talk)09:51, 15 November 2025 (UTC)Reply
I might try finishing the draft again and see if that draft gets accepeted into being a full article in English Wikipedia. If that got declined as well, I think I won't likely to create a seperate wiki website using MediaWiki, I still go on Fandom to continue contributing to that unfinished wiki which needs a lot of improvements. Yeah, I am busy on Fandom because I edit a lot of wikis.VoitieVelocity (talk)14:48, 15 November 2025 (UTC)Reply
Running a MediaWiki website on your own is inherently complex. There are some sites that offer fully-managed solutions for it, but it's rare, and you'll have to pay either way.Jasper Deng (talk)22:21, 15 November 2025 (UTC)Reply
Latest comment:6 days ago2 comments2 people in discussion
Hello MediaWiki, I recently installed the Wikibase extension version 1.44 for my Wiki, which is version 1.44.2, but the update script doesn't want to update and gives an error due to a database issue. Моя вики ru.encyclowiki.ru@Therudekiweweffffffff (talk)14:35, 18 November 2025 (UTC)Reply
Latest comment:24 minutes ago15 comments3 people in discussion
I have a Rocky Linux-9 server running OpenLDAP over sssd. I can login, sudo, etc., so I know that LDAP is working. I have also created an ldapprovider.json file using the same values:
# Load extensionswfLoadExtensions(['PluggableAuth','Auth_remoteuser','LDAPProvider','LDAPAuthentication2','LDAPAuthorization','LDAPUserInfo']);# LDAP configuration$wgLDAPUseLDAP=true;$wgLDAPServers=['ldaps://ldap.my.com'];$wgLDAPBaseDNs=['dc=my,dc=com'];$wgLDAPRDN='$username';$wgLDAPUserFilter='(&(uid=$username)(objectClass=posixAccount))';$wgLDAPUserBaseDNs=['ou=people,dc=my,dc=com'];$wgLDAPAttributes=['realname'=>'cn','email'=>'mail',];$wgLDAPHygiene=true;# Path to the configuration file$wgLDAPProviderConf="$IP/../ldapprovider.json";#$wgLDAPProviderConf = '/var/www/html/mediawiki/ldapprovider.json';#$wgLDAPProviderConf = 'ldapprovider.json';$wgDebugLogGroups['ldap']='/var/log/mediawiki/ldap_debug.log';$wgShowExceptionDetails=true;// In any case we need to specify LDAP domain configs#$LDAPProviderDomainConfigs = "/var/www/html/mediawiki/ldapprovider.json";$LDAPProviderDomainConfigs="$IP/../ldapprovider.json";// If local login is supported as well, then these globals are still needed$wgPluggableAuth_EnableLocalLogin=true;#---------------Extension LDAPAuthentication2---------------$LDAPAuthentication2AllowLocalLogin=true;$LDAPAuthentication2UsernameNormalizer='strtolower';#---------------Extension LDAPProvider---------------$ldapJsonFile="$IP/../ldapprovider.json";$LDAPProviderDomainConfigs=$ldapJsonFile;$wgPluggableAuth_Config['Log In (LDAP)']=['plugin'=>'LDAPAuthentication2','data'=>['domain'=>'my.ldap']];
That line refers tocount( $this->configArray ), where configarray is$this->configArray = FormatJson::decode( file_get_contents( $jsonFilePath ), true ); which in turn implies an invalid json file. The extensions should probably improve it's error handling in situations like that, and I suggest you file tickets with the extension maintainer, or of course submit a gerrit change. —TheDJ (Not WMF) (talk •contribs)12:42, 19 November 2025 (UTC)Reply
I have now tested the connection using LDAPSEARCH and found that I could bind in clear. I also used JSONVALIDATE to check my ldap file and that is also ok. I now get a new error:
aR3OL_Q_6TYooanu46D4IwAAAFM] /index.php?title=Special:PluggableAuthLogin TypeError: MediaWiki\Config\HashConfig::__construct(): Argument #1 ($settings) must be of type array, null given, called in /var/www/html/mediawiki/extensions/LDAPProvider/src/DomainConfigFactory.php on line 77
Backtrace:
from /var/www/html/mediawiki/includes/config/HashConfig.php(52)
I have done more testing and the latest version of OpenLDAP only supports SSL/TLS. If you connect in clear it will not decrypt passwords so you can only check usernames.
I tried both:
"port": 636,
"enctype": "ssl",
Returns: PluggableAuthLogin MWException: Could not bind to LDAP: (-1) Can't contact LDAP server
and
"port": 389,
"enctype": "tls",
Returns: /index.php?title=Special:PluggableAuthLogin MWException: Could not start TLS!
I think that more SSL/TLS configuration is required. My LDAP certs are self-signed and not the same as those of the LDAP servers themselves which are using fully-signed wildcard certs (*.acme.com) . My LDAP works perfectly on this server and is using sssd.
PHP Warning: ldap_start_tls(): Unable to start TLS: Connect error in /var/www/html/mediawiki/extensions/LDAPProvider/src/PlatformFunctionWrapper.php on line 141
MWException from line 168 of /var/www/html/mediawiki/extensions/LDAPProvider/src/Client.php: Could not start TLS!
I have been testing my certificates and my LDAP server's CA cert is self-signed so: openssl s_client -CAfile /etc/openldap/certs/ca.pem -connect ldap1.com:636 returns: Verify return code: 21 (unable to verify the first certificate).
Verify return code: 21 (unable to verify the first certificate)
If I add: -no_tls1_3 to the command I just see the code: 21, therefore I suspect that the Wiki plugin needs to be able to either fall-back to TLS1.2 or to allow for a self-signed CA cert.
It would also be really nice if there were some working examples showing the contents of LocalSettings.php and ../ldapprovider.json enabling a connection to AD and OpenLDAP.Techietubby (talk)12:42, 20 November 2025 (UTC)Reply
I spent a lot of time talking with Robert Vogel one of the LDAP plugin and we discovered the reason that the host wasn't connecting. He wrote this script and it showed that the OS needed the LDAP CA cert needed to be trusted by the OS.
<?php
error_reporting( -1 );
ini_set( 'display_errors', 1 );
$ldapconn = ldap_connect("ldaps://ldap.test.com:636") or die("Could not connect to LDAP server.");
Latest comment:4 days ago3 comments2 people in discussion
In late 2024, a new category appeared on all wikis called "Category:Pages using the JsonConfig extension" which included all pages with a citation, unless theMediaWiki:Jsonconfig-use-category was created with "-". Now it appears that across all wikis, this category (Wikidata link:d:Q130635582) has become empty and many have been deleted. Was the software configuration changed to no longer populate this? Can it just be deleted everywhere?~2025-34912-63 (talk)17:14, 19 November 2025 (UTC)Reply
Latest comment:1 day ago4 comments2 people in discussion
So I'm wanting to make a table inside of myTabberNeue, because I don't feel like making a template since there isn't enough information for it to have it's own. It works if I put it into a simple tabber, but if I put it into a nested tabber, it doesn't work.
|-| For This Device =Several devices have their own blocks that can run functions or obtain data that other devices can't.{{#tag:tabber|Damager=There is 1 block specific to the[[Damager]].{|class="wikitable"!Image!Tooltip!Input types!Is an input?!Dropdown 1!Dropdown 2!Configurable settings|-|[[File:Damage block.png|frameless|231x231px]]|None|Number.|No|DNE|DNE|None|}{{!}}-{{!}} Inventory Item Manager={|class="wikitable"!Image!Tooltip!Input types!Is an input?!Dropdown 1!Dropdown 2!Configurable settings|-|[[File:IIM block.png|frameless|176x176px]]|None|None|Yes|DNE|DNE|None|}}}</tabber>
Whenever I try this, all I see is the text at the beginning, one nested tab, and a bracket. Am I doing something wrong? Do I have to use templates?Fulcrum-19 (talk)00:41, 21 November 2025 (UTC)Reply
I actually have a starting tabber before that, so that isn't the issue. There's a lot more to the tabber, I just copy-pasted the part that wasn't working.Fulcrum-19 (talk)01:28, 23 November 2025 (UTC)Reply
Latest comment:3 days ago2 comments2 people in discussion
Does anyone have a script showing how they build the certificates for use with OpenLDAP? I created a CA and then a cert and key signed with the CA. They work fine with OpenLDAP and Linux sssd but not with older nslcd libraries, and it appears not with Mediawiki. No matter what I try I get either "Can't Connect" or "Can't start TLS".
The only clue I can find is that the CA certificate shows as being self-signed.
@Techietubby:: I don't have an LDAP server available at the moment to test, but you need to configure PHP and/or your local OpenSSL stack to recognize the CA as authoritative. You should be able to by using, for example, update-ca-certificates onDebian orUbuntu orupdate-ca-trust on redhat-derived linuxes. --☠MarkAHershberger☢(talk)☣14:40, 22 November 2025 (UTC)Reply
Latest comment:1 day ago2 comments2 people in discussion
Hello,
I am a developer and maintainer for the projecthttps://wikiromandie.org, a wiki for Swiss French part of Switzerland.
I am trying to build our Mediawiki images on Github actions, but my builds fail with the remaining error :
Error: error: RPC failed; HTTP 429 curl 22 The requested URL returned error: 429
Error: fatal: the remote end hung up unexpectedly
Unable to fetch in submodule path 'extensions/Wikibase/view/lib/wikibase-data-model'; trying to directly fetch 6b304daeb804591ddc4520925337429ac086515c:
Error: fatal: Fetched in submodule path 'extensions/Wikibase/view/lib/wikibase-data-model', but it did not contain 6b304daeb804591ddc4520925337429ac086515c. Direct fetching of that commit failed.
Error: fatal: Failed to recurse into submodule path 'extensions/Wikibase'
Error: The process '/usr/bin/git' failed with exit code 128
While installing the Wikibase extension. And our build won't go further.
