Re: [users@httpd] Port 80 error still there even though listening on different port

2019-02-17 Thread Luca Toscano
Hi Mike, Il giorno lun 18 feb 2019 alle ore 04:08 Mike Starr ha scritto: > > Hi, I am still getting the ubiquitous Port 80 blocked error when starting > Apache even though I am listening on port 8080 in httpd.conf. > > What am I doing wrong? I assume your OS is Linux, so what I'd do is run a

Re: [users@httpd] Apache upgrade 2.2 -> 2.4 and "PerlAuthenHandler Authen::Simple::IMAP"

2019-02-17 Thread Luca Toscano
Hi Jobst, Il giorno lun 18 feb 2019 alle ore 04:05 Jobst Schmalenbach ha scritto: > > Hi > > I have just started upgrading all of my CentOS servers from 6.X to 7.X. > With that Apache gets upgraded from 2.2 to 2.4. > > While I have fixed most of the issues one that I cannot solve is the >

[users@httpd] Re: Making my website accessible from another computer?

2019-02-17 Thread Mike Starr
Okay, so far my progress is that I have found my router's IP address and accessed it. Now I have to find the login info and enable port-forwarding to access through port 8080 (where Apache is listening) on my PC. On Sun, Feb 17, 2019 at 8:26 PM Mike Starr wrote: > Hi, I tried adding > > Order

[users@httpd] Making my website accessible from another computer?

2019-02-17 Thread Mike Starr
Hi, I tried adding Order Allow,Deny Allow from all to my httpd.conf file but that broke Apache. I would like to host my website from my computer (YES I realize it will only be accessible while apache is running and the computer is on, and yes I realize there are security issues--but I just want

Re: [users@httpd] Getting port 80 error even though listening on different port

2019-02-17 Thread Mike Starr
NOTE: ISSUE RESOLVED (SEE END OF E-MAIL MESSAGE) E-mail: Hi. Thank you for the response. First off, I am using Windows, so I don't think lsof works for me. Would the corresponding command be netstat? PID 4 is listening, in Apache it says it is "Unable to open process" and in Windows task manager

Re: [users@httpd] Getting port 80 error even though listening on different port

2019-02-17 Thread Chris Punches
Your configuration files would be a wonderful start. On Sun, Feb 17, 2019, 10:21 PM Mike Starr wrote: > I've modified the Listen directive in httpd.conf to listen on port 8080 > instead of 80 but Apache still won't start, with the error that port 80 is > blocked. > > What am I doing wrong? > >

RE: [users@httpd] Getting port 80 error even though listening on different port

2019-02-17 Thread Muggeridge, Matt
You don’t say what is listening on port 80. I’d first stop Apache httpd and then check the ports you want to use are free: lsof -i:80 -i:8080 This should return nothing. Watch the Apache httpd error log, as specified in your “ErrorLog” directive; I suggest using “tail -f ”, then start Apache

[users@httpd] Getting port 80 error even though listening on different port

2019-02-17 Thread Mike Starr
I've modified the Listen directive in httpd.conf to listen on port 8080 instead of 80 but Apache still won't start, with the error that port 80 is blocked. What am I doing wrong? Thanks. Michael PS: Sorry if this is a double post, I sent this message before I was added to the mail list so I'm

[users@httpd] Apache upgrade 2.2 -> 2.4 and "PerlAuthenHandler Authen::Simple::IMAP"

2019-02-17 Thread Jobst Schmalenbach
Hi I have just started upgrading all of my CentOS servers from 6.X to 7.X. With that Apache gets upgraded from 2.2 to 2.4. While I have fixed most of the issues one that I cannot solve is the "PerlAuthenHandler Authen::Simple::IMAP" in .htaccess files. I use this frequently on many machines as

[users@httpd] Port 80 error still there even though listening on different port

2019-02-17 Thread Mike Starr
Hi, I am still getting the ubiquitous Port 80 blocked error when starting Apache even though I am listening on port 8080 in httpd.conf. What am I doing wrong? Michael