Home → Installation and System Configuration →

Upgrade problem to 6.10.5

• Edit

steelej

Nov 15, 2011 @ 06:26 PM

I am upgrading our test server. The upgrade seems to have gone well except I suspect my SSL configuration went awry. After installation I tested on http://localhost:8080 and all seemed well. I followed procedure to use SSL for access. The results are below:

On the local server

If I go to http://localhost:8080
it forwards me to
https://localhost:8443/login.act
Using the 8443 port in the URL works also

If I go to http://cascadedev.wit.edu
It should forward me to the above login page but is giving me a 404 error

From an external browser

If I try http://cascadedev.wit.edu
it gives a 404

If I try http://cascadedev.wit.edu:8080
It forwards properly to https://cascadedev.wit.edu:8443/login.act

If I try http://cascadedev.wit.edu:8443
I get a 404

I've enclosed my logs and xml files in hope you might see where I erred.

• cascade.log 264 KB
• catalina.2011-11-15.log 30.6 KB
• server.xml 6.81 KB
• web.xml 52.2 KB

1. Support Staff 1 Posted by Tim on Nov 15, 2011 @ 08:43 PM

   

   Hi,

   In your server.xml file, can you try changing this line:

   <Connector connectionTimeout="20000" maxThreads="256" port="8080" protocol="HTTP/1.1" redirectPort="8443"/>
   

   to this:

   <Connector connectionTimeout="20000" maxThreads="256" port="80" protocol="HTTP/1.1" redirectPort="8443"/>
   

   Then, restart Cascade and see if you can get to the site via the external link.

   • Edit

2. 2 Posted by steelej on Nov 15, 2011 @ 09:08 PM

   

   Thanks Tim,
   That did it, but I'm curious why the 8080 value was working in our previous installation. Any idea?

   Jim

   • Edit

3. Support Staff 3 Posted by Tim on Nov 15, 2011 @ 09:17 PM

   

   Hi Jim,

   By previous installation, are you referring to your production instance? Or was this working previously on this test instance? The only way I can think of that would allow your external URL to point to port 8080 would be if you had Apache installed on the machine and had a rule to redirect to this port - or - if you had multiple connectors specified in your server.xml file.

   • Edit

4. 4 Posted by steelej on Nov 15, 2011 @ 09:32 PM

   

   The SSL section of server.xml I copied directly from the 6.10.3 file to the new one. I don't know why there would be a difference, but, on the bright side, it's working now.

   • Edit

5. Support Staff 5 Posted by Tim on Nov 15, 2011 @ 09:34 PM

   

   The only section we changed to make this work was for the HTTP connector (not the HTTPS connector). So, while you may have copied over the SSL portion from the server.xml, the HTTP connector may have been set to port 80 before (but reset to port 8080 when you upgraded). Just a thought, but perhaps this isn't the case. Anyhow, I'm glad to hear this is working properly. Let us know if you ever run into any similar problems and we'll be glad to help out.

   Have a good one, Jim!

   • Edit

6. Tim closed this discussion on Nov 15, 2011 @ 09:34 PM.

7. steelej re-opened this discussion on Nov 15, 2011 @ 09:50 PM

8. 6 Posted by steelej on Nov 15, 2011 @ 09:50 PM

   

   Thanks Tim, I really appreciate it.

   • Edit

9. Tim closed this discussion on Nov 15, 2011 @ 09:57 PM.