Unable to establish connection from domain --> Dispatcher --> Render ..502 Bad Gateway | Community
Skip to main content
gurup34365977
gurup34365977
Level 2
February 26, 2020
Solved

Unable to establish connection from domain --> Dispatcher --> Render ..502 Bad Gateway

  • February 26, 2020
  • 3 replies
  • 5183 views

Hi Team,

We are using Apache version 2.4 with dispatcher 4.3.3 version. Configured dispatcher.any, httpd.conf,http_Vhost.conf, when we are accessing from dispatcher I am able to get response from renderer. But when we are accessing from domain i am getting 502 bad gateway. In dispatcher.log response status coming as 400. Please help me on the same. 

When accessing from dispatcher find logs

 

Wed Feb 26 09:40:16 2020] [D] [pid 26772] Render-ID in cookie detected: rend01

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Found farm author for rnse2-usst-lweb01.rno.com:21100

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] checking [/bin/healthchecktype=external]

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] request URL has no extension: /bin/healthchecktype=external

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] cache-action for [/bin/healthchecktype=external]: NONE

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Creating new connection: rns2-usst-lapp03.rno.com:8443

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Connected to backend rend01 (rns2-usst-lapp03.rno.com:8443)

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Host

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Cache-Control

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Upgrade-Insecure-Requests

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: User-Agent

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Sec-Fetch-Mode

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Sec-Fetch-User

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Accept

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Sec-Fetch-Site

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Accept-Encoding

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Accept-Language

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Cookie

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Via

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: X-Forwarded-For

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: X-Forwarded-SSL

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: X-Forwarded-SSL-Cipher

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: X-Forwarded-SSL-Session-ID

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: X-Forwarded-Port

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Adding request header: Server-Agent

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] response.status = 200

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] response.headers[Date] = "Wed, 26 Feb 2020 09:40:16 GMT"

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] response.headers[X-Content-Type-Options] = "nosniff"

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] response.headers[X-Frame-Options] = "SAMEORIGIN"

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] response.headers[X-Powered-By] = "Jetty(9.4.15.v20190215)"

[Wed Feb 26 09:40:16 2020] [D] [pid 26772] Storing socket for later reuse: rns2-usst-lapp03.rno.com:8443

[Wed Feb 26 09:40:16 2020] [I] [pid 26772] "GET /bin/healthchecktype=external" 200 none [author/rend01] 48ms

 

 

when we are accessing from domain it is capturing following logs

 

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Found farm author for accp-sh-uat.rno.com

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] checking [/bin/healthchecktype=external]

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] request URL has no extension: /bin/healthchecktype=external

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] cache-action for [/bin/healthchecktype=external]: NONE

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Reusing connection: rns2-usst-lapp03.rno.com:8443

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Connected to backend rend01 (rns2-usst-lapp03.rno.com:8443)

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: Host

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: x-shield-req-id

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: User-Agent

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: Via

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: X-Forwarded-For

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: X-Forwarded-SSL

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: X-Forwarded-SSL-Cipher

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Adding request header: Server-Agent

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] response.status = 400

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] Setting sticky connection to rend01

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] response.headers[Set-Cookie] = "renderid=rend01; path=/; secure"

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] response.headers[Cache-Control] = "must-revalidate,no-cache,no-store"

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] response.headers[Content-Type] = "text/html;charset=iso-8859-1"

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] response.headers[Content-Length] = "2078"

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] response.headers[X-Powered-By] = "Jetty(9.4.15.v20190215)"

[Wed Feb 26 09:40:16 2020] [D] [pid 2797] No socket reuse: backend asks to close connection

[Wed Feb 26 09:40:16 2020] [I] [pid 2797] "GET /bin/healthchecktype=external" 400 none [author/rend01] 2ms

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by joerghoh

    The error is created on AEM side, so you check the logs there.

    * The request.log on that publish instance should log this request with the response code 400 as well.

    * Check the error.log if there is any trace for that request.

     

    What code is behind this /bin/healthchecktype=external request? I am quite sure that it is not AEM ootb functionality.

    3 replies

    H
    Adobe Employee
    Hamid1350Adobe Employee
    Adobe Employee
    February 26, 2020

    Please check the following document where the steps to use dispatcher with multiple domains is explained:

    https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-domains.html#define-virtual-hosts-on-the-web-server

    gurup34365977
    gurup34365977Author
    Level 2
    February 26, 2020

    Hi Hamid, Thank you for your quick response. I have followed the same documentation. But no luck. Please suggest me any other options.

     

    Note that I am able to establish request from dispatcher to renderer but unable to establish from domain via dispatcher to appserver.

    joerghoh
    Adobe Employee
    joerghohAdobe EmployeeAccepted solution
    Adobe Employee
    February 29, 2020

    The error is created on AEM side, so you check the logs there.

    * The request.log on that publish instance should log this request with the response code 400 as well.

    * Check the error.log if there is any trace for that request.

     

    What code is behind this /bin/healthchecktype=external request? I am quite sure that it is not AEM ootb functionality.

    gurup34365977
    gurup34365977Author
    Level 2
    June 2, 2020

    Hi All,

     

    It's been resolved. SSL certification issue.

     

    Regards,

    Guru Pavan

      Terms & ConditionsAccessibility statement

      Loading footer...