WampServer

Hello,

We have this issue that is consistently happening on the front-facing webserver but does not work when (even the same VM image) is the intranet. We tried googling and searching this forum but the only mention of this symptom ("new PHP version not appearing in the version menu to switch to") does not seem to be be a very popular problem. We'd appreciate any help you guys can give us.

The 13 questions From the FAQ:
-----------------------------
Windows version used: Windows Server 2016 Datacenter (64bit)
Version WampServer: 3.1.9 (64bit)
Apache Version: 2.4.41
PHP Version: 7.3.8 (currently running - trying to upgrade to 7.3.10)
MySQL Version: --none-- (it's disabled in the WampServer options "Allow MySQL"
MariaDB Version: --none-- (same as above)
Colour of WampServer Icon: Green

Windows Event:
We've looked at the the windows event viewer. Nothing relevant there.
Active lines in hosts:
127.0.0.1 localhost
::1 localhost
<internalIP> <domain>.<tld>
Do you have access to localhost (Homepage WampServer)?
Yes
If so, is there an error message at the bottom of the page?
Yes "Port:443 used for the VirtualHost is not an Apache Listen port". Please note, the website is running in HTTPS exclusively with an EV SSL certificate that has been validated with 3 different external tools and a separate security team.
Do you have access to phpMyAdmin?
No, MySQL is disabled see above.
If you use an Antivirus and / or Firewall, please include the names of these:
Checkpoint (not running on this server specifically, it's upstream)
What is the full path to the installation of WampServer (eg D:\wamp\):
c:\wamp64\
If you have one or more Virtual Hosts defined, please show their definition(s):
[This information is redacted for security purposes]

<VirtualHost *:80>
ServerName localhost
ServerAlias localhost
DocumentRoot "${INSTALL_DIR}/www"
<Directory "${INSTALL_DIR}/www/">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require local
</Directory>
</VirtualHost>

<VirtualHost *:443>
SSLEngine on
SSLCertificateFile <file>
SSLCertificateKeyFile <keyfile>
SSLCertificateChainFile <chainfile>
SSLOpenSSLConfCmd Protocal "-ALL, TSLv1.2"
<IfModule mod_headers.c>
Header always set X-XSS-Protection "1; mode=block" early
Header unset X-XSS-Protection
Header always set X-Content-Type-Options "nosniff" early
Header unset X-Content-Type-Options
Header always set Strict-Transport-Security "max-age=15768000; includeSubDomains; preload"
Header always set X-Frame-Options SAMEORIGIN early
Header unset X-Frame-Options
</IfModule>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{REQUEST_METHOD} ^(TRACE|TRACK)
RewriteRule .* - [F]
</IfModule>
ServerName <domain>.<tld>
ServerAlias www.<domain>.<tld>
DocumentRoot "c:/wamp64/www/<folder>"
<Directory "c:/wamp64/www/<folder>/">
Options -Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require all granted
</Directory>
</VirtualHost>

Description of Issue:
---------------------
[*] Install the PHP Addon (in this case 7.3.10 but this used to happen in 7.3.8 too). No errors.
[*] The folder is correctly created in c:\wamp64\bin\php\x
[*] The php.ini, phpForApache.ini and wampserver.conf exist in the new folder.
[*] The new version does NOT appear in Left Click > PHP > Versions menu.

Things we've tried:
-------------------
[*] Stopping the services before installation does not fix it.
[*] Exiting WampServer before installation does not fix it.
[*] Restarting Windows before installation does not fix it.
[*] Restarting Windows after installation does not fix it.
[*] Installing another PHP Addon before this one does not fix it.
[*] All VCRedist packages are installed (32 and 64 bit).
[*] There's NO reference to the PHP version in the Windows PATH environment.

The ONLY thing that fixed it was: take the machine out of the DMZ and into the intranet, install PHP addon and change version then put it back into the DMZ. That's how version 7.3.8 was last installed back in August. As you can imagine this is not a reasonable procedure to do on a production server.

On our staging and development servers (both are inside the intranet only) this problem does not occur, new versions ALWAYS show up in the Version menu, regardless of whether we take the (wamp)server offline. In fact it was quite the surprise to us that after all the tests we ran in the staging server we still had issues in the production server.

If you guys have any things we can try that'd be great! Thanks in advance!

Hi,

> Windows Server 2016 Datacenter (64bit)
I don't have this system, but all addons installations are tested on Windows 7 Pro 64 bit and Windows 10 pro 64 bit, both always up to date with the latest Microsoft updates and VC++ packages.

Under Windows 10, Wampserver 3.2.0(*) 64 bits, without database manager, i.e. like you with MySQL and MariaDB disabled.
Wampserver runs with PHP 7.3.9 and the PHP 7.3.10 addon is not installed.

Download [wampserver.aviatechno.net]
Launch the installation of the addon as an administrator, i. e. right-click on the exe file and then Launch as an administrator.
Launch Wampserver64, wait for the green icon and then :
Left-click -> PHP -> 7.3.10
version 7.3.10 appears in the menu and you can switch to version 7.3.10 without any problem.


What determines, for the PHP script for detecting PHP versions, the presence of a version is the presence of a wampserver.conf file in the php folder, for example :

e:\wamp64\bin\php\php7.3.10\wampserver.conf

Have you installed the addon "as an administrator"?
Do you have write and read permissions on the php 7.3.10 folder?

> If so, is there an error message at the bottom of the page?
> Yes "Port:443 used for the VirtualHost is not an Apache Listen port".
I would say that this message is "normal".
I wouldn't teach you that Wampserver is primarily intended for neophytes and that it includes some tools for them such as creating or adding VirtualHost.
For wampserver and therefore neophytes, the file httpd-vhosts.conf is reserved for VirtualHost on port 80 or on ports declared as additional ListenPorts in Wampserver tools.
For SSL and therefore port 443, it is preferable to make the VirualHost declarations in the file
e:\wamp64\bin\apache\apache2.4.41\conf\extra\httpd-ssl.conf
However, if you do not mind this message in the Localhost page, you can stay as is.

It is the same process to switch Apache version as to switch PHP version and you have switch your Apache version.

(*)Sorry, I no longer have a 3.1.9 installation, I'm in preparation for Wampserver 3.2.0 to, among other things, support PHP 7.4.0

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons



Edited 1 time(s). Last edit at 09/30/2019 09:10PM by Otomatic.

Hello, thanks for your reply. Since we don't have remote access to the production server we could only try this yesterday. we tried your suggestions but still the problem remains. Let me address your points one by one:

> Download [wampserver.aviatechno.net]
> Launch the installation of the addon as an administrator, i. e. right-click on the exe file and then Launch as an administrator.
> Launch Wampserver64, wait for the green icon and then :
> Left-click -> PHP -> 7.3.10
> version 7.3.10 appears in the menu and you can switch to version 7.3.10 without any problem.

we've tried downloading the package again and launching it as administrator. WampServer shuts down all services, the PHP folder is correctly created (with wampserver.conf, etc.). We restart WampServer, Apache comes back up and the new PHP version does not appear in the Version menu for selection.

> Have you installed the addon "as an administrator"?

We did not in the past but did so yesterday with no change.

> Do you have write and read permissions on the php 7.3.10 folder?

Yes. The folder is correctly created by the addon installer. We've compared all Windows permissions between both php7.3.8 and php7.3.10 folders and they are the same.

> It is the same process to switch Apache version as to switch PHP version and you have switch your Apache version.

Yes, and the Apache addon works correctly and new versions show up in the menu for selection. It's only the PHP addon that does not. (This server does not have MySQL/MariaDB so we can't say if it also happens with those). Btw, we also tried uninstalling WampServer completely, installing 3.1.9 from scratch and performing the php 3.7.10 upgrade, same problem.

Just to be clear, we don't think this is a problem with php7.3.10 specifically, back in August we also had this problem when upgrading to php7.3.8 and, like I mentioned, we had to take the server out of the DMZ and into the intranet, perform the addon upgrade there and put the server back in the DMZ.

Question #1: do you recommend running the wampmanager.ini tool? You mention in the page that "but install this tool only if you need it" so we haven't tried it (we can't test the problem on a staging server because the issue only occurs in the production server that's publicaly available).

Question #2: could we manually edit wampmanager.ini to put the new version menu item in there? We tried it in a STAGING server with a "fake" php version but we must have done something wrong because the WampServer tray menu never worked right after that. So we don't want to try it on the production server.

Thanks again for all your help.

Hi,

Quote
clara-rcosta
Question #1: do you recommend running the wampmanager.ini tool? You mention in the page that "but install this tool only if you need it" so we haven't tried it (we can't test the problem on a staging server because the issue only occurs in the production server that's publicaly available).

It's no use, you don't have a problem with the wampmanager.ini file.

Quote
clara-rcosta
Question #2: could we manually edit wampmanager.ini to put the new version menu item in there? We tried it in a STAGING server with a "fake" php version but we must have done something wrong because the WampServer tray menu never worked right after that. So we don't want to try it on the production server.

What is indicated in the first lines of the file wampmanager.ini :

; **************************************************************
; ****** DO NOT EDIT THIS FILE **** DO NOT EDIT THIS FILE ******
; ** There is no point in modifying the file wampmanager.ini ***
; * The wampmanager.ini file is completely rewritten each time *
; * Wampserver is launched and each time a Wampserver, Apache, *
; * PHP, MySQL or MariaDB option is modified.                  *
; **************************************************************

There is something blocking on your production server that makes it impossible to change the menus.
For this to work, you wrote:
we had to take the server out of the DMZ and into the intranet, perform the addon upgrade there and put the server back in the DMZ.
A priori, this indicates that wampmanager cannot be rewritten and therefore new menu items do not appear.
I don't have the opportunity to test what's happening on your production server similar to yours, or why it's blocking.
All Wampserver configurations and addons are always tested on a local development server, which is why Wampserver was developed.

I don't have the opportunity to go any further in explaining your problem.
Maybe Wampserver 3.2.0 will allow this with the ability to track the execution of scripts.

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Hello again,

Thanks for all your time anyway. Yes, we'll manually upgrade the PHP version ourselves the next time we have access to the server.

We did read that wampmanager.ini file but since we were out of options we figured we could test what would happen on a testing server.

Hopefully version 3.2 (w/ script tracking) will allow us to see what is blocking the installer. In the meantime, if we figure something out we'll update this thread.

Mercy Otomatic!