WampDeveloper 5 Known Issues and Solutions

v5.3.0.1

Issue: SVG images are not automatically compressed

Status

Fixed in next release.

Effect

While the mod_deflate configuration appears to have the SVG content-type in its compression list, SVG images are reported as not compressed (e.g., when testing in Google Pagespeed).

Cause

The content-type regex match string is incorrect.

Solution

Edit file –
C:\WampDeveloper\Config\Apache\extra\wampd-deflate.conf

Change this line –

FilterProvider COMPRESS DEFLATE "%{CONTENT_TYPE} =~ m#^image/(svg+xml|x-icon)#i"

To this –

FilterProvider COMPRESS DEFLATE "%{CONTENT_TYPE} =~ m#^image/(svg\+xml|x-icon)#i"

You are just adding a “\” in front of the “+” character.

Since the above is a regex, and the “+” is one of regex’s meta/special characters, it needs to be escaped so it’s taken literally.

Save file. Restart Apache. Clear your Browser’s cache.

Issue: Installing web-apps sometimes fails

Status

Fixed in next release.

Effect

After auto installing a webapp via WebApps Tab, either a connection to the webapp’s database is not established, a blank screen is shown, or its files are missing.

Cause

If the webapp’s URL is accessed before the webapp is fully installed, the webapp installation process can fail, as you would be accessing a script that has only partially placed its files and populated its database – which can have unpredictable results.

Solution

Delete the webapp installation, and try again… Except wait until accessing its URL only after the webapp “State” changes from “Installing” to “Installed” (re-size column in WebApps tab to see full text).

Issue: After installing WampDeveloper Apache won’t load PHP, or there are issues with PHP

Status

Fixed in next release.

Effect

After installing WampDeveloper, either:

A) Apache will not start… And returns a message about not being able to find nor load “php5ts.dll”…

Cannot load C:/WampDeveloper/Components/Php/php5ts.dll into server: The specified module could not be found.

B) PHP is not loaded… And phpMyAdmin will not work, etc.

Cause

On installation, PHP-FCGI (php5.dll) has been linked to, but the Apache configuration (Config\Apache\httpd.conf) is including (using) the configuration file for PHP-Regular (php5ts.dll) instead, or vice-versa.

There are 2 possibilities for the cause of this:

This might be happening because httpd.conf was shipped with the configuration for PHP-FCGI un-commented, but the installer is proceeding thinking that PHP-regular is being used (e.g., PHP-FCGI is linked, but httpd.conf is updated to use the configuration for PHP-regular).

This can also happen if you are using anti-virus software such as McAfee, which is preventing process WampDeveloper.exe for modifying httpd.conf, and/or creating NTFS Junction Points (i.e., linking Components\Php to the proper PHP Versions\Php folder). In this case, white-list the WampDeveloper.exe process (or the entire C:\WampDeveloper folder), and then re-link to PHP-regular in Components Tab.

Solution

Re-link to the proper PHP-regular version in Components Tab.

Go into Components Tab, and select –

Channel: Current
Bits: 32
PHP Type: Regular

Then select (check-mark box “use”) the appropriate Apache, PHP, and MySQL versions in their sub-tabs. And click: Switch To Selected Versions.

You can also fix this manually by editing Config\Apache\httpd.conf (and near the bottom of the file) un-commenting “Include …wampd-php5-fcgi.conf” and commenting-out “Include …wampd-php5.conf”.

Issue: After installing Drupal the admin password does not work

Status

Fixed in next release.

This issue might also affects previous versions.

Effect

After installing Drupal via WebApps Tab, the provided password does not work.

Cause

The password field for user “admin” in the newly created drupal database is wiped clean on install due to an issue with the PHP script that generates the hash of the new password.

Solution

Using phpmyadmin, select the drupal database.

1. To clear out all the failed attempts and to unblock the account…

Empty (Truncate) table: flood

2. Set admin’s password to “password”…

Edit table: users

Edit user “admin”, set “pass” field to value:

$S$DAoA1X8jkN5.nv4d.C.E9OqgeQs49ktgbEcPWQjD08hgiHMzX0Io

The above hash is for the string “password”.

3. Log-in with username “admin” and password “password”. Afterwards, you should be able to set another password.

v5.2.0.1

Issue: Switching Channels, and Apache and PHP Versions, sometimes does not work 100%

Status

Fixed in next release.

This issue also affects previous versions.

Effect

When switching between Channels, sometimes the Apache Service is not (re)-installed (the old Service is uninstalled, the new Service is not). Other times it is, but it’s not started (if it was running before).

This mostly happens if Apache and MySQL Services are set on “Startup Type”: “Auto” (instead of “Manual”).

Cause

A. Application was re-linking Structure (version’s folders and files) first, and then uninstalling the older Service – which might have depended on it’s older/native paths.
B. WMI is returning Service StartMode value “Auto”, yet the definition (in API) is labeled as “Automatic”. This caused some issues in the codebase.

Solution

1. Close WampDeveloper.

2. Reboot to clear out any bad DLL loads.

3. Try again… Except next time, before the switch, set Apache and MySQL Services to “Startup Mode”: “Manual”, and also stop them.

v5.1.0.1

Issue: Unassigned IPs and Domain Names are redirected to URL: http://localhost/

Status

Fixed in upcoming release.

Effect

The designed behavior for dealing with requests for unassigned IPs and Domain Names is to default them to the localhost VirtualHost – which acts as the default or fallback website.

Currently, while this is technically working, the localhost VirtualHost ends up redirecting those requests to URL: http://localhost/… Which is a problem for non-local visitors.

That is, a request for http://public.ip.address/ (from internet), http://lan.ip.address/ (within LAN), or http://unassigned.domain.name/ (from internet or LAN) gets picked up by the localhost VirtualHost, which then proceeds to redirect the Browser to URL http://localhost/.

Cause

The HTTP and SSL localhost VirtualHosts contain general redirect rules for everything except http://127.*.*.*/ and http://[::1]/.

Solution

Edit files:
C:\WampDeveloper\Config\Apache\extra\wampd-localhost.http.vh.conf
C:\WampDeveloper\Config\Apache\extra\wampd-localhost.ssl.vh.conf

Comment out, or remove, the relevant Redirect rules:

# Do NOT redirect on http://127.0.0.1/ (nor 127 /8 address block) or ::1...
RewriteCond %{HTTP_HOST} ^127\. [OR]
RewriteCond %{HTTP_HOST} ^\[::1\]
RewriteRule .* - [E=no_redirect:1]

# Redirect all ServerAlias to ServerName (and preserve port)
RewriteCond %{ENV:no_redirect} !^1$
RewriteCond %{HTTP_HOST} !^localhost(:[0-9]*)?$ [NC]
RewriteCond %{HTTP_HOST} (:[0-9]*)?$ [NC]
RewriteRule ^/*(.*)$ http://localhost%1/$1 [R=301,L]

* The SSL VH also contains redirect rules for ServerStatus, ServerInfo, and *.apache.local addresses. DO NOT remove these rules.

Save files. Restart Apache. Also clear your Browser cache and restart (close + open) it.

Issue: Switching to Apache 2.0 (PHP 4.4) does not work (the Apache Service is not installed)

Status

Fixed in upcoming release.

Effect

After switching down to the Legacy Channel (Apache 2.0, PHP 4.4, MySQL 5.1), the Apache Service is either listed as not switched, or as not installed (after the WampDeveloper app is close/opened again).

Cause

A IPv6 syntax issue in Apache’s configuration files is preventing Apache 2.0 from installing and starting.

Specifically the issue is with lines “Allow from 127.0.0.0/8 ::1“, used through the *.conf files under folder Config\Apache\ (and sub-folders).

This problem can also manifest with some Apache 2.2 builds, as the official apache.org builds did not enable IPv6 support in until Apache 2.4.

Solution

Using an editor such as Notepad++…

A) Replace all occurrences of:

Allow from 127.0.0.0/8 ::1

With:

<IfVersion >= 2.4>
Allow from 127.0.0.0/8 ::1
</IfVersion>
<IfVersion < 2.4>
Allow from 127.0.0.0/8
</IfVersion>

In this file list:

C:\WampDeveloper\Config\Apache\extra\httpd-info.conf (2 hits)
    Line 24:    Allow from 127.0.0.0/8 ::1
    Line 50:    Allow from 127.0.0.0/8 ::1

C:\WampDeveloper\Config\Apache\extra\wampd-httpd.host.http.vh.conf (1 hit)
    Line 31:    Allow from 127.0.0.0/8 ::1

C:\WampDeveloper\Config\Apache\extra\wampd-httpd.host.ssl.vh.conf (1 hit)
    Line 39:    Allow from 127.0.0.0/8 ::1

C:\WampDeveloper\Config\Apache\extra\wampd-info.host.conf (1 hit)
    Line 41:    Allow from 127.0.0.0/8 ::1

C:\WampDeveloper\Config\Apache\extra\wampd-status.host.conf (1 hit)
    Line 45:    Allow from 127.0.0.0/8 ::1

B) Replace all occurrences of:

Allow from 127.0.0.0/8 ::1

With:

Allow from 127.0.0.0/8

In this file:

C:\WampDeveloper\Config\Apache\extra\wampd-phpmyadmin.conf (4 hits)
    Line 83:    Allow from 127.0.0.0/8 ::1
    Line 96:    Allow from 127.0.0.0/8 ::1

* Ignore the commented out (#) lines.

C) Also edit file C:\WampDeveloper\Tools\phpMyAdmin.php4\.htaccess to replace “Allow from 127.0.0.0/8 ::1″ with “Allow from 127.0.0.0/8″.

*Versions of Apache below 2.0.65 (WampDeveloper only provides v2.0.65), do not support the “IfVersion” directive. If you are using a custom version of Apache 2.0, you’ll instead just need to remove the ” ::1″ part from each line.

Issue: Mediawiki installation into root (/) of a website produces Browser error “website is not available”

Status

Fixed in upcoming release.

Effect

When Mediawiki is installed into the root of a website (into ‘\webroot’), as opposed to some sub-folder like ‘\webroot\wiki’, Browser is redirected to http://index.php/… (no domain-name in URL) and produces a general website not available or reachable error.

Cause

The webapp package uses a relative path in Mediawiki’s configuration file that is misinterpreted as a full path.

Solution

After Mediawiki installation, edit file (via Notepad) –
C:\WampDeveloper\Websites\primary.domain.name\webroot\LocalSettings.php

Change this:
$wgScriptPath = "/";

To this:
$wgScriptPath = "";

Save file. Also clear your Browser cache and restart (close + open) it.

Issue: New websites’ VirtualHost files are missing PHP error_log setup for Legacy Channel: Apache 2.0 + PHP 4.4

Status

Fixed in upcoming release.

Effect

When using Legacy Channel for Apache 2.0, and PHP 4.4, PHP’s error_log is not set per website (the global PHP error_log defined in php.ini is used instead).

Cause

The VirtualHost templates seems to be missing this part.

Solution

Edit files (via Notepad) –
C:\WampDeveloper\Resources\default.http.vh.conf
C:\WampDeveloper\Resources\default.ssl.vh.conf

Right after this code:

<IfModule mod_php5.c>
  php_value error_log "{{logsAlt}}/Websites/{{websiteName}}/http.phplog.txt"
  # php_admin_flag {{opcodeString}} Off
</IfModule>

Add this:

# Apache 2.0 / PHP 4.4
<IfModule sapi_apache2.c>
  php_value error_log "{{logsAlt}}/Websites/{{websiteName}}/http.phplog.txt"
  # php_admin_flag apc.enabled Off
</IfModule>

* For the SSL VirtualHost, instead of string http.phplog.txt, using string ssl.phplog.txt.

Save files. Also edit any previously created websites with real values (don’t use the above template codes).

v5.0.2.1

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

Status

Fixed in upcoming release.

Effect

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:
http://127.0.0.1/phpmyadmin

Cause

  • 1) “localhost” is getting resolved to IPv6 “::1″ instead of IPv4 “127.0.0.1” (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

Solution

Edit file (via Notepad):
C:\WampDeveloper\Tools\phpMyAdmin\config.inc.php

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:
    127.0.0.1 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:
Tools\phpmyadmin.php4\config.inc.php
Tools\phpmyadmin.php4\.htaccess
Config\Apache\extra\wampd-phpmyadmin.conf

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

Status

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

Effect

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.

Cause

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.

Solution

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:

127.0.0.1 localhost

127.0.0.1 ServerStatus stat.apache.local
127.0.0.1 ServerInfo info.apache.local
127.0.0.1 ServerHost host.apache.local

127.0.0.1 DefaultWebsite website

127.0.0.1 www.example.com example.com

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

Status

Fixed in upcoming release.

Effect

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.ini)

zend_extension="C:\WampDeveloper\Components\Php\ext\php_opcache.dll"
opcache.enable=1

(C:\WampDeveloper\Config\Apache\extra\wampd-phpmyadmin.conf)
(C:\WampDeveloper\Vhosts\localhost.http.vh.conf)

php_admin_flag opcache.enable Off

URL:
http://localhost/phpmyadmin

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

(php.ini)

opcache.blacklist_filename="C:\WampDeveloper\Config\Php\opcache.blacklist.txt"

(C:\WampDeveloper\Config\Php\opcache.blacklist.txt)

C:\WampDeveloper\Tools\phpMyAdmin\
C:\WampDeveloper\Tools\phpMyAdmin.php4\

Cause

PHP, OPcache Extension, and/or Apache bug.

Solution

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 –
C:\WampDeveloper\Config\Apache\extra\wampd-phpmyadmin.conf

Remove line –

php_admin_flag opcache.enable Off

Also do the same in these files, if they exist –
C:\WampDeveloper\Vhosts\localhost.http.vh.conf
C:\WampDeveloper\Vhosts\localhost.ssl.vh.conf

And perform the same edit in all your websites’ VirtualHost files –
C:\WampDeveloper\Vhosts\primary.domain.name.http.vh.conf
C:\WampDeveloper\Vhosts\primary.domain.name.ssl.vh.conf

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)
phpMyAdmin 4.1.8.0

Issue: Strange .htaccess RewriteRule Issues

Status

Fixed in upcoming version.

Effect

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.

Cause

‘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]

Solution

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]

2 thoughts on “WampDeveloper 5 Known Issues and Solutions”

  1. Just installed Wampdeveloper and clicked to “Continue Trial” and it went from 14 days left (never gave me 30 days) to -6 days and said either Purchase or Uninstall. So I uninstalled and all it did was remove icon from desktop. Couldn’t uninstall thru Control Panel (wasn’t listed) but pgm is still installed. I opened it up again (after doing some research) to uninstall but only option was to finish installation or exit. How do I get this uninstalled so I can move on based on this situation?

    Thanks.

    1. Hi Gary,

      If you’d like to try again, I went into the trial database and manually updated your trial with the proper 30 day value…

      But before you do that:
      Run “regedit”.
      Go to: HKEY_LOCAL_MACHINE\SOFTWARE\WampDeveloper\v5\
      And delete Value: RegData

      Or if you’d still like to finish the uninstall, the uninstall process did everything aside from removing folder C:\WampDeveloper… Delete it and you’ll be done.

      Just installed Wampdeveloper and clicked to “Continue Trial” and it went from 14 days left (never gave me 30 days) to -6 days

      I’ve checked the logs, and it looks like your system’s identifiers matches someone else’s that did the trial on: 2015-01-28…

      If you are installing in a VPS, cloud hosted VM (like in AWS EC2), or on a regular PC but in something like VMWare, this problem can come up – as sometimes the trial system picks up system identifiers that matches a previous trial (because of the homogeneous environment).

      Also, on a rare occasion, two regular Windows installs might match due to some reason unknown.

      The upcoming release should improve this situation.

      So I uninstalled and all it did was remove icon from desktop.

      The uninstall process does everything except for deleting folder:
      C:\WampDeveloper\

      It leaves the folder because it can still contain websites and databases that the user might want to keep or migrate.

      I opened it up again (after doing some research) to uninstall but only option was to finish installation or exit.

      Since WD is now in an uninstalled state, when you run it, it will bring up the installation process.

      How do I get this uninstalled so I can move on based on this situation?

      Once you delete the folder, it’s gone (except for the registry key that remains).

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>