[Seaside] Seaside Listening on localhost only ?

Sebastian Sastre ssastre at seaswork.com
Mon Nov 26 16:17:11 UTC 2007

Hi Sven,

	most surely is a firewall issue. What distro is your server? Make
sure you can telnet that port in that host from remote machines or see

Seaside uses KomHttpServer that AFAIK does not have restrictions on hosts by
default nor internal firewall support.


Sebastian Sastre


> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Sven Van Caekenberghe
> Enviado el: Lunes, 26 de Noviembre de 2007 12:59
> Para: seaside at lists.squeakfoundation.org
> Asunto: [Seaside] Seaside Listening on localhost only ?
> Hi All,
> I just recently started working with Seaside again after a 
> long hiatus, so I am probably missing something obvious or 
> simple. While trying to deploy a test web application on a 
> server (Squeak-3.9-8.i686- pc-linux-gnu VM on RHEL 4), I 
> discovered that both there and on my development machine 
> (Squeak 3.8.18beta1U VM on Mac OS X 10.5) using a Squeak 3.9 
> image with Seaside 2.8 started with WAKom startOn: 8080 only 
> bind their server socket on localhost ( and do 
> hence not accept network connections.
> Is this by design (and do I need to put Apache proxying in front of
> it) or is there a way to fix this ?
> If I am tracing the call graph correctly, I arrive at  
> TcpListener>>pvtNewListener: where clearly
> Socket>>listenerOn:backlogSize:interface: is called with the interface
> argument hard-coded to #(127 0 0 1). It seams that Squeak has 
> NetNameResolver localHostAddress which would give back the 'correct'  
> interface name to bind the server socket to ?
> All hints appreciated!
> Thx,
> Sven

More information about the seaside mailing list