Current Page: 1 of 1
Results 1 - 13 of 13
3 months ago
sebseb
That would explain things - I was updating from 3.3.1 Anyway, all good now. I moved the VirtualHost sections into https-vhosts.conf which fixes the fatal error. And added a ServerName entry for <VirtualHost *:80> which fixes the warning. Thanks again, Seb
Forum: WampServer English
3 months ago
sebseb
> Do not modify "things" without knowing the implications. I get your point of course. But bear in mind that I've worked for many years with WAMP. (I think it didn't always have the feature to configure virtual hosts via a UI. Or maybe I just preferred to edit conf files. It's been so long I have this configuration that I don't remember exactly.) My point was that a configur
Forum: WampServer English
3 months ago
sebseb
I have log_errors = Off for my dev environment so C:\wamp64\logs\php_error.log was empty. With errors on for the PHP CLI used by WAMP, and get this: [04-Mar-2026 19:45:04 UTC] PHP Warning: Undefined variable $server_name in C:\wamp64\scripts\refresh.php on line 3076 [04-Mar-2026 19:45:04 UTC] PHP Stack trace: [04-Mar-2026 19:45:04 UTC] PHP 1. {main}() C:\wamp64\scripts\refresh.php:0
Forum: WampServer English
3 months ago
sebseb
Ok, so running the 3.4.0 update broke the wampmanager.ini in a similar way to the repair process (now the file is very incomplete and the menus stopped working). With a working wampmanager.ini restored from backup, I set WAMPTRACE_PROCESS to true. wamptrace.log after start-up: wamptrace.log after attempting to switch to PHP 8.4.15 in the menu:
Forum: WampServer English
3 months ago
sebseb
Only the default Windows 10 antivirus, no 3rd party software. Outbound firewall rules are set to block by default. Might this might make a difference? httpd is permitted. Maybe not every PHP version CLI exe is allowed outboard connections though. I restored the wampmanager.ini from the save folder after the "repair" broke it, so the menus are working again now. Still have the prob
Forum: WampServer English
3 months ago
sebseb
This is what wampmanager.ini looks like after the repair process: 3KB compared to the usual 556KB And even the WAMPSERVER version is wrong.
Forum: WampServer English
3 months ago
sebseb
> Apply wampmanager.ini repair I just did that and now it's broken wampmanager.ini - the left and right click menus are not working. Most of the sections of wampmanager.ini are gone I think. It's only 79 lines long. I should mention that this was basically a brand new fresh install of 3.4.0, nothing custom. I only added an older MySQL version. (I had to do a complete uninstall and
Forum: WampServer English
3 months ago
sebseb
> Right-Click -> Restart from zero - This didn't help. Exact same behaviour as Exit and then restart as described above.
Forum: WampServer English
3 months ago
sebseb
Updated subject
Forum: WampServer English
3 months ago
sebseb
Actually, it's not just a cosmetic problem. If I Exit WAMPServer via the right-click menu, then restart, it then reverts back to php 8.3.28. Here's the full info: I switch to PHP 8.4.15 wampmanager.conf now has: phpVersion = "8.4.15" httpd.conf now has: LoadModule php_module "${INSTALL_DIR}/bin/php/php8.4.15/php8apache2_4.dll" C:\wamp64\bin\apache\apache2
Forum: WampServer English
3 months ago
sebseb
If I change the PHP version, it stays stuck on the same version in the Left-Click tray menu. e.g. I change to 8.4.15 It updates httpd.conf and wampmanager.conf ok and makes the symlink to the correct phpForApache.ini But the wampmanager.ini file is not update with the chosen PHP version, so the menu stays stuck, always showing 8.3.28 Cosmetic problem only, but it used to work fine. Broken in
Forum: WampServer English
18 years ago
sebseb
Thanks but this is where I started: with the latest version of WampServer on a fresh install of Windows XP. If something was written into the error.log file then at least I would know what's going on, but as it is httpd.exe just terminates immediately when run as a service (even though it runs just fine when started in the foreground). I tried starting the service from the command prompt an
Forum: WampServer English
18 years ago
sebseb
Hi, I have a strange problem with the apache service not starting... I have a fresh install of WinXP SP2. httpd.exe runs fine when started manually from the command prompt, so the conf file settings are all ok. But when the service is started it immediately terminates. Starting the service manually gives the following message: "Could not start the wampapache service on Local Comput
Forum: WampServer English
Current Page: 1 of 1