[Mon Dec 28 12:21:57.562500 2015] [ssl:warn] [pid 4800:tid 740] AH01909: RSA certificate configured for www.example.com:443 does NOT include an ID which matches the server name
[Mon Dec 28 12:21:57.906250 2015] [ssl:warn] [pid 4800:tid 740] AH01909: RSA certificate configured for www.example.com:443 does NOT include an ID which matches the server name
[Mon Dec 28 12:21:58.000000 2015] [mpm_winnt:notice] [pid 4800:tid 740] AH00354: Child: Starting 150 worker threads.
Self-signed certificate or reverse dns warning (dns record change can only be done by ISP). Almost sure it is a self-signed cert issue or just the host config. Change www.example.com in your config to your actual domain name.
not using a certificate. I am using Hamachi for remote access. I get this when a remote user edits the patient demographics. Hamachi is a logmein product and it creates a vpn tunnel and everything is routed over the tunnel. This just happens at one site and to my knowledge they are all setup the same.
Uh…very different, and outside my scope, but 443 apache thinks it is https and if it is talking about www.example.com, then you are needing to look at your httpd.config or vhosts file and look for something like this:
<VirtualHost *:80>
DocumentRoot /www/example1
ServerName www.example.com
Otherwise it wouldn't come up with the name example.com would it?
Ping yourself at port 80 from your remote access. Better yet, just forward port 3386 or you favorite and use a no man-in-the-middle RDP, then test hitting localhost:443 and compare it to localhost:80
See above…Post awaiting moderation? NO, the tilde lines do NOT make an uninterpreted code block. I have almost never had it work. this is getting quite off topic though…sorry.
I try it here with meaningless code and it will work:
But the Xampp control panel says it is running on port 80. This error is only happining when you run thru Hamachi. Here is another wrinkle if you run the developer cosole in chrome the eror goes away.
OK, sometimes apache on 443 (in windows) just flat out flakes. This is a known thing, but there is a dearth of information on it.
My best method of dealing with that is to have ngnix on the firewall box handle the https stuff and forward it to the server running apache.
So, yeah, maybe this is a new and unrelated issue to your first error message. Are you only using chrome or chromium, or are you using firefox as well for testing?
Know that when it comes to JS there are differences.
OOOOOOHHH! DANG!
Dude, are you SURE you have all the billion tweaks needed to run xammp on anything other that the drive letter C:? I personally have not ever been fully successful with it anywhere else!
this is on one clients server. I have 14 that are working just fine. It also happens on my test box. I took the opportunity on my test box of renaming the xampp directory and loading it again from the OEMR website. Loaded it and the problem was still there (thinking that the xampp load was the major problem) Problem stayed. I commented out line 522 in the Apache config file to take care of the ssl stuff ( line 522 is Include conf/extra/httpd-ssl.conf)
Solution : Change secure VPN software. It is a Hamachi problem upon further investigation the other locations have the same issue once the VPN software is used for a period of time. This client just uses the software more than anyone else.