Page 1 of 1

windows 8.1+xampp

PostPosted: 31. August 2015 07:48
by lassinni
I assumed that problem with apache was from skype ports but it seems it is seems there is something else on problem. Could you help with this
[Mon Aug 31 08:08:59.934174 2015] [ssl:warn] [pid 1812:tid 392] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Aug 31 08:09:00.253169 2015] [ssl:warn] [pid 1812:tid 392] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Aug 31 08:09:00.343162 2015] [mpm_winnt:notice] [pid 1812:tid 392] AH00455: Apache/2.4.16 (Win32) OpenSSL/1.0.1p PHP/5.6.12 configured -- resuming normal operations
[Mon Aug 31 08:09:00.344163 2015] [mpm_winnt:notice] [pid 1812:tid 392] AH00456: Apache Lounge VC11 Server built: Jul 12 2015 10:56:48
[Mon Aug 31 08:09:00.344163 2015] [core:notice] [pid 1812:tid 392] AH00094: Command line: 'C:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Mon Aug 31 08:09:00.350162 2015] [mpm_winnt:notice] [pid 1812:tid 392] AH00418: Parent: Created child process 2960
[Mon Aug 31 08:09:01.625244 2015] [ssl:warn] [pid 2960:tid 392] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Aug 31 08:09:01.957306 2015] [ssl:warn] [pid 2960:tid 392] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Aug 31 08:09:02.055315 2015] [mpm_winnt:notice] [pid 2960:tid 392] AH00354: Child: Starting 150 worker threads.

Re: windows 8.1+xampp

PostPosted: 31. August 2015 11:11
by Nobbie
I cannot see any error. Simply ignore the warnings about www.example.com, these do not have any effect.

Re: windows 8.1+xampp

PostPosted: 01. September 2015 05:27
by lassinni
Ok i edited httpd.conf file ports to 85 from 80 and still problem prevails. Does anyone have idea how to fix this now
edited*
Edited also httpd-ssl file and that solved a trick. But how to now open localhost site?

Re: windows 8.1+xampp

PostPosted: 01. September 2015 13:37
by Nobbie
lassinni wrote:But how to now open localhost site?


When you choose to take another port than port 80 (which is default for HTTP), you have apply the portnumber in the URL:

http://localhost:85

If you also changed port 443 for HTTPS (for example 445), you also have to apply the portnumber in https connections:

https://localhost:445


I do not recommend to solve the port problem in this way, it would be far better to find out the reason, why the ports are already in use, because these ports are meant for webservers like Apache. And port 85 is not standard.