Broken pipe when attempting to publish artifact

[David Schlesinger]

I'm attempting to publish an artifact from my remote agent to bamboo (version 5.5.1) using bamboo's artifact publisher. The build completes correctly up until the artifact publish step.

I have been seeing the following error (taken from the remote agents logs):

Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe

I can't seem to find any information on what would cause this error.

Thanks

[Przemek Bruski · Accepted solution]

Which URL does your agent use? If it's the reverse proxy URL, you may want to point directly at Bamboo's Tomcat URL.

[David Schlesinger]

It's a reverse proxy URL (running Nginx) and actual bamboo is on localhost. It would require a lot of configuartion changes otherwise.

Is it unusual to run bamboo behind a proxy? I seems like this would be a very common issue.

[Przemek Bruski]

It's not unusual. But you won't find out if it's an issue with the proxy unless you reconfigure. Nginx versions quite often doesn't support full HTTP/1.1 . Some configuration options may prevent hte publishing from working too.

How about installing a different proxy then? For example, Apache?

[Daniel Wester]

You can use nginx (I've done it) - I believe that the issue is that nginx strips out the Content-Length so you'll need to allow that header through. Your best bet would be to take a look at the nginx error logs and the bamboo server logs at the same time. One of them should tell you which header is missing.

[David Schlesinger]

I managed to fix the issue by pointing directly to http://brokerURL:8085/agentServerrather then https://brokerURL/agentServer

Thanks for the help.

[Razvan Grigore]

If you want to keep your nginx reverse proxy, like we did, because of SSL offloading, you need to add this to your config:

client_max_body_size 1G;

The size depends on the artifacts size you have.