Groups | Search | Server Info | Login | Register

Groups > alt.apache.configuration > #4354

Re: OS 10.13 High Sierra Apache listening ports

Show all headers | View raw

On Friday, October 20, 2017 at 8:54:30 AM UTC-7, Jerry Stuckle wrote:
> On 10/20/2017 12:11 AM, JamieCoy wrote:
> > On Wednesday, October 18, 2017 at 8:28:19 PM UTC-7, Jerry Stuckle wrote:
> >> On 10/18/2017 3:04 PM, JamieCoy wrote:
> >>> On Friday, October 13, 2017 at 6:57:40 PM UTC-7, Jerry Stuckle wrote:
> >>>> On 10/13/2017 9:30 PM, JamieCoy wrote:
> >>>>> On Tuesday, October 3, 2017 at 11:41:25 AM UTC-7, Jerry Stuckle wrote:
> >>>>>> On 10/2/2017 11:02 PM, JamieCoy wrote:
> >>>>>>> On Monday, October 2, 2017 at 7:58:50 AM UTC-7, Jerry Stuckle wrote:
> >>>>>>>> On 10/2/2017 12:08 AM, JamieCoy wrote:
> >>>>>>>>> On Saturday, September 30, 2017 at 1:02:43 PM UTC-7, Ivan Shmakov wrote:
> >>>>>>>>>>>>>>> JamieCoy rites:
> >>>>>>>>>>>>>>> On Thursday, September 28, 2017 at 8:45:31 AM UTC-7, Ivan Shmakov wrote:
> >>>>>>>>>>
> >>>>>>>>>> [...]
> >>>>>>>>>>
> >>>>>>>>>>       >> Leave the <IfDefine /> sections intact, and put additional (i. e.,
> >>>>>>>>>>       >> other than "Listen 80") ports outside of them; like:
> >>>>>>>>>>
> >>>>>>>>>> [...]
> >>>>>>>>>>
> >>>>>>>>>>       > Thanks Ivan - I tried your suggestion but to no avail.  My web site
> >>>>>>>>>>       > requires a web hop that I have via DynDNS.
> >>>>>>>>>>
> >>>>>>>>>> 	Do you mean "reverse proxy" or just a DNS name for a "dynamic" IP?
> >>>>>>>>>>
> >>>>>>>>>> 	(It's been years since I've last used DynDNS.)
> >>>>>>>>>>
> >>>>>>>>>>       > Since my OS update, I have a new IP address for the first time in
> >>>>>>>>>>       > many months.  I checked for open ports on it and the port I
> >>>>>>>>>>       > designated to be open (8201) via my router is not showing - in fact
> >>>>>>>>>>       > there are no open ports at all.
> >>>>>>>>>>
> >>>>>>>>>> 	I suppose you should check ports open on the server first, like
> >>>>>>>>>> 	the following.  (That's for GNU/Linux; don't know if that'd work
> >>>>>>>>>> 	on your system.)
> >>>>>>>>>>
> >>>>>>>>>> $ netstat -ln | grep -F -- :80
> >>>>>>>>>> tcp6       0      0 :::80                   :::*                    LISTEN
> >>>>>>>>>> $
> >>>>>>>>>>
> >>>>>>>>>> 	If you use private (RFC 1918) IPv4 addresses in your network,
> >>>>>>>>>> 	you can also try to connect to the server using such an address
> >>>>>>>>>> 	(with a browser, Wget, cURL, etc.)
> >>>>>>>>>>
> >>>>>>>>>>       > I'm wondering if since the last time I was assigned an IP address if
> >>>>>>>>>>       > Comcast policy has changed and closed these ports.  Does that sound
> >>>>>>>>>>       > right to you?  Not having that port open explains why Apache can't
> >>>>>>>>>>       > start up successfully.
> >>>>>>>>>>
> >>>>>>>>>> 	The ISP policy changes could've prevented your server from being
> >>>>>>>>>> 	accessed from the "outside," but I see no way they would've been
> >>>>>>>>>> 	of any hindrance to its starting up.
> >>>>>>>>>>
> >>>>>>>>>> 	I suggest that you check the server's logs (ErrorLog,
> >>>>>>>>>> 	specifically) for any clues.  And also:
> >>>>>>>>>>
> >>>>>>>>>> # apachectl configtest
> >>>>>>>>>>
> >>>>>>>>>> [...]
> >>>>>>>>>>
> >>>>>>>>>> -- 
> >>>>>>>>>> FSF associate member #7257  http://am-1.org/~ivan/    7D17 4A59 6A21 3D97 6DDB
> >>>>>>>>>
> >>>>>>>>> I have run the configtest and it's coming up with MANY errors, mostly in modules saying they're already loaded but a very curious one about a syntax error in line 551....and that line's syntax has not changed from the previous version!  If you will indulge me, would you mind taking a look at this rather lengthy configtest results?....I'm well and truly stumped now.  Thanks
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Before worrying about line 551, get your other errors fixed first.  If
> >>>>>>>> modules are being loaded twice, comment out the second load (or surround
> >>>>>>>> it with <Ifmodule !modname>...</Ifmodule> conditionals.
> >>>>>>>>
> >>>>>>>> Once you do that, look at any other errors you have and fix them,
> >>>>>>>> starting with the first.
> >>>>>>>>
> >>>>>>>> Just because a line syntax hasn't changed doesn't mean it's not a
> >>>>>>>> problem.  For instance, that particular command may have been deleted, a
> >>>>>>>> module may not be loaded or lots of other things.
> >>>>>>>>
> >>>>>>>> -- 
> >>>>>>>> ==================
> >>>>>>>> Remove the "x" from my email address
> >>>>>>>> Jerry Stuckle
> >>>>>>>>
> >>>>>>>> ==================
> >>>>>>>
> >>>>>>> HI Jerry - I see no instance of a module being double loaded in the httpd.conf file. This is why I'm so stymied.  Thanks!
> >>>>>>>
> >>>>>>>
> >>>>>> <snip>
> >>>>>>
> >>>>>> Well the Apache configuration thinks there is, and I haven't found it to
> >>>>>> be wrong.  You could have other files included in your httpd.conf (very
> >>>>>> common in some distros) or some modules were compiled into Apache.
> >>>>>>
> >>>>>> Lots of possibilities here - just because you don't see the same modules
> >>>>>> listed in your LoadModule statements in your httpd.conf file doesn't
> >>>>>> mean they aren't being loaded multiple times.
> >>>>>>
> >>>>>> -- 
> >>>>>> ==================
> >>>>>> Remove the "x" from my email address
> >>>>>> Jerry Stuckle
> >>>>>> j
> >>>>>> ==================
> >>>>>
> >>>>> Okay, I was able to find a mistake in my httpd.conf file and the syntax all works fine now - however, the folks at DynDNS tell me that the port I need opened, 8201, is not in fact open, even though I have changed nothing on my router - same static address on the same router, same open ports, same everything.  Is my router giving up the ghost, or does Comcast block these ports now? They SAY they don't, but I'm stymied here....
> >>>>>
> >>>>
> >>>> I have no idea.  I'm not on your system and my crystal ball is broken.
> >>>> You need to do some troubleshooting on your system.
> >>>>
> >>>> -- 
> >>>> ==================
> >>>> Remove the "x" from my email address
> >>>> Jerry Stuckle
> >>>>
> >>>> ==================
> >>>
> >>> Thanks - I've already tried, but no revelations. My router is working fine aside from not being able to open the needed port. Does the port not open until the service is running?  In other words, would port 8201 not show as open until Apache is successfully running, or should it be open prior to that?  Thanks again.
> >>>
> >>
> >> A port is open only if someone opens it.  Typically that is some
> >> application (although a kernel module could open it).  If the port is
> >> open before Apache is running, some other application has opened it.
> >> This will cause an error when Apache tries to open it.
> >>
> >> You can always telnet to the port to see if it's open or not.  If it's
> >> open, you will be able to connect (although you may not be able to do
> >> anything else).  If the port is not open, your connect attempt will fail.
> >>
> >> Trying this from different locations should give you a better idea what
> >> is blocking the communications.  You need to start at the system running
> >> Apache and work out from there.
> >>
> >> -- 
> >> ==================
> >> Remove the "x" from my email address
> >> Jerry Stuckle
> >
> >> ==================
> > 
> > So it would appear that since Apache isn't opening, that it isn't opening the needed port. I've confirmed the it is running, and also that the site cannot be accessed from anywhere. I am indeed working from the machine that's running Apache. At least I now know that the problem is one of two things - either my httpd.conf file is corrupt (the syntax comes up as correct now), OR my five year old Apple Express Router is giving up the ghost and can't open ports correctly.  Thanks again for your help!
> > 
> 
> The real question here is - can you access it from that machine?  You 
> need to be able to do that before you can access it from another one.
> 
> And there are other possibilities, also.  Yes, despite not having any 
> errors, your Apache configuration may not be set up correctly.  Or you 
> may have a firewall on your machine not allowing traffic to the port. 
> Or your router may not be set up to properly forward packets from 
> outside of your LAN to your machine.  Or any of a number of possibilities.
> 
> But it all starts with being able to access your server from the server 
> itself.  Then moving out from there.
> 
> -- 
> ==================
> Remove the "x" from my email address
> Jerry Stuckle
> 
> ==================

I can't access the site from my own Mac, the same one that is ostensibly running Apache.  No other computer in the house can access it either.

I'm wondering if there's some module I had to enable in this version which previous versions have not required....that happened once before in a previous Apache update.

The other possibility is that the httpd.conf file is corrupt, even though it passes the syntax test - and then finally there's the router - it has the exact same configuration it always has had when Apache has been working. And it's still doing its DHCP thing just fine, it's just that the port isn't opening. The port I opened for screen sharing IS working, so I'm less inclined now to think that the router is failing. 

And the mystery continues...thanks again for your help. It is very much appreciated.

Back to alt.apache.configuration | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-09-27 20:29 -0700
  Re: OS 10.13 High Sierra Apache listening ports Bruce Esquibel <bje@ripco.com> - 2017-09-28 15:29 +0000
  Re: OS 10.13 High Sierra Apache listening ports Ivan Shmakov <ivan@siamics.net> - 2017-09-28 15:45 +0000
    Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-09-30 12:30 -0700
      Re: OS 10.13 High Sierra Apache listening ports Ivan Shmakov <ivan@siamics.net> - 2017-09-30 20:02 +0000
        Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-01 21:08 -0700
          Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-02 10:58 -0400
            Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-02 20:02 -0700
              Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-03 14:41 -0400
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-13 18:30 -0700
                Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-13 21:57 -0400
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-18 12:04 -0700
                Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-18 23:28 -0400
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-19 21:11 -0700
                Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-20 11:54 -0400
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-22 13:01 -0700
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-22 13:03 -0700
                Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-22 18:26 -0400
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-10-22 19:26 -0700
                Re: OS 10.13 High Sierra Apache listening ports Kees Nuyt <k.nuyt@nospam.demon.nl> - 2017-10-23 17:26 +0200
                Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-23 15:38 -0400
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-11-07 21:48 -0800
                Re: OS 10.13 High Sierra Apache listening ports Kees Nuyt <k.nuyt@nospam.demon.nl> - 2017-11-09 01:48 +0100
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-11-08 22:34 -0800
                Re: OS 10.13 High Sierra Apache listening ports Kees Nuyt <k.nuyt@nospam.demon.nl> - 2017-11-09 13:46 +0100
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-11-10 21:42 -0800
                Re: OS 10.13 High Sierra Apache listening ports Kees Nuyt <k.nuyt@nospam.demon.nl> - 2017-11-11 11:28 +0100
                Re: OS 10.13 High Sierra Apache listening ports Bruce Esquibel <bje@ripco.com> - 2017-11-11 15:39 +0000
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-11-12 13:28 -0800
                Re: OS 10.13 High Sierra Apache listening ports JamieCoy <coyle.james1@gmail.com> - 2017-11-15 13:59 -0800
                Re: OS 10.13 High Sierra Apache listening ports Jerry Stuckle <jstucklex@attglobal.net> - 2017-10-22 18:21 -0400
          Re: OS 10.13 High Sierra Apache listening ports Ivan Shmakov <ivan@siamics.net> - 2017-10-03 15:30 +0000

csiph-web