Getting 502 Bad Gateway error while trying to upload packes via curl from Jenkins | Community
Skip to main content
Level 2
January 27, 2020
Solved

Getting 502 Bad Gateway error while trying to upload packes via curl from Jenkins

  • January 27, 2020
  • 2 replies
  • 5241 views

Hi All,

 

Am trying to implement the Continuous integration from Jenkins and while trying to install the package to the package manger(AEM 6.4) via the below command, we are getting 502 - bad gateway error.

 

Command:

curl -u ****:**** -F package=@/var/jenkins_home/workspace/package.zip https://www.site.com/crx/packmgr/service/.json/?cmd=upload -F force=true

Response:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
</body></html>

Do i need to tweak something in the  Dispatcher configuration? Can someone please help me on how to approach this issue?

Best answer by user05162

If you replace "https://www.site.com" with the actual IP of AEM instance(bypassing dispatcher), does the issues get resolved? If yes, the issue lies with the dispatcher.

2 replies

user05162Adobe EmployeeAccepted solution
Adobe Employee
January 27, 2020

If you replace "https://www.site.com" with the actual IP of AEM instance(bypassing dispatcher), does the issues get resolved? If yes, the issue lies with the dispatcher.

October 15, 2020

Why is this marked as solved, if there isn't a single comment or answer....