I seem to have made a boo-boo. I installed web2py on a production
server that is also running a Seaside app. Like web2py, Seaside runs
its own internal server, so the app references localhost:8080, for
example.

Since installing web2py, I can access web2py, for example, with
localhost:8000. But now, I can't access the Seaside app -- I get a
forbidden access error. I surmise that it's because localhost is no
longer Seaside's internal server but web2py's. Oops.

So how do I back out of this? More importantly, how do I make web2py
coexist with Seaside, when each runs its own internal server?

Please, I hope somebody can help me.

Thanks,
Richard

Reply via email to