WampServer

I have an https / apache problem I can't solve and I would like to receive some help if possible.

My virtual hosts cant be reached anymore (except with localhost) in 2 browsers (Firefox and Chrome).

I assume the reason is that both browsers now oblige to use https, but I dont want to install a certificate for my virtual hosts.

Are there any settings I can adjust in the apache configuaration files or should I solve this 'browserside' (which I didnt manage) ?


Please help.

Hi

Its not a problem at the WAMPServer end. This is purely the browser.

Are you using a .dev extension on your Virtual Hosts. We all used to do that and you will find posts here suggesting that.

However, recently Google purchased and now owns the .dev tLD so you should consider using something else instead, specially if you are using Chrome browser as google could add anything in there to pick up the use of .dev and, well, do anything.


Also as of V63 Chrome does in fact force a redirection of .dev and attempts to assume a HTTPS connection.

The simplest solution is to change your Virtual Host and HOSTS file and use something other than .dev as the domain extension.

I have started using .test or you might like .local, these are just examples you can pick anything you like.

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

I made a new virt host called *.test and one called *.ddev, but both didnt work.


I also tried *.localhost as virtual tld, BUT .. I had to use a Empty Cache Hard Reload in Chrome before I got it working.

So it seems to work only for one tld.



Edited 1 time(s). Last edit at 03/15/2018 12:31PM by LivingThis.

Sorry I dont understand.

Maybe if you show your Virtual Host definitions

---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>
Read The Manuals Apache -- MySQL -- PHP -- phpMyAdmin
Get your Apache/MySQL/mariaDB/PHP ADDONs here from the WAMPServer alternate Repo
-X-X-X- Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-

Hi,

What is the result of :
- Right-Click wampmanager tray icon ->Tools -> Sow VirtualHost examined by Apache

Did you perform a DNS restart after modifying the VirtualHost and the hosts file with the related tld
- Right-Click wampmanager tray icon -> Tools -> Restart DNS

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