Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

SCP identity agent key invalid problem Edited

I am getting below error while coping some files with scp task


2018-03-21 07:19:00,116 INFO [17-BAM::Default Agent::Agent:pool-32-thread-1] [TransportImpl] Client identity string: SSH-2.0-SSHJ_0.21.12018-03-21 07:19:00,182 WARN [17-BAM::Default Agent::Agent:pool-32-thread-1] [IdentificationStringParser] Server identification has bad line ending, was expecting a '\r\n' however got: '2' (hex: 32)2018-03-21 07:19:00,183 WARN [17-BAM::Default Agent::Agent:pool-32-thread-1] [IdentificationStringParser] Will treat the identification of this server 'SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u2' leniently


This error started getting after changing remote server without changing IP.

1 answer

Simon says:

On your remote SSH server (the one that is the destination of the copy operation) configuration set the following option:


DebianBanner no


and restart the remote SSH server. This will transform the SSH banner to  SSH-2.0-OpenSSH_7.4p1.

On some other distribution you may have to use instead the option:


VersionAddendum none


in the SSH server configuration on the remote host.


Cheers, Simon out.

Hello Simon, I tried both but not work for me. The result is the same.

Jeyanthan I Atlassian Team Mar 31, 2018

Do you get the same error when you execute the scp command from the terminal as the same user outside Bamboo?

If it didn't error out, you may use the script task instead of scp task where you can define your scp command.

I used script instead of scp task. I guess scp task cache the ip addresses or ssh library of java cache the ip address. And the ip changed for same server. The scp task give this error interestingly.

Jeyanthan I Atlassian Team Oct 29, 2018

Ah, good catch. Thanks for sharing it here :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

223 views 4 6
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