[Sluglug] Apache Server on Resnet

[Erich]

Oh, wow, of course - I should have realized. I set up iptables to drop all
ports besides 80 and 22 like a hot potato. Well, that's not true, I opened a
few other ports for games... I guess they just don't show up in an nmap or
something? Or maybe only when I am playing said games.

This has gone on too long. I'm just going to give it a try.

Thanks everyone for all your tips and suggestions. You've been a big part of
my learning process over the past few weeks. I hope all of my time here is
as productive as it has been so far.

By the way, and I feel I am obligated as a proud parent of a (I believe)
well crafted web site, if this https deal works, you can see it at
https://timothytoo.dyndns.org. It's now using 100% squashable CSS, and a
completely dynamic php/mysql interface. I'm going to be adding comments to
it soon (the code is all in place, I just need to create the html), and then
I can go wild with content. But, uh, until I do so, it's a rather boring
site - but there it is.

~Erich

PS: Just finished the config - connection refused. I set up the certs, set
up the vhost, told http.conf to LISTEN to 443, put in LoadModule mod_ssl
(and gave it the path) - when loading apache2 a second time I got an error:

(98)Address already in use: make_sock: could not bind to address [::]:443
No listening sockets available, shutting down
Unable to open logs

Figuring this was just because the server wasn't shutting down cleanly, I
rebooted. Got the same error at "default" boot time. Oh well.

Anyway, unless anyone can think of something obvious, I'm just going to
stick to port 80 until thanksgiving, when I hope to fix this all by hosting
it from my home. I have a Sun UltraSparc2 there running Gentoo that I can
set up with a tunneled SSH and a tunneled apache server. So I think that
that is the ticket.

Right, that's enough. Signing out!


On 10/24/05 10:25 AM, "Misha Nasledov" <misha at nasledov.com> wrote:
> https ought to work from ResNet .. it was working great last year. I don't
> know if they changed it this year, but it doesn't seem likely. It's always
> worth a shot. I believe that Apache2 in Debian supports SSL out-of-the-box..
> 
> On Wed, Oct 19, 2005 at 02:00:23PM -0700, cerise at armory.com wrote:
>>    I thought https might work, but it won't.  I nmapped your IP.  That tells
>> me
>> that most ports are filtered.  The only open port <8080 is ssh at port 22.
>>    BTW, you probably already have https set up.  All you should have to do if
>> not is load mod_ssl.