Thanks, that worked. In the meantime I also managed to install web2py as a service, and setting the "options.py" to 0.0.0.0 and port 80 and it works fine. Note IIS is disabled too.
Cheers for your help again.. On May 27, 2:31 pm, mdipierro <[email protected]> wrote: > Honestly I have never seen anybody configure web2py with windows > server and it may not be trivial (except in proxy mode) because it > requires this: > > http://sourceforge.net/apps/trac/pyisapie > > My guess is that you do not have pyisapie and you are running both the > built in web2py web server on 127.0.0.1 and IIS on localhost:80. > If you want to expose web2py to your public network the easiest way is > NOT to use IIS and just use the built-in server. Instead of 0.0.0.0 > try using your actual IP address. You can find it with > > arp -a > > On May 27, 8:25 am, Andrew Buchan <[email protected]> wrote: > > > > > Hello, > > > I had my web2py running happily on a windows 2003 server, or so I > > thought, and when I went to check it to install an application it > > seemed not to be running (no one's using it yet so can't tell when it > > stopped). I tried stopping and starting it from the GUI, and it comes > > up with "The page cannot be displayed" in the browser. > > > It works if I set it to 127.0.0.1:8000 or 127.0.0.1:80, but not from > > 0.0.0.0:8000 or 0.0.0.0:80. > > > I tried enabling and disabling IIS Admin Service, but this seems to > > have no effect... > > > I can't seem to think of any changes that I have made other than > > removing folders which contained other frameworks I played about with > > which IIS may have been pointing at. > > > Does IIS need to be on for me to access 0.0.0.0:80? (I'm using the non- > > source version of web2py which is meant to have its own server...) > > > Anyone have any ideas/tips on running web2py on windows or why it > > might not be working, also am I best installing it as a service? > > > Thanks.
