Note: You are currently viewing documentation for Moodle 3.1. Up-to-date documentation for the latest stable version of Moodle is probably available here: Installation FAQ.
- 1 System information needed for Installation problems forum
- 2 PHP - is it installed and what version do I have?
- 3 What & where are Moodle's configuration settings stored?
- 4 Downloading previous releases of Moodle
- 5 How to enable and check PHP error logs
- 6 Email copies are not being sent from my forums
- 7 I can't log in - I just stay stuck on the login screen
- 8 I log in but the login link doesn't change. I am logged in and can navigate freely.
- 9 Uploaded files give "File not found"
- 10 Why are all my pages blank?
- 11 Why is a particular page blank or incomplete?
- 12 Installation hangs when setting-up database tables
- 13 Why can't I upload a new image into my profile?
- 14 Why doesn't my Moodle site display the time and date correctly?
- 15 How do I uninstall Moodle?
- 16 How do I upgrade Moodle? Do I just overwrite the files?
- 17 I obtain the message "Upgrade already running in this session, please wait!"
- 18 Migrating Moodle to a new site or server
- 19 Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?
- 20 Maximum upload file size - how to change it?
- 21 How do I install Moodle on Windows Vista?
- 22 Moodle claims PHP float handling is not compatible
- 23 When upgrading Moodle claims my database is not UTF8 when I'm sure it is
- 24 How do I run multiple instances of Moodle without duplicating base code?
- 25 What is FreeTDS and how can I use it in my installation?
- 26 How do I install a plugin?
- 27 See also
System information needed for Installation problems forum
When posting questions to the Installation problems forum, try to provide as much background information as possible about your Moodle system. Use this template to copy and paste into your post:
- Server Operating System name (version also if possible):
- Browser name (version also if possible):
- Moodle version:
- Moodle install type? (New/Upgrade):
- Moodle config.php attached?(Y/N):
- Phpinfo attached? (Y/N):
For the last two items, try to include the following in your post as an attachment:
- A copy of your phpinfo output as shown in your browser (see the instructions above for an explanation of how to obtain this, or see phpinfo).
- A copy of the Moodle configuration file (with secret info like database password deleted, of course). This is located in the main Moodle directory (by default called moodle), and is named config.php
Copy and paste both of these into a single text file (using vi, Notepad, etc) and attach this to your post. If your PC is a Windows box and config.php looks messy (line breaks missing or in the wrong places) in Notepad, try Wordpad.
If you cannot provide your phpinfo, try to copy & paste and complete these in your post:
- Webserver (e.g. Apache/IIS) version:
- Database server (e.g. MySQL, PostgreSQL) version:
- PHP version:
For installation on web hosting accounts: contact your support desk who should be able to tell you this information.
- Security Warning: Make sure you edit any files and delete any passwords before posting onto the forum.
PHP - is it installed and what version do I have?
Make a new file on your web site called info.php, containing the following text, and call it from your browser:
<?PHP phpinfo() ?>
If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the phpinfo page for details about the content of this page.
What & where are Moodle's configuration settings stored?
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the Configuration file docs. Please remember that manually editing the file is not recommended and may lead to blank pages, especially if there are additional spaces and/or lines after the final php closing tag "?>".
Downloading previous releases of Moodle
It is possible to download previous versions of Moodle that are not found on the Standard Moodle Download page. There are zip and tgz compressed located at http://download.moodle.org/stable[version_number] (see links below).
|2.0 Versions||1.9 Versions||1.8 Versions|
|1.7 Versions||1.6 Versions||1.5 Versions|
|1.4 Versions||1.3 Versions|
You can download previous releases by using wget, lynx or curl with this URL: http://download.moodle.org/stable[version_number].
- For example: to download Moodle version 1.5, use http://download.moodle.org/stable15. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
- Windows Packages: To download other releases not found in Moodle packages for Windows, use this URL:
- Mac Packages: To download other releases not found in Mac pacakges, use either of these URLs (depending on whether you need the Intel or PPC package):
- Using CVS: You can also use CVS to download older releases and incremental releases of the Moodle generic packages, e.g. Moodle 1.5.4 - see the CVS documentation.
How to enable and check PHP error logs
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See PHP error logs.
Email copies are not being sent from my forums
You must set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on.Basically, you need to set up a process to regularly call the script
. Please refer to the cron instructions.
- Try the default settings in Site Administration > Server > Email. This generally works. Except...
- On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
- Make sure that allowuseremailcharset in Administration > Server > Email is set to No. Setting this to Yes can cause a problem in some versions of Moodle.
I can't log in - I just stay stuck on the login screen
This may also apply if you are seeing “Your session has timed out. Please login again” and cannot log in.
The following are possible causes and actions you can take (in no particular order):
- Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
- Sessions may not be configured properly on the server. You can test this by calling the script http://yourserver/moodle/lib/session-test.php.
- If your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
- Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
- Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing Norton firewall products.
- Try deleting the sessions folder in your moodledata directory (anybody currently logged in will be thrown out)
- Try deleting cookies on your computer and/or try another browser or another client computer
- In Site Administration > Server > Session handling, try setting a value for 'Cookie prefix'. You can also do this by setting
$CFG->sessioncookie='something';in config.php. This is especially true if you are using multiple Moodles on the same browser.
- Make sure you have not removed or changed the Password Salt value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This feature was optional since Moodle 1.6 but has been applied by default since 1.9.7. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
- Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
- Check the value of mnet_localhost_id in the mdl_config database table. It's normally 1 but must match the mnet_hostid field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
- You are using the correct username and password, yes?
Make sure the URL in your
$CFG->wwwrootsetting is exactly the same as the one you are actually using to access the site.
Uploaded files give "File not found"
For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.
Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your httpd.conf, or to a .htaccess file in your local directory (see Installing Moodle for more details):
Note, this will ONLY work for Apache versions 2.x.
For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.
IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.
Once you've got URL rewriting working the recommended rewriting rule is:
RewriteRule ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]
In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.
If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.
To use this alternative method, you should change the slasharguments variable. For moodle versions < 1.7, this is located in the Operating System section of Administration > Configuration > Variables. In later versions, this option is located in Site Administration > Server > HTTP. You should now be able to access your uploaded files.
- Using Moodle Troubleshooting Guide - 404 Errors forum discussion.
Why are all my pages blank?
Check the dirroot variable in config.php. You must use complete, absolute pathnames (Note some operating systems use single slashes instead of double slashes shown here)
$CFG->dirroot = "d:\\inetpub\\sites\\www.yoursite.com\\web\\moodle";
Another reason might be that PHP has not been configured to support MySQL. This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see How to enable and check PHP error logs.
To determine if MySQL support is your problem, insert this as the second line in your config.php file
then reload the web page. Examine the output closely to see if MySQL is supported. If not, look for a package you are missing.
Why is a particular page blank or incomplete?
- Check your web server log files!!
- If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on Debugging and check your PHP error logs. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.
- If you are upgrading to a new version of Moodle, check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".
- If you do not see any blocks listed, turn editing on and remove any blocks that you have added to that page and try reloading.
- You may get this error immediately after selecting a language. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle Moodle Requirements page.
- Using Moodle PHP configuration error forum discussion
Installation hangs when setting-up database tables
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.
See Unexpected installation halts for more about solutions that involve:
- Checking for MySQL limits
- Checking the .htaccess files
- Code customizations issues
- Checking memory limit
- Upgrade incrementally
- Fix fopen function
Why can't I upload a new image into my profile?
If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
- The permissions associated with the role you are using are preventing you from changing your profile picture.
- GD is not installed, or is not enabled on your server. Make sure GD has been included in your PHP installation. You can check this by going to Site Administration > Server > PHP info and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
- GD is installed, but is in some way corrupt. For instance, see this discussion on empty lines or white spaces in config files.
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.
If Moodle thinks GD is not installed, then you will need to install the GD library.
- On Unix you may need to re-compile PHP with arguments something like this:
./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd --with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf --enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars --enable-versioning --with-zlib
- On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
- Windows users should see the installation instructions for further help.
3. Remember to restart your webserver (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.
See also: Using Moodle forum discussion Profile pictures for additional information.
Why doesn't my Moodle site display the time and date correctly?
Each language requires a specific language code (called a locale code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.
How do I uninstall Moodle?
Webhost/manual installation: If you have installed Moodle manually or have installed onto a webhost, follow these steps:
- Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
sql>DROP DATABASE moodle;
- In the above example replace 'moodle' with the name of the moodle database you created when installing.
- Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
- Delete the moodle directory itself. This will delete all of the moodle PHP script files.
XAMPP windows installation: If you have installed Moodle on windows through the XAMPP package, follow these steps:
- Open cmd.exe and navigate to this directory within your installation directory:
- Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
mysqladmin.exe -u USERNAME -p drop DATABASE
- Enter your database password at the prompt (the default is "" [blank]).
- Enter "y" to confirm the database drop.
- Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
- Delete the moodle directory itself. This will delete all of the moodle PHP script files.
How do I upgrade Moodle? Do I just overwrite the files?
Do not overwrite files, it may cause strange errors. You should read the Upgrade documentation before proceeding.
I obtain the message "Upgrade already running in this session, please wait!"
Most likely you refreshed the page before the completion message. If you are absolutely sure that there are no upgrade processes active (php and/or mysql), you can click on "!!!" and restart the upgrade.
- Note: If you click on "'!!!" or try to restart the upgrade from another browser, there is a chance that your data in the database could be corrupted. If this happens, you will need to restore the database from sql dump and then restart the upgrade and wait - the process can take several hours on large sites.
Migrating Moodle to a new site or server
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the Moodle Migration page.
Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
- For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
- If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
- Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see masquerading.
Maximum upload file size - how to change it?
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the course administration block.
If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings upload_max_filesize and post_max_size, setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, /etc/init.d/apache2 force-reload. Check your documentation or just reboot the server.
For more help see:
- These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650
How do I install Moodle on Windows Vista?
Moodle claims PHP float handling is not compatible
The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".
This forum thread and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.
You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.
Update: we have a guess that the problem may be the 'precision' setting in your php.ini file. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
to your config.php file, and report your success in MDL-18253.
When upgrading Moodle claims my database is not UTF8 when I'm sure it is
The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.
The database may not have it's character encoding set quite correctly. You can safely try this command on the database
ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.
Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use phpMyAdmin to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).
If your Moodle site is version 1.5 or older then it's telling the truth.
How do I run multiple instances of Moodle without duplicating base code?
What is FreeTDS and how can I use it in my installation?
FreeTDS is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.
How do I install a plugin?
Please see Installing contributed modules or plugins.