Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

502 Bad Gateway on traffic from https://px.ads.linkedin.com

Written By

Brian Suh

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • The browser console is showing a 502 Bad Gateway on traffic from https://px.ads.linkedin.com, specifically https://px.ads.linkedin.com/collect?v=2&fmt=js&pid={PID}&time={TIMESTAMP}&url={URL}

Environment

  • Liferay DXP 7.3, 7.4

Resolution

Please note that as this documentation identifies a problem stemming from a third-party technology, Liferay Support will be limited in its ability to provide assistance. For further guidance, please reach out to the vendor of the third-party technologies. This information is being shared on an informational basis to provide insight into this behavior.

  • The asset that is failing to load is related to a LinkedIn Insight tracker that is being introduced by a Google Tag Manager script. The 502 status code may indicate that the LinkedIn Insights functionality is enabled and not configured properly. To resolve this, you will need to review your Google Tag Manager settings to ensure that it the LinkedIn tag configuration is applied correctly.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?