It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Azure - 502 - Web server received an invalid response while acting as a gateway or proxy server.

Joakim Bergquist Mar 16, 2018

We have followed the documentation and the wizard regarding setting up Jira in Azure. However we get the 502 response. 

 

I don't have much Azure knowledge but following this guide: https://docs.microsoft.com/sv-se/azure/application-gateway/application-gateway-troubleshooting-502

Doesnt give me much help since my subscipting doesnt allow me to run these commands. 

PS C:\Console> $vnet = Get-AzureRmVirtualNetwork -Name jiravnet -ResourceGroupName IT_JIRA
Get-AzureRmVirtualNetwork : The current subscription type is not permitted to perform operations on any provider namespace. Please use a different subscription.

 

I also checked the Catalina conf. and this looks like this: 



  <Service name="Catalina">

 

    <Connector port="8080"

               maxThreads="150"

               minSpareThreads="25"

               connectionTimeout="20000"

               enableLookups="false"

               maxHttpHeaderSize="8192"

               protocol="HTTP/1.1"

               useBodyEncodingForURI="true"

               redirectPort="8443"

               acceptCount="100"

               disableUploadTimeout="true"

               proxyName="jira.nibe.se"

               proxyPort="80"

               scheme="http"

               secure="false"/>

 

    <Engine name="Catalina"

            defaultHost="localhost"

            jvmRoute = "jiracluster">

 

      <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true">

 

        <Context path=""

                 docBase="${catalina.home}/atlassian-jira"

                 reloadable="false"

                 useHttpOnly="true">

 

          <Resource name="UserTransaction"

                    auth="Container"

                    type="javax.transaction.UserTransaction"

                    factory="org.objectweb.jotm.UserTransactionFactory"

                    jotm.timeout="60"/>

Please advise... 

2 answers

0 votes
Arthur Goncalves Atlassian Team May 01, 2018

Hi Joakim,

 

Which operations are returning a 502 error? This usually happens when the timeout period for the gateway exceeds. I would recommend you to check the Jira application logs to see if there are any traces of long running operations.

Hope this info helps!

 

Regards,
Arthur Gonçalves | Atlassian Support

0 votes
Gábor Simon Oct 24, 2018

For me the nodes could not start. The root cause was that I specified the username of the node VM as 'jira' - that conflicted with the username of the jira application linux user (also 'jira') .

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

12,538 views 61 59
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you