tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/207-upgrade-problem-to-6105Cascade CMS: Discussion 2018-10-18T20:36:25Ztag:help-archives.hannonhill.com,2010-02-09:Comment/114351772011-11-15T20:43:14Z2011-11-15T20:43:14ZUpgrade problem to 6.10.5<div><p>Hi,</p>
<p>In your server.xml file, can you try changing this line:</p>
<pre>
<code><Connector connectionTimeout="20000" maxThreads="256" port="8080" protocol="HTTP/1.1" redirectPort="8443"/></code>
</pre>
<p>to this:</p>
<pre>
<code><Connector connectionTimeout="20000" maxThreads="256" port="80" protocol="HTTP/1.1" redirectPort="8443"/></code>
</pre>
<p>Then, restart Cascade and see if you can get to the site via the
external link.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/114351772011-11-15T21:08:32Z2011-11-15T21:08:32ZUpgrade problem to 6.10.5<div><p>Thanks Tim,<br>
That did it, but I'm curious why the 8080 value was working in our
previous installation. Any idea?</p>
<p>Jim</p></div>steelejtag:help-archives.hannonhill.com,2010-02-09:Comment/114351772011-11-15T21:17:53Z2011-11-15T21:17:53ZUpgrade problem to 6.10.5<div><p>Hi Jim,</p>
<p>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.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/114351772011-11-15T21:32:18Z2011-11-15T21:32:18ZUpgrade problem to 6.10.5<div><p>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.</p></div>steelejtag:help-archives.hannonhill.com,2010-02-09:Comment/114351772011-11-15T21:34:58Z2011-11-15T21:34:58ZUpgrade problem to 6.10.5<div><p>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.</p>
<p>Have a good one, Jim!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/114351772011-11-15T21:50:15Z2011-11-15T21:50:15ZUpgrade problem to 6.10.5<div><p>Thanks Tim, I really appreciate it.</p></div>steelej