Tag Archives: FAQ

Wamp-Developer Server FAQ

Using Custom Apache PHP MySQL Versions Under WampDeveloper

WampDeveloper Pro can use (just about) any version of Apache, PHP, and MySQL that is supplied… It does not matter if those versions are provided through us, or from somewhere else.

WampDeveloper Pro will happily use any custom (user supplied) 32 and 64 bit versions of Apache, PHP, and MySQL as long as:

  • They are placed into the proper \WampDeveloper\Versions\<component-name>\<version-format>\ folder.
  • Any extra Apache and PHP modules/extensions *that are used* (ex: XDebug loaded in php.ini) are also included.

Howto Use 64bit Apache 2.4 + PHP 5.5 + MySQL 5.6 Versions

Apache 2.4 and PHP 5.5 64 bit VC11 (VS.NET 2012) builds can be downloaded from here:

Unpack and place Apache as:

Unpack and place PHP as (depending if it’s PHP-regular or PHP-FCGI):


All extra Apache modules will need to be of build type: VC11, 64bit

The following Apache modules will need to be inside the version’s \modules folder:

  • mod_fcgid – only if you are using PHP-FCGI.
  • mod_logio + mod_ssl – are almost always already present/provided in the package.
  • mod_security – only if you are using it / have it enabled (most don’t).

Also, you can safely delete these Apache version’s folders as they will be re-created by WampDeveloper Pro:
cgi-bin, conf, htdocs, logs


All extra PHP extensions will need to be of build type: VC11, 64bit

PHP extensions also have the TS/NTS specification:

  • For PHP-regular, extensions are “TS” (Thread Safe)
  • For PHP-FCGI, extensions are “NTS” (Not Thread Safe)

The following PHP extensions will need to be inside the version’s \ext folder, at least if you are using them (have them loaded in php.ini):
php_xdebug.dll, ioncube_loader.dll, php_memcache.dll, php_mongo.dll, php_varnish.dll, php_xcache.dll, php_imagick\php_imagick.dll

The extensions will need to be properly re-named from their default file-names to the above names.

The extensions will need to be downloaded for build: PHP 5.5, VC11, 64bit, TS and/or NTS (depending on if it’s for PHP or PHP-FCGI).

Most PHP extensions can be downloaded from here:

Also, you can safely delete the PHP version’s php.ini file as it will be re-created by WampDeveloper Pro.


Download the “zip archive” of MySQL 5.6 64 bit from here:

Unpack and place it as:

Delete it’s \data folder.

VC++ Runtime DLLs

Since we are using VS.NET 2012 builds of Apache and PHP, the proper Runtime DLLs that they depend on might not be present on your OS…


The VC++ 2012 Runtime (x64) will need to be installed on your OS:

Running Multiple Versions of PHP 5 Under Apache Side-by-Side

This guide will show you how to set up and run PHP 5.5 and 5.3 at the same time under Apache (but can also be used to set up and run any two, or more, different PHP 5 versions side-by-side).

1. Make sure WampDeveloper is currently using PHP 5.5 FCGI (check Components Tab). This will load the default/global PHP-FCGI configuration, which we will later override under a website or directory.

You’ll also need the PHP 5.3 FCGI version already downloaded and present on the system.

We’ll use PHP version 5.3.28 in this example.

2. Create a separate PHP configuration file for the specific PHP 5.3 version, php-…

Make a copy of file:

Rename the copy:

Edit the new file and replace all occurrences of the global PHP path with the specific version’s path:









3. Edit the website’s HTTP and SSL VirtualHost files and insert into the “webroot” Directory block the overriding PHP-FCGI configuration:

<IfModule fcgid_module>
	FcgidWrapper "C:/WampDeveloper/Versions/Php/php- -c C:/WampDeveloper/Config/Php/php-" .php virtual
	FcgidWrapper "C:/WampDeveloper/Versions/Php/php- -c C:/WampDeveloper/Config/Php/php-" .php4 virtual
	FcgidWrapper "C:/WampDeveloper/Versions/Php/php- -c C:/WampDeveloper/Config/Php/php-" .php5 virtual

This will set up the entire website to use the different PHP version. If instead you just want a specific directory using a different PHP version… Instead of using the “webroot” Directory block, create your own block next to it, and place the above configuration inside.

4. Save edited files. Restart Apache.

WampDeveloper 5 Known Issues and Solutions


Issue: Access of \phpmyadmin is denied to root user (and others)


Fixed in upcoming release.


When accessing phpmyadmin by using the “phpmyadmin” button in WampDeveloper’s System Tab, or using this URL: http://localhost/phpmyadmin, user ‘root’ is not able to login.

Opposite to the above, this URL does work:


  • 1) “localhost” is getting resolved to IPv6 “::1″ instead of IPv4 “″ (due to the Windows Hosts file entries).
  • 2) phpmyadmin’s configuration file config.inc.php is missing an access entry for the corresponding MySQL “root@::1″ account.

It’s possible that the installer was not able to update the Windows Hosts file, and/or Windows Defender (or some other security app) was able to undo the changes.

And if IPv6 is enabled on your system, and “localhost” get’s resolved to the IPv6 loopback address “::1″, user “root” will not be able to login via URL: http://localhost/phpmyadmin


Edit file (via Notepad):

Add into the “AllowDeny” rules-array this line:

'allow root from ::1',

Also edit the Windows Hosts file (LocalDNS Tab, button: Hosts File) -

  • Remove line:
    ::1 localhost
  • Make sure this line is present: localhost

Save files. Then close and open your Browser, and you should now be able to login to phpmyadmin with user root.

* If you still have issues after this, try: 1) clearing the Browser’s cache, 2) stopping Apache and MySQL and clearing out the C:\WampDeveloper\Temp\ folder of all files (but don’t delete the sub-folders), and 3) rebooting/restarting the system.

Exclude the Windows Hosts file in Windows Defender

*If you are also going to use the provided older phpmyadmin version that’s compatible with the Legacy Apache 2.0 and PHP 4.4 channel, it’s not possible to apply part of this fix due to Apache lacking IPv6 support and the IPv6 syntax (“::1″) being unknown to Apache and/or phpmyadmin. So only the Host file edit is needed. Just as a note, if it was possible to use IPv6 on that channel, these files would need to be updated:

Issue: LocalDNS does not work, and/or Hosts file gets overwritten


Reported. Could depend on OS, antivirus software, and environment.


a) On WampDeveloper installation, the entire Windows Hosts file is emptied, or only contains 1 or 2 entries.

b) On website creation or LocalDNS changes, domain-names do not work.


Antivirus software such as BitDefender (and Windows Defender) block WampDeveloper from making edits to the Hosts file, and/or attempt to restore this file when changes are detected.


Exclude the process C:\WampDeveloper\wampdeveloper.exe and the folder C:\WampDeveloper\ in the anti-virus software’s settings.

Then open Windows Hosts file (LocalDNS Tab, click button: Hosts file), and add at least these entries in: localhost ServerStatus stat.apache.local ServerInfo info.apache.local ServerHost host.apache.local DefaultWebsite website www.example.com example.com

Issue: PHP’s OPcache crashes Apache on some phpMyAdmin URLs


Fixed in upcoming release.


Having PHP’s OPcache extension globally enabled AND having “php_admin_flag opcache.enable Off” in either the website’s VirtualHost file or in the configuration of Config\extra\wampd-phpmyadmin.conf will cause Apache to crash after several \phpmyadmin tabs are clicked in succession.




php_admin_flag opcache.enable Off



It also does not matter if the phpmyadmin file paths are excluded via OPcache’s blacklist file:






PHP, OPcache Extension, and/or Apache bug.


Comment out and do not use “php_admin_flag opcache.enable Off” at all, not in websites’ VirtualHost files nor in any Apache configuration files.

Edit file -

Remove line -

php_admin_flag opcache.enable Off

Also do the same in these files, if they exist -

And perform the same edit in all your websites’ VirtualHost files -

If needed, exclude phpmyadmin (and other) file paths via OPcache’s blacklist… Or don’t disable the caching of phpmyadmin if no opcode cache issues are present with used PHP, OPcache Extension, and phpmyadmin versions.

WAMP Component Versions

Apache 2.4.9
PHP 5.5.11 (via mod_php)

Issue: Strange .htaccess RewriteRule Issues


Fixed in upcoming version.


Some mod_rewrite RewriteCond and RewriteRule lines in a website’s .htaccess file could interact with the VirtualHost file’s “Domain Aliases to Primary Domain Name” redirect ruleset, with faulty results.


‘Domain Aliases to Primary Domain Name’ redirect ruleset does not terminate after the redirect sequence…

# Redirect all ServerAlias to ServerName (and preserve port)
RewriteCond %{HTTP_HOST} !^www\.example\.com(:[0-9]*)?$ [NC]
RewriteCond %{HTTP_HOST} (:[0-9]*)?$ [NC]
RewriteRule ^/*(.*)$ https://www.example.com%1/$1 [R=301,NC]


Update websites’ HTTP and SSL VirtualHost files, and the template VirtualHost files (C:\WampDeveloper\Resources\default.http.vh.conf, default.ssl.vh.conf).

Changing this line:
RewriteRule ^/*(.*)$ https://www.example.com%1/$1 [R=301,NC]

To this:
RewriteRule ^/*(.*)$ https://www.example.com%1/$1 [R=301,L]

Howto Start MongoDB and Enable php_mongo in WAMP

Start MongoDB

WampDeveloper comes with MongoDB located in folder:

MongoDB can either be started:

A) Manually from the command-line:

mongod --config C:\WampDeveloper\Tools\mongodb\mongodb.conf

B) Or by double-clicking entry “MongoDB” in WampDeveloper’s Applications Tab, in which case, WampDeveloper will run file:

The MongoDB server will run as long as the command-line window is open.

Enable php_mongo

To connect and talk to the MongoDB server via PHP code, PHP extension php_mongo must be loaded.

1. Edit file:

2. Uncomment section:


(* uncomment by removing “;”, section is located near end of file)

3. Save file and restart Apache.

Connecting To and Using MongoDB

A REST interface to some MongoDB stats and information is provided on URL:

Example PHP code to test the operations of the MongoDB server is provided here:

Howto Start Memcached and Enable php_memcache in WAMP

Start Memcached

WampDeveloper comes with memcached located in folder:

Memcached can either be started:

A) Manually from the command-line:

memcached.exe -l -p 11211 -m 128 -t 4

B) Or by double-clicking entry “memcached” in WampDeveloper’s Applications Tab, in which case, WampDeveloper will run file:

The memcached server will run as long as the command-line window is open. The “-m” option specifies the size (in MB) of memory to use.

Enable php_memcache

To connect and talk to the memcached server via PHP code, PHP extension php_memcache must be loaded.

1. Edit file:

2. Uncomment section:


(* uncomment by removing “;”, section is located near end of file)

3. Save file and restart Apache.

Connecting To and Using memcached

Example PHP code to test the operation of the memcached server…


ini_set('display_errors', 1);

$memcache = memcache_connect('localhost', 11211);

// note - memcache_connect errors must be suppressed (@) for this code to be reached
if ($memcache === false)
	echo "Connection to memcached failed.";

// test string
$key_string = "string to store in memcached";

// test number
$key_number = 123;

// test array
$key_array  = Array(123, 345, 567);

// test object
$key_object = new StdClass;
$key_object->str_attr = 'test';
$key_object->int_attr = 123;

// store the values into memcached
$memcache->set("str_key", $key_string);
$memcache->set("num_key", $key_number);
$memcache->set("arr_key", $key_array);
$memcache->set("obj_key", $key_object);

// retrieve the values from memcached


Browser’s “Could Not Find” or “Could Not Display” Webpage Message

Oops! Google Chrome could not find domain-name

Server not found. Firefox can’t find the server at domain-name.

Internet Explorer cannot display the webpage

If, from the same system that the WAMP server is running on, your Browser (Chrome, Firefox, IE) is not able to locate your local website, the above messages will be displayed.

This happens when:

A) The Windows Hosts file does not have an entry resolving the website’s domain-name to the “loopback” address (

B) The Browser is still using its previous bad DNS resolve cache for this domain-name.

To fix this:

1. In WampDeveloper’s LocalDNS Tab, make sure this website is check-marked. If the check-mark disappears, then LocalDNS is not able to make changes to the Windows Hosts file because this file is being locked by another application.

2. Then click the Windows Hosts file button to open the file.

Make sure something similar to this line is present in the file: website.domain.name website.domain.alias1 website.domain.alias2

And that no other lines have your website.domain.name in them.

Save file if changes are made.

3. After making these changes, close your Browser so the older DNS caches are cleared.

*To unlock the Windows Hosts file see this howto:

*WampDeveloper’s LocalDNS works by resolving the domain-name to the local IP address via the Hosts file, so your local Browser (Chrome, Firefox, IE) knows where to find that website.

*Windows 8 users, see section “Enable IE Intranet Browsing” here: http://www.devside.net/wamp-server/installing-wamp-on-windows-8

Howto Switch WampDeveloper’s Apache PHP MySQL Branches

WampDeveloper provides 3 Apache, PHP, and MySQL channels:

  • Current: Apache 2.4, PHP 5.5, MySQL 5.6
  • Stable: Apache 2.2, PHP 5.3, MySQL 5.5
  • Legacy: Apache 2.0, PHP 4.4, MySQL 5.1

The WAMP server can be switched to use any channel at any time.

For example:

To switch to using WampDeveloper’s “Stable” channel, which is: Apache 2.2, PHP 5.3, and MySQL 5.5…

1. In WampDeveloper’s Components Tab, click the download links to the latest provided releases of Apache 2.2, PHP 5.3 (regular, not FCGI), and MySQL 5.5 – that are not on the system already.

2. Once downloaded, extract each into the appropriate Versions folder:

Apache versions are maintained in: C:\WampDeveloper\Versions\Apache\
PHP versions are maintained in: C:\WampDeveloper\Versions\Php\
MySQL versions are maintained in: C:\WampDeveloper\Versions\Mysql\

See this howto to make sure each packaged version is correctly extracted and placed:

3. After these versions are on system, close WampDeveloper and open it again to make sure it re-reads everything (*usually not necessary).

4. Select to use the new Apache, PHP, and MySQL versions:

In WampDeveloper’s Components Tab, in the top right corner, there is a group named “Select Subscription”.

Click on its “Channel” dropdown box, it will list items: Current, Stable, Legacy.

Select “Stable”, and all the Apache, MySQL, PHP branches that are on system in that channel will become select-able via their check-boxes.

Check-mark the “Use” box on each of the latest versions in that channel (ex: Apache 2.2.27 + MySQL 5.5.36 + PHP 5.3.29).

Then click: Update To Selected

* When switching to another Channel, you have to switch all 3 components at the same time: Apache, MySQL, PHP. You cannot switch one at a time.

* Channel “Current” will only work for OSs above XP and Server 2003.

* If you are using PHP-FCGI, using dropdown box “PHP Type”, switch selection from Regular to FCGI.

WAMP’s “Internal Server Error” Message

When Apache or PHP encounter a problem, sometimes this message is displayed…

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at admin@httpd.host to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Apache/2.4.9 (Win32) PHP/5.5.11 Server Port 80

This error is usually 99% of the time a result of an .htaccess file problem.

Check the specific website’s .htaccess file to make sure it’s not using old or incorrect paths and URLs, RewriteRules, nor a bad RewriteBase /path (try commenting it out with a #).

Also, a much more informative/helpful error message will be logged in the website’s HTTP and PHP error logs…

If you select this website in WampDeveloper’s Websites Tab, and click the (“Logs HTTP” group) ErrorLog and PhpLog buttons, the end of the files will tell what the real issue is. It might be something really easy to fix/correct.

If nothing relevant is shown, check the general Apache and PHP error logs files (in WampDeveloper’s Reliability Tab).

Moving Websites and Databases Between 2 WAMP Installs

This assumes you have the same WampDeveloper versions (ex: WampDeveloper 5.0) installed on each system, running the same MySQL branch (ex: MySQL 5.6), and that each WampDeveloper instance is installed on the same path (ex: C:\WampDeveloper).

First, make sure the receiving WampDeveloper installation has the same websites already created via the Websites Tab – so all the VirtualHosts, website folders, and other configuration files exist.

Then stop the Apache and MySQL Services on both systems.

Transferring Websites

Transfer (zip up and copy) to the other system the Websites folder. Select to overwrite everything, if prompted.

As an alternative, you can instead only move a specific website by transferring sub-folder:

Transfer Database

Delete the other system’s Database folder. Replace it completely (replace it, don’t copy-over to overwrite files).

MySQL Issues

If MySQL does not start/run after the \Database folder is replaced, and both machines are using the same MySQL version…

It’s possible that your ZIP program, FTP program, etc, (whatever you are using to package + transfer the files), or its options, does not preserve this NTFS Junction-Point folder link:
Database\mysql-data –> Database\mysql-data-56

You can re-create it (after transferring the \Database folder) by:

1. Deleting folder: Database\mysql-data

2. Opening the command-line w/administrative-permissions (System Tab button) and executing this command (*all on one line):
mklink /j C:\WampDeveloper\Database\mysql-data C:\WampDeveloper\Database\mysql-data-56

Note that the above example is for WampDeveloper v5.0 using MySQL 5.6.
For MySQL 5.5, the folder is: Database\mysql-data-55
For MySQL 5.1, the folder is: Database\mysql-data-51

And under WampDeveloper v4.x the Database folder is “as-is” (it does not have specific version sub-folders, nor NTFS Junction-Point links).

If this is not the issue, open this log file to see MySQL’s error messages:

VirtualHosts and other Website Specific Configuration Files

If you’ve made custom changes to the websites’ VirtualHost files, they exist in this folder and can be transferred:


If you’ve made custom changes to the websites’ AWStats files, they exist in this folder and can be transferred:


Custom DocumentRoot Locations

WampDeveloper expects all websites to be contained under folder C:\WampDeveloper\Websites\ (and it’s best to leave this as-is), but you can work around this by using NTFS “Junction Points” to make a link between an outside folder and either the website’s entire containing folder or the website’s \webroot (DocumentRoot) folder.

First, create a website via WampDeveloper, it will create a website DocumentRoot folder such as:

Then create an NTFS “Junction Point” from the website’s webroot folder to the real location…

1. Delete (or move to new location) the website’s existing DocumentRoot folder:

2. Then from the command line (WampDeveloper’s System Tab, Command Line button) execute (all on one line):
mklink /j C:\WampDeveloper\Websites\www.example.com\webroot C:\Users\YourName\Documents\Web\ProjectName\WebsiteRoot

*Note that C:\Users\YourName\Documents\Web\ProjectName\WebsiteRoot has to already exist.

This way you’ll have your real C:\Users\YourName\Documents\Web\ProjectName\WebsiteRoot folder (where the files reside) and a link to that folder from C:\WampDeveloper\Websites\www.example.com\webroot (which is what WampDeveloper will use).

Notes -

“Junction Points” only work between local drives of the system and OS (between local volumes), and will not link to networked drives or remote shares.

It is also not usually possible to directly link the folders of websites, nor the database folder, to a NAS device.

To use network shares, you would need to change Apache’s account from “LocalSystem” to an account that has network share access. Under Windows, while “LocalSystem” can access TCP/IP, it does not have permissions to access network shares.

Non-local file system access will significantly slow down Apache.