Testimonials
What our customers say about Team Password Manager

Troubleshooting Internal Server Error 500 when installing Team Password Manager

Current Team Password Manager version: 7.73.146

The 500 Internal Server Error is general HTTP status code that means something has gone wrong on the web server but the server could not be more specific on what the exact problem is. It is one of the most common errors our users find when installing Team Password Manager.

Since it is a general error there are many factors that can trigger it. In this document we list the most common ones that our support department has found.

If you get this error when excuting index.php/install, please check:

1. That you have the required files and folders for installing and executing Team Password Manager. When decompressing the Team Password Manager zip file you should get the following files and folders. All of them (except the .txt files) are required:

config.php
css (folder)
eula.txt
folder.php
import (folder)
index.php
install.txt
robots.txt
system (folder)
upgrade.txt
wmm (folder)

2. That the files and folders have the appropriate permissions. All the files should be readable by the web server. In Linux, folders should also have the x permission (you can do chmod -R ugo+X * from the program root to set the x permissions where needed). A quick way to test if permissions are producing the Error 500 is to set all the files and folders to 777 permisions and try again.

3. That you have the php-mysqli and mcrypt modules installed. To see if they're installed create a php file on your server (ex: phpinfo.php) with the following command:

<?php phpinfo(); ?>

Open it with your browser and look for the mysqli and mcrypt sections. If you don't find these sections it means that the modules are not installed. If you find the sections they should report that "mysqli support" and "mcrypt" support is "enabled".

Important: after verifying this make sure you delete the phpinfo file. It is not needed for Team Password Manager to run and it's giving away information about your server.

4. That you don't have any .htaccess blocking access or with strange rewrites.


If after checking these steps you still get the Error 500 please contact our support department and we'll try to sort it out together.