דף לבן ריק מציין שגיאת PHP שאינה מודפסת למסך.כדי לכפות זאת, הוסיפו את השורות הבאות לקובץLocalSettings.php, מתחת ל-<?php
error_reporting(E_ALL);ini_set('display_errors',1);
ניתן גם להגדיר ערך עבורerror_log בתוךPHP.ini ולקרוא את יומן השגיאות של PHP כדי לברר מה קורה.In some cases, PHP errors might also be recorded in the web server error log.
Error reports may include:
date.timezone = is set correctly (or set at all) inphp.ini.media folder in your/includes folder is no longer present, you may receive the message that a required imaging process "failed to open stream").Check the original installation package at MediaWiki (make sure to consult the appropriate version) to see if this is the case.If so, simply copy the missing files from the package into your MediaWiki directory.It may be necessary to refresh the cache and restart the webserver afterwards.LocalSettings.php is set to the correct MySQL socket butphp.ini is not, it may result in a blank screen with no error output from the webserver or PHP.The fix is to update themysql.default_socket entry in thephp.ini file.Many people report blank pages in recent versions after submitting articles to their new wiki.A likely cause is the memory limit in default php installations (usually 8 MB).Please check your PHP and/or Apache error logs.To modify this setting edit/etc/php.ini and increase the "memory_limit" setting.For example to raise it to 32 MB replace the existing text withmemory_limit = 32M.Make sure to restart your webserver after you have changed this value.
The memory limit may also have been set in yourLocalSettings.php file.Scan for the line containing the memory_limit setting and increase as needed.20M may not be enough if you are running version 1.15.1.Change it to e.g. "memory_limit = 32M".This change does not require you to restart Apache.
If the page just hangs loading during some time (like 30 seconds) doing a specific action, and then it results in a blank page or HTTP 500 error, the problem is a timeout connecting to some server.This may be the database server, or if it happens doing a specific action, the mail server (if you have configured email settings).If it's the email server, check if you can connect to it from the server running MediaWiki, for example, running theTelnet client to the server and port configured on$wgSMTP and seeing if it can connect.
If you can see the page contents briefly, and suddenly the entire page goes blank, most likely the problem is caused by the presence of adocument.write,document.writeln, ordocument.open JavaScript instruction in one of the scripts of the wiki.You can check if that's the case if you open your browser console (hit F12) and reload the page.If the network tab returns a HTTP 200 status, and the transfer is of several kilobytes, it's very likely this is the problem.These are legacy methods of theDocument interface that cause the entire page to become blank if it's used outside of the page HTML, and it may be present on thewiki's JavaScript pages.Their usage is strongly discouraged, as indicated by theHTML specification itself.You can disable JavaScript on your browser, or set$wgUseSiteJs and$wgAllowUserJs tofalse to disable those scripts until you fix the broken scripts.
This section lists problems and solutions relating to thumbnails not rendering or displaying.
This might happen due to wrong values of global variables as explained in:
If image thumbnails simply don't appear, and there's no error visible on those pages, look at the HTML source of the page and search for "srcset".If you find something like<img ... srcset="/images/thumb/File.png/600px-File.png 1,5x, /images/thumb/File.png/800px-File.png 2x">, where it appears1,5x instead of1.5x, the problem is caused byT181987, and you should add this to LocalSettings.php:
setlocale(LC_NUMERIC,"C");
First, determine your$wgSVGConverter setting.By default, it is set to use ImageMagick for conversion.
You need at least ImageMagick 6.x.x.Ensure that your$wgImageMagickConvertCommand variable is valid.Common settings are:
$wgImageMagickConvertCommand="/usr/bin/convert";$wgImageMagickConvertCommand="/usr/local/bin/convert";
If it does not work, try setting$wgSVGConverterPath.
$wgSVGConverterPath="/usr/bin";$wgSVGConverterPath="/usr/local/bin";
Shared hosts may provide different ImageMagick versions to meet the needs of different users.Please use version 6.x.x.
/usr/bin/convert --version or/usr/local/bin/convert --version to detect.If generating thumbnails with ImageMagick fails with a web server error log message like "Memory allocation failed" or "/bin/ulimit4.sh: Segmentation fault /usr/bin/convert ...", the$wgMaxShellMemory value may need to be increased.
When the path is missing non-ASCII characters
locale -alocale-gen en_US.utf8 or put in the locales with UTF-8 for your country and change the value for$wgShellLocale according to this.When using IIS/FastCGI on Windows, the guest account that is used also needs execute permission on C:\Windows\System32\cmd.exe otherwise you will receive an "Unable to Fork" error.
MediaWiki places time and memory limits on shell commands under Linux.If you receive the error "Error occurred during initialization of VM, Could not reserve enough space for object heap, Could not create the Java virtual machine.", try increasing the value of$wgMaxShellMemory.
On some Linux and BSD installations rsvg is renamed:
Instead of setting (default)
$wgSVGConverters=array('rsvg'=>'$path/rsvg -w$width -h$height $input $output');
you would like to set
$wgSVGConverters=array('rsvg'=>'$path/rsvg-convert -w $width -h $height -o $output $input');
Symptom:This error message within a grey box:
One cause: the number of pixels in the original image exceeding$wgMaxImageArea.The default value 1.25e7 is too small for many modern cameras.Too bad the diagnostic really doesn't hint at the problem.
You can increase the value of$wgMaxImageArea or switch to using ImageMagick which evades this restriction (set$wgUseImageMagick and$wgImageMagickConvertCommand).
Large images can take significant processing time.It may be good policy to cap the size of images.
Symptom:This error message within a grey box:
Some PHP 4.x and 5.x versions of PHP have a bug where libjpeg is detected but not enabled during the./configure step; this is fairly prevalent on Red Hat/RHEL/CentOS systems.If you don't want to use ImageMagick, the fix for this is to recompile PHP.First, find out (fromphpinfo()) what the existing./configure switches were, and add--with-jpeg-dirbefore--with-gd.
makeclean./configure--with-various-switches--with-jpeg-dir--with-gd--with-more-switchesmakemaketest# switch to rootmakeinstall
Afterwards, restart the webserver (for Apache on Red Hat:service apache stopthenservice apache start ).To test, simply view the File:... page again (no need to upload again).For more information see the comments onPHP: imagecreatefromjpeg (function synopsis)
If you get the error "Error generating thumbnail / Error creating thumbnail: Unable to save thumbnail to destination" and the$wgUploadDirectory directory has the correct permissions (at all levels), check that$wgTmpDirectory actually exists.(Unlike some path variables such as$wgCacheDirectory, $wgTmpDirectory is not created at runtime.)A more detailed error message may be available if you turn on logging with$wgDebugLogFile.
This error can also occur when read only mode ($wgReadOnly) has been set inLocalSettings.php.You can try to remove$wgReadOnly
If you get "Error creating thumbnail Error code: 25" with ImageMagick, try increasing$wgMaxShellFileSize.
In situations in which it's not feasible to create the thumbnails dynamically on request (e.g. for very large images, "Error creating thumbnail: unable to extend cache", "Error creating thumbnail: convert: no images defined", and similar), it is possible to manually add the thumbnail files.This involves creating the smaller images in the desired sizes and uploading them to thethumb/ directory in$wgUploadDirectory.
For example, a file that has uploaded to:
images/f/f8/Foo.png
should have its thumbnails at:
images/thumb/f/f8/Foo.png/100px-Foo.pngimages/thumb/f/f8/Foo.png/600px-Foo.png
The pixel size is the horizontal dimension.An example Bash script for creating thumbnails is available atPhabricator:P7049.
For unidentified reason, creation of thumbnails on some mutualized OVH hosting are failing with this error, even if running the command in SSH shell works.
Solution is to specifically prevent from using ImageMagick by setting$wgUseImageMagick tofalse in LocalSettings.php:
$wgUseImageMagick=false;
If your Apache server has theHardened PHP patch, you may need to edit several variables in your /etc/php.ini file if you wish to have wiki pages with large amounts of content.In particular, consider the settings forvarfilter.max_value_length,hphp.post.max_value_length,hphp.request.max_value_length.The default settings may limit your pages to less than 10k or 64k in size.
Another possibility is if your Apache server is usingmod_security that could be interfering with MediaWiki.You will need to turn it off for MediaWiki to work properly.
This is caused by something truncating or dropping POST data from the browser to the web server.
In at least one instance, this was caused bypost_max_size andupload_max_filesize in php.ini being set too high (2048M).Setting them back to more sane values (8M) fixed it.Apparently, no POST data was actually making it through to MediaWiki.
In another instance, mod_auth_sspi was interfering with http posts to MW.Using FireFox and entering domain credentials would work fine, but MSIE would fail.This is a known defect in mod_auth_sspi 1.0.4.
You have a few options to make this work:
If the wiki looks fine if you browse it from the same server where it's being hosted but it appears without CSS styles applied (no colors, no backgrounds, no images, very minimal formatting, etc) if you access it from other machines (or some of them), the most probable cause is that the server is having problems with determining the IP or host name that is being used to access it, or it's misconfigured.This causes URLs to styles and images to be generated using the loopback IP address 127.0.0.1, localhost, or a host name not known outside of the server.You can see the source code of any page and check how URLs look like and what happens if you try to access them directly via your browser.
The solution is to manually specify the$wgServer variable to the host name that everyone will use to access the wiki.
If your wiki is being accessed from an internal network and an external one, you may need to use the external address for$wgServer.Don't forget the port number if you are using a non-standard port as may by the case if your ISP has blocked port 80 (Example:$wgServer="http://example.domain.com:8080";)
If styles aren't applied even when browsing the wiki from the server where it's hosted, the problem may be a PHP error on theResourceLoaderload.php script.Try to browse the load.php file of your MediaWiki installation with your web browser and see if it displays any errors or just a blank page (see#You see a Blank Page).You should see a comment similar to/* No modules requested. Max made me put this here */.If so, it may be a problem with the web server's.htaccess file.
If you instead see a 404 Not found error, it may be a problem with the web server's rewrite rules if you attempted to configureShort URLs.
If you are getting 500 error responses from load.php urls, check the webserver's error log files to get more information of the errors.There seems to be a problem with some PHP versions and Gentoo that causes Apache to segfault.[1]This can also happen if you have APC enabled, settingapc.serializer=php in php.ini might help.[2]
Since MediaWiki 1.23, you may end with a wiki with most of the Vector-specific skin styles, like sidebar placed at the end of the page.That may be caused by a lowpcre.backtrack_limit set up on some distributions like FreeBSD.It's known to have problems with values of 10,000.Increase that value to 100,000, or the current default of 1,000,000.
Since MediaWiki 1.26, some skins, and specially Vector, may have this problem.If you see the errorInternal error Problematic modules: {"startup":"error"} in the error console of your browser, most likely cause is the lack of permissions of MediaWiki to write to the default temp folder, either because PHP has no permissions to write to/tmp (C:\WINDOWS\TEMP on Windows), or because there's anopen_basedir restriction and that path isn't included on it.SeeT119934.You can also set$wgTmpDirectory if you are unable to change permissions on the system's default temp directory.
| MediaWiki version: | ≥ 1.20 |
If you get that error message after upgrading, you must run therebuildLocalisationCache.php maintenance script with the--force option:
php rebuildLocalisationCache.php --force
If you are seeing this, try running therebuildLocalisationCache.php maintenance script with the--force option:
php rebuildLocalisationCache.php --force
This will force MediaWiki to rebuild the localisation cache.
If JavaScript is not working (one of the symptoms is the edit toolbar not appearing when editing a page) it may be caused by a JavaScript error.Open the error console of your web browser (usually by hittingF12), reload the page and see if any error message appears there.If it displays an error, usually, setting$wgShowExceptionDetails would give you more information.Sometimes the problem is that the system's temp directory is not writable.In that case, you can also set$wgTmpDirectory if you are unable to change permissions on the system's default temp directory.
If you get errors likeUncaught SyntaxError: Unexpected token < orError: SyntaxError: syntax error (...) Source Code: <script (...), the cause is usually a hosting provider that is automatically injecting HTML code for tracking or advertising inside theLoad.php script, which is used byResourceLoader to load the scripts and CSS used by MediaWiki.Open a support ticket with your hosting provider asking them to disable that injection.If that's not possible, you should migrate your site to another hosting provider.That usually happens on free hosting providers.
Try rebuilding the Localisation Cache:
php maintenance/rebuildLocalisationCache.php
Fromthis thread.
It may be caused by wrong rewrite rules when configuringShort URLs.Try disabling them (and the related configuration variables of MediaWiki) to see if that solves the problem.
Another problem may be a limit imposed by the web server about how many data the server can receive on a single request.SeeManual:Configuring file uploads#Set maximum size for file uploads for some configuration variables.If you have mod_security or suhosin installed, they may also be limiting the size of uploaded files, discarding the upload entirely without PHP noticing it.
Check also theupload_tmp_dir configuration directive from php.ini, and be sure that the folder has proper write permissions for the user account running PHP.On Windows, this directive often points toC:\Windows\TEMP, which may not be accessible in some circumstances.In that case, you can set up a different temp folder like C:\TEMP\ with proper permissions.To discard other problems, give temporarily all permissions to that folder (on Windows, add the local user group "Everyone" with full permissions), and then restrict the permissions as needed once you verify uploads are working.
If all uploads fail with the message "נראה שהקובץ שהעלית ריק.ייתכן שהסיבה לכך היא שגיאת הקלדה בשם הקובץ.יש לוודא שזה הקובץ שברצונך להעלות.", and in the Apache error logs you have entries like this:
Notice: Undefined index: tmp_name in /srv/www/htdocs/mediawiki/includes/WebRequest.php on line 1153Notice: Undefined index: size in /srv/www/htdocs/mediawiki/includes/WebRequest.php on line 1140Notice: Undefined index: error in /srv/www/htdocs/mediawiki/includes/WebRequest.php on line 1167
This is a problem with the PHP version your server is using.There have been several reports of this problem with PHP 5.3.8 on SLES11 sp2.You may need to upgrade PHP or recompile it yourself.
It may happen, on Windows installations under Apache, that someSpecial pages are inaccessible, giving a error, and in the logs you can see something like this:
[core:error] The given path is misformatted or contained invalid characters: [client 127.0.0.1] AH00127: Cannot map GET /wiki/Special:SpecialPages HTTP/1.1 to file
This can be caused by various PHP bugs.One of them is when the wiki is installed in a NTFS junction.If that's not the problem, upgrading PHP to a newer version can help (see this forum thread)
This is a common issue for shared host which havemod_security enabled.To know if it's a problem with mod_security or not, create a simple test page and save it with a small text (something as simple as writing just a dot in the content).If the edit is saved, but other edits aren't, that's caused by mod_security.Ask your hosting customer support to disable it completely or the rules affecting your edits.
If even saving a very simple edit gets you redirected to the main page, or to the same page without the edit appearing, it may be a problem with how you've set up$wgServer or some other configuration variable that controls the path of the index.php script, or conflicts with rewrite rules in your webserver's configuration.
 | Parts of this page (those related tothis section) areoutdated. It was written for an older version of MediaWiki and may not apply to the most recent version. If you have checked or updated this page and found the content to be suitable, please remove this notice.(2020-04-02) |
You may get a message likeMediaWiki עושה שימוש בעוגיות כדי להכניס משתמשים למערכת.בדפדפן שלך העוגיות מבוטלות.יש להפעיל אותן ולאחר מכן לנסות שוב.
.
If cookies aren't disabled on your browser, it could be one of those problems:
$wgSessionsInMemcached set totrue but MediaWiki can't connect to Memcached.Turn off this setting or check the Memcached configuration.Setting adebug log should display any cookie received by MediaWiki, so it may be a first step to detect if cookies are actually received by MediaWiki or not.
It may help to increase$wgMaxImageArea to get rid of the problem (tried with MediaWiki 1.26.2).
If images are not displayed on the pages, and manually opening the URL of any image results in an Internal Server Error page, the problem is most likely caused by the.htaccess file from theimages directory.This configuration file contains some rewrite rules to prevent old Internet Explorer versions from being affected by a cross site scripting vulnerability.However, some hosts like strato.de prevents disallow theRewriteOptions directive in .htaccess, causing any request for a file in the images folder to fail with an error.If you can't enable rewrite rules on .htaccess file, you may need to comment-out or remove those lines from .htaccess, or the entire .htaccess altogether.Seethis thread.
By default, there's a filter in Recent Changes to hide edits made by bots. Clear this filter and see if the edits appear.
If enabling the display of edits made by bots doesn't make them appear in Recent Changes, the problem is usually in one of the installed extensions, causing an error when Recent Changes are updated.The update of Recent Changes when performing an edit or other action is deferred until the page has been sent to the browser.However, an error can abort such updates, and the error not get displayed to the user.To detect such errors,Set up a debug log file (remember to disable it once you've completed the diagnosis), and save a new edit to a page.If an error happens, it should be logged there — but note it will also log a lot of other things, try to search for "error" or "exception".An error may give a stack trace of the execution, and it may point to an extension likely causing the error.
Ensure your extensions are compatible with your MediaWiki version.
Information about pages contained in a category, links to other wiki pages and images embedded in pages are tracked in special tables.The update of such tables is not done immediately after the edit is saved, but deferred to thejob queue for performance reasons.If it takes too long to update, you may need to adjust$wgJobRunRate, or try setting$wgRunJobsAsync tofalse in LocalSettings.php.This can happen in some installations, especially since MediaWiki 1.27 (seeT142751).
Check that the "images" directory has permissions which allow writing.For example:chown -R www-data:www-data images andchmod -R 777 images.
If you haveSELinux enabled, this could also be problematic.
You need to create an alias file.So, put something like this in yourextension.json file:
"ExtensionMessagesFiles":{"SpecialMyExt":"MyExt.alias.php"},"MessagesDirs":{"MyExt":["i18n"]},
Then create an alias file like this:
MyExt.alias.php
<?php/** * Aliases for Special:Foo * * @file * @ingroup Extensions */$specialPageAliases=[];/** English (English) */$specialPageAliases['en']=['MyExt'=>['MyExt'],];
Make sure you don't have a$wgMessagesDirs item with the same key.Keys of$wgExtensionMessagesFiles which are also in$wgMessagesDirs will be skipped.
Probably you just moved your wiki, and didn't import your database, so it's empty.
To fix the warning, uncomment this line in LocalSettings.php:
#$wgCacheDirectory = "$IP/cache";Please followManual:How to debug/Login problems.
If a MediaWiki extension shows this error after installing that MediaWiki extension, double-check that you downloaded the version or branch of that MediaWiki extension which matches the version or branch of your MediaWiki installation.
The function has been disabled inphp.ini.This prevents usingImageMagick to resize images to create thumbnails.Either contact your hosting provider, or try to usegd instead ofImageMagick by setting$wgUseImageMagick tofalse.
user_touched for user ID '*' (read from slave); the version of the user to be saved is older than the current versionThere are several reasons for this error.One simple one is if the content ofuser.user_touched is empty or is set to a time in the future.
You might want to check if the server's time is set correctly and synchronized.Also check the contents of that column and fill the column with valid content e.g. with this SQL statement:
UPDATE`user`SETuser_touched='20250718170022'WHEREHEX(user_touched)='0000000000000000000000000000';-- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^-- 28 zeroes
Where the date is in YYYYMMDDHHMMSS format for the current date/time.Seephab:T247751.
If you recently upgraded MediaWiki, or recently installed or upgraded extensions, try running theupdate.php maintenance script.(See alsoמדריך:שדרוג.)
If that doesn't help, then you really may have ran into a bug in the software.Try to obtain more details about the query that fails (Manual:How to debug) andfile a bug.
Your system does not support/dev/urandom so the key was generated withmt_rand().See$wgSecretKey.
If the PHP version on your web server should be recent enough, check if you have several PHP versions installed in parallel.
Create a file calledinfo.php with the single-line content<?phpphpinfo(); and place this file in the web directory.Access it with your web browser.It will display the PHP version that is used by your web server.
Raise PHP's memory limit in php.ini:
memory_limit=64M; Maximum amount of memory a script may consume (32MB)
| MediaWiki version: | ≥ 1.16 |
You can add a higher value for$wgMemoryLimit in LocalSettings.php.
| MediaWiki version: | ≤ 1.15 |
ini_set('memory_limit','20M');
This error happens when PHP hasn't been compiled with DOM support, or the DOM/xml extension is missing.
php-xml package for your distro. Example:sudo yum install php-xml$wgParserConf)That issue seems to indicate it's a problem with a PHP code accelerator that doesn't match the installed version of PHP or it's outdated.Try upgrading the accelerator.report
Most likely, your text editor added abyte order mark (BOM) while you edited MediaWiki's PHP files, but any other content before the opening<?php causes the same problem.This usually happens withLocalSettings.php - but see error message for exact file.Note that BOMs are invisible in most text editors.To remove the BOM, edit the file with something better than Windows Notepad, but if you don't really have time - open the file with it and chooseSave as..., then choose "Unicode (UTF-8 Without signature) - Codepage 65001" as file type.
If you get Strict Standards: errors in the HTML output, that's because yourerror_reporting configuration variable of PHP is set toE_ALL, but since PHP 5.4.0, E_STRICT became part of E_ALL.E_STRICT are not errors, but warnings about code interoperability and forward compatibility of PHP code, and they shouldn't be visible in production environments.
Just add your time zone to LocalSetting.php, e.g.
$wgLocaltimezone='Europe/Berlin';
The following does not work in all cases.It may be better to put this in the php.ini which must be present in all affected directories.
You may turn off E_STRICT errors putting the following line of code inside yourLocalSettings.php, or in case a line with theerror_reporting function exists, replace it with:
error_reporting(E_ALL&~(E_STRICT|E_NOTICE));
You can turn off PHP error reporting entirely using this instead:
error_reporting(0);
See also:Setting error reporting in PHP.
If nothing works, please check at the start of your LocalSettings.php file:If that error happened on the setup process, the LocalSettings.php that it generated could have included the error message at the top of it (example).If that was what happened, edit the file removing everything before "<?php<?php
This could happen if you upgraded and you have aStartProfiler.php file in the root MediaWiki installation directory, probably because you enabled profiling in an old installation.To solve the issue simply remove that file.
| MediaWiki version: | ≤ 1.24 Gerrit change 203631 |
After your move, you might see PHP warnings that certain files could not be accessed.This is most likely caused byT37472:The columnmd_deps in themodule_deps table contains absolute file paths, which are used to locate the images and LESS files that CSS depends on.These paths break when the wiki is, e.g., moved to another folder or another server.Since MediaWiki 1.25,update.php now deletes the contents of themodule_deps table, thus clearing the cache.module_deps also is no longer used for tracking images and LESS files that CSS depends on.For MediaWiki 1.24 and older, you can use this workaround to manually fix wrong entries in themodule_deps table:
-- Update entries in <code>module_deps</code> tableSET@old='wiki.old-domain.org';SET@new='wiki.new-domain.org';UPDATE`module_deps`SET`md_deps`=REPLACE(`md_deps`,@old,@new);
This can be used to update wrong path segments and to fix the error.
| MediaWiki versions: | 1.17 – 1.26 |
A similar issue can happen when MediaWiki tries to read ResourceLoader messages.In this case the solution is to truncate the according tables:
-- Truncate message related cachesTRUNCATETABLE`msg_resource`;TRUNCATETABLE`msg_resource_links`;
chown orchgrp to correct the file permissions ofLocalSettings.php.sudo setenforce 0.The installer is unstyled and instead of the stylesheet,/mw-config/index.php?css=1 shows this error message: "Less_Exception_Parser from line 447 of ...\vendor\oyejorge\less.php\lib\Less\Parser.php: Less.php cache directory isn't writable: C:\Windows\TEMP"
Make sure that the webserver user, who by default is namedIUSR, is allowed to access the C:\Windows\TEMP directory.At least read and write permissions are necessary.
You need to Grant permissions on wikidb.*.
GRANTALLONwikidb.*TO'username'@'localhost'IDENTIFIEDBY'password';
or if your Web Server is on a different box than your DB server - you have to configure remote access to MySQL and grant differently
GRANTALLONwikidb.*TO'username'@'192.168.0.x'IDENTIFIEDBY'password';
NOTE: Replace 192.168.0.x with your Webserver's IP.Also note that the apostrophes (') need to stay.
As above, or temporarily use the mysql root user.
PHP MySQL support is not installed/enabled - Seehttps://php.net/book.mysqli.Depending on your operating system, you may need to install an additional package.For example, on debian/ubuntu runsudo apt install php-mysql.
If you are using a different FTP client than FileZilla to upload files to your server, be sure to configure the client tonot force uppercase or lowercase filenames.MediaWiki filenames are case-sensitive.
The MediaWiki package includes a lot of files, spread over dozens of directories.Be careful when uploading.If the transfer is interrupted, you might have missing or incomplete files.You may have to retry your upload several times, especially if you have an unreliable connection.
If your webserver produces a "403 Forbidden error" page and you are using symbolic links, then make sure your Apachehttpd.conf file hasOptions FollowSymLinks to allow symbolic links and that each directory leading up to your linked directory has+x permission for user running httpd.
If your webserver produces a "500 Internal Error" at the beginning of the install process, you may need to change the permissions on themw-config directory to 755.If you have changed the permissions for the config directory and still get an unwritable error try changing the owner to Apache.
chown-Rapache:apache/var/www/html/mediawiki/*
If you downloaded the MediaWiki codefrom Git, and after finishing the installation process, accessing your MediaWiki installation in the web browser produces a "500 Internal Error", go to the MediaWiki installation folder and running the following commands:
find.-typef-execchmod644{}\;find.-typed-execchmod755{}\;
Linux distributions which support SELinux ('Security Extensions') are becoming more widespread.On such systems, PHP scripts will still be unable to write to the config directory, after you have set the normal file permissions.You will also need to use the 'chcon' command to change the SELinux file type.
If you are running the MediaWiki software on a free site that requires banners or prefix advertising, this may cause MediaWiki not to work, and appear to only generate empty pages beyond the banner advertising.You will have to contact your host to make them make their advertising compatible with MediaWiki, or choose a different host.
If you are running the MediaWiki software on Debian with Apache2 and PHP5, and have problems connecting to MySQL, e.g you get the following error message in your browser:(Can't contact the database server: MySQL functions missing, have you compiled PHP with the --with-mysqli option?) try uncommenting:extension=mysqli.so
If that does not work, try the following...
Check that MySQL module for php is installed:
dpkg--list|grepphp-mysqlIf you need to install the php5-mysql module enter:
apt-getinstallphp-mysql
Then restart Apache2:
/etc/init.d/apache2restart
Ensure that MySQL is not running in strict mode.
If you are using a hosting service, the database name and database username may have an extra prefix (normally the userid given by your hosting provider).For example, if you have created a database named db01 with username u01 and your userid is ocom (given by your hosting provider), you should enter the database name and database username as ocom_db01 and ocom_u01 respectively.
If you are getting the error:failed with error [2013] Lost connection to MySQL server during query. orfailed with error [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13)., this may be caused by using the wrong database host name or by a permissions issue with the mysql.soc file or directory.
If you are using a hosting provider, ensure that you are using the correct host name for the database.
The MySQL manual hasa good set of pages on dealing with common errors (such as these).Visit the page for links to documentation for other versions of MySQL.
If you are unsure if MySQL is even installed, try the commandmysql from the command line; if it is not installed, seeManual:Running MediaWiki#System-specific instructions.
Errors include:
PHP must have access to /usr/bin.In php.ini (probably/etc/php/php.ini), add:/usr/bin/ to open_basedir config variable as below:
open_basedir=/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/:/var/www/:/usr/bin/
To disable GIT set$wgGitBin to a path that's allowed but doesn't exist.
$wgGitBin="";
This is usually an issue with the configuration of your web server software and unrelated to MediaWiki itself.See for examplethis Stackoverflow thread or other web server forums.
When this happens on every page, this is usually caused by a wrongמדריך:כתובת URL קצרה configuration, usually because of an error in a redirect rule.
This can also happen when$wgForceHTTPS is set totrue, and somehow MediaWiki isn't properly detecting the protocol used by the client, and keeps sending a redirect to https:.This may happen when MediaWiki is set behind a reverse proxy that isn't setting theX-Forwarded-Proto HTTP header tohttps.
rc_timestamp field ofrecentchanges table. Should not happen.Might e.g. happen on upgrading from MW 1.27 to another version.If there is no database content at all you might see this message.Seephab:T236671.
This may happen if you didn't specify the same$wgDBprefix as your original installation, causing MediaWiki to not find its tables.Check the existing tables on the database and see if they all share a common prefix, and update that setting accordingly.
Another cause may be that you set an empty database.Reinstall the database content from a backup and proceed with migrating.
Some upgrades cannot be performed without an intermediary upgrade.For instance, to upgrade from a wiki older than 1.33 to MW 1.39.1, you will need to upgrade to 1.35 first.See taskphab:T326071.
This error message can also be a red herring.It may appear when you are trying to update an empty database, without tables.Create the database first byinstalling the wiki.