Redirect server for Confluence problem

[Jonathan Kim]

It seems we are having the same redirect issue with our Confluent application after we had to do emergency restore of our server.  It originally pointed to Wiki location

[Edsel_Clarin]

Hi JP,

Back in February, Dustin Safady helped us resolve a connectivity issue with our JIRA server (Case #GHS-178709).  As it turns out, requests were not being routed to the JIRA because our URL (http://jira.amada.com) is no longer available.  Dustin instructed us to change the connector in server.xml as follows, and that fixed the problem.

New Connector:

<Connector port="8081"
maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"
enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
acceptCount="100"
disableUploadTimeout="true"
relaxedPathChars="[]|"
relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"/>

Old Connector:

<!-- For https://jira.amada.com
<Connector port="8090" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.amada.com" proxyPort="443"/>
-->

Our problem now is that we have lost connectivity to our Confluence and Bitbucket applications as well, and it feels alot like the same cause.  The URLs for those apps are also no longer available, and we need to remove any URL connectors, such as was done with JIRA.

Regards,

Edsel Clarin

[JP _AC Bielefeld Leader_]

Hi,

solution for Confluence & Bitbucket is about the same. The server.xml is the file to check for Confluence & Bitbucket.

Best

JP

[JP _AC Bielefeld Leader_]

Hi,

sorry, but I'm missing a question here...

Also "same redirect issue" & "Wiki location" is nothing I can help with.

Could you provide more & detailed information?

Best

JP