Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Reverse Proxy Problem after lost httpd file |
|
| Author |
|
Doyman
Joined: 19 Jun 2018
Posts: 2
Location: USA, Sioux Falls, SD
|
 Posted: Thu 21 Jun '18 18:27 Post subject: Reverse Proxy Problem after lost httpd file |
 |
|
I'm working with a client who lost their httpd file. It is a Windows server running Apache and is being used as a reverse proxy. I have been trying to build the httpd file and we've been testing it.
* Note- that without the virtualhost stanzas, apache opens up and the pages can be accessed. However, after about 5 to 10 minutes, the webpages hang and stop responding.
* The client also has SSL setup in their environment
* The bad part is that the website is currently running on a windows server and is running fine. I think the httpd code is running in memory. They do not have a backup of the file. Client said they went to edit the file to get a copy of the text- and then the screen went blank and it was gone. That's all I know.
The following is the current httpd.conf file. I am trying to figure out how to allow both servers to be allowed to use 443. I'm quite sure there are other issues. Please have a look. I checked my pride at the door. I've setup plenty of apache web servers. just not any reverse proxies, let alone those with more than one server
Admin note:
Warning, see forum rules.
httpd.conf file moved to pastbin : https://apaste.info/FHWv
***********
The Errors;
The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address [::]:443 .
And
The Apache service named reported the following error:
>>> (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : AH00072: make_sock: could not bind to address 0.0.0.0:443 .
And
The Apache service named reported the following error:
>>> AH00451: no listening sockets available, shutting down .
And
The Apache service named reported the following error:
>>> AH00015: Unable to open logs
 |
|
| Back to top |
|
Doyman
Joined: 19 Jun 2018
Posts: 2
Location: USA, Sioux Falls, SD
|
| Posted: Thu 21 Jun '18 21:45 Post subject: |
|
|
| This issue isn't "solved" but we found a work around. No need to work through it. thank you! |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Mon 16 Jul '18 15:28 Post subject: |
|
|
| What did you do to get it working? |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Mon 16 Jul '18 15:33 Post subject: |
|
|
I think there is a program listen on port 443
see https://www.apachelounge.com/viewtopic.php?t=1265
or maybe
On Windows 10 there is sometimes an error that port 80 is blocked, it might be W3SVC service. Set it to "manual" starting.
| Code: | french name is: "Service de publication World Wide Web"
english name is: "World Wide Web Publishing Services"
german name is: "WWW-Publishingdienst"
Polish name is: "Usluga publikowania w sieci WWW"
Russian name is "Служба веб-публикаций" |
|
|
| Back to top |
|
|
|
|
|
|
