Forum OpenACS Q&A: Re: After upgrade, users unable to register

Collapse
Posted by Jade Rubick on
Thank you for the stabs :)

The SystemURL is http://www.safe4all.org

The system is actually on port 8000, but the router is directing it from port 80 to port 8000 inside the LAN.

When I first upgraded, the site actually went down because of this problem. For some reason, the ForceHostP was reset (I believe) to 1, so it would force all requests to go to port 8000. I set it to 0, and it worked.

So I guess my problem might be related to that. The easiest fix might just be to move the port, but this is a really strange error to get, and I have no idea of how to track it down.

Is this a request processor issue?

Collapse
Posted by Robert Locke on
Hi Jade,

Ah.... well that explains it!

Looking at the telnet session above, here's what's appears to be going on:

  • The browser attempts to fetch "/register" without the trailing slash.
  • The server redirects to the directory "/register/". Since you're running on port 8000, it provides the fully qualified host name of "www.safe4all.org:8000", which seems to be the correct behavior.
  • The browser fails to connect to port 8000 (because your router's external interface is listening on 80) and appears to try a convoluted URL (that's the part I don't fully understand).

In any case, I'm not sure of a better solution, but I think it should work if you had the webserver listen on port 80 and had the router forward from port 80 to port 80.

And, for now, you can atleast change the register link on your home page and other pages to:
    http://www.safe4all.org/register/

Note the trailing slash. Click on the above link to see that it works..

Hope that helps!