httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Jones <>
Subject Re: [users@httpd] Re: troubleshooting apache server
Date Sat, 30 Jan 2010 16:11:46 GMT
I guess it just took resetting my router. I am IN. Thanks for all of your


On Sat, Jan 30, 2010 at 8:44 AM, Scott Jones <> wrote:

>  On Sat, Jan 30, 2010 at 4:04 AM, Nicholas Sherlock <>wrote:
>> On 30/01/2010 10:41 a.m., Scott Jones wrote:
>>> I run apache 2 on my server, at <>, and
>>> have no problem accessing it locally. I run Mailman and SugarCRM among
>>> others, but am dead in the water for the moment. I have ports 80 and 443
>>> forwarded to my server machine through my Linksys WRTP54G router. I can
>>> ssh in to my server no problem, but I can't access the admin pages for
>>> SugarCRM or for Mailman.
>>> Where do I start in troubleshooting my setup? I have two identical hdds
>>> in this server and have already installed Ubuntu 9.10 with ext4 on the
>>> second drive. Would I better off just moving over to the new drive,
>>> installing Apache2, Mailman, SugarCRM and starting fresh there? That
>>> option exists but I'd still like to figure out why Apache is not serving
>>> up pages correctly as is.
>> Whoops, I see you're currently running Ubuntu.
>> Your hosting on port 443 is working just fine. I can see your SugarCRM
>> login page at There's nothing listening on port 80,
>> though.
>> You should check your Apache error log, and double check your
>> port-forwarding configuration.
> Nicolas:
> I tried logging in to and indeed I arrive at
> the login screen too. Is this because my installation of SugarCRM is setup
> to be secure, https, while my Mailman installation is just without the
> security, http? Secure on 443 and unsecure on port 80?
> I went to my router webmin page and unchecked port 80 forwarding, saved,
> and went back and switched it back on. Port 80 is forwarded to the same
> internal machine address as port 443, so it has to be elsewhere. I can't
> access my system from work here today so I'll have to check the error log
> tonight.
> Any other suggestions?
> Scott

View raw message