I must apologise for my screw-up.
Apache is working fine.
The problem was that when I sought to access Webmin i got the message :
This server is running in ssl mode. I assumed it was apache, not
realizing that port 1 took me to the Webmin server.
To clear things up, apache2.2.4 apparently au
On 7/12/07, pj <[EMAIL PROTECTED]> wrote:
Chuck Swiger wrote:
> On Jul 11, 2007, at 10:22 AM, pj wrote:
>> I can access apache from my windows machine: "It works"
>> But I cannot access http://biggie:1 - message says: try https://...
>> that does bring up the Webmin page. I know apache liste
Chuck Swiger wrote:
On Jul 11, 2007, at 10:22 AM, pj wrote:
I can access apache from my windows machine: "It works"
But I cannot access http://biggie:1 - message says: try https://...
that does bring up the Webmin page. I know apache listens on port 80,
but why https to get the Webmin page?
Thanks for the speedy reply.
I saw something about this accf_http while checking the Web, but haven't
got to trying that yet. I find it strange since this was never needed
before - even in my previous installation of apache22.
I'll try it shortly.
Amitabh Kant wrote:
On 7/11/07, pj <[EMAIL PRO
Sorry, the file is /boot/loader.conf
Regards
Amitabh
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 7/11/07, pj <[EMAIL PROTECTED]> wrote:
On top of this, when I try to stop apache with apachectl stop, apache
stops. But apachectl start gives : "[warn] (2) No such file or
directory: Failed to enable the 'httpready' Accept Filter"
Phil
Either load the kernel module using "kldload accf_ht
On Jul 11, 2007, at 10:22 AM, pj wrote:
I can access apache from my windows machine: "It works"
But I cannot access http://biggie:1 - message says: try
https://...
that does bring up the Webmin page. I know apache listens on port
80, but why https to get the Webmin page?
Umm, so you don
