[Seaside] Simple network question

[Derek Brans]

Hi Michael,

Does the exact same seaside app work on the remote machine at a higher port?

Next, check that port 80 is not in use by another process:
netstat -an | grep 80

Next, put a 'self halt' in WAKom>>process: (if that's what you're using) to
see if the request is getting through to WAKom.

Derek Brans
Nerd on a Wire
Web design that's anything but square
http://www.nerdonawire.com
phone: 604.874.6463
mailto: brans at nerdonawire.com

----- Original Message -----
From: "Michael Cole" <michael.cole at nimiq.net>
To: <seaside at lists.squeakfoundation.org>
Sent: Tuesday, May 06, 2003 9:51 AM
Subject: [Seaside] Simple network question


> I have a seaside app that runs fine on my local network on a high port
> (>1024). I want to move it to a server machine and expose it to the world
on
> the standard http port 80. My firewall is configured to allow http and
https
> to the machine, and I can confirm the port is accessible from the outside
> world by starting up apache and setting it to listen to the standards
ports.
>
> Unfortunately, when I start seaside (WAKom startOn:80) there is no
connection
> to be made "connection refused". I can access a service running on the
high
> port from other machines inside the firewall.
>
> I know this must be a network issue, but am at a loss to understand what
the
> problem might be. Perhaps the network/firewall savvy can provide a clue?
>
> Many thanks,
>
>
> Michael Cole
>
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>
>