need to p4 trust

This question is in reference to Atlassian Documentation: Perforce

Error testing connection.
Unable to get repository info: Unable to login: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The authenticity of '10.27.145.22:2110' can't be established, 
this may be your first attempt to connect to this P4PORT. 
The fingerprint for the key sent to your client is 
60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14 
To allow connection use the 'p4 trust' command. 

2 answers

1 vote

The credentials you have configured Fishey with are not correct for Perforce.  The mistake I usually make with Pp4 is forgetting to give it the right port, so check that.  Then check out what p4 trust tells you.

Yes, I am on the correct port.

p4trust has answered it - you haven't told the Perforce server that the Fisheye server is a friend.

Have a look at https://confluence.atlassian.com/fishkb/error-testing-connection-for-perforce-repository-the-authenticity-can-t-be-established-656409132.html

The command line in that article is wrong

p4 trust -l 10.10.10.10:1666 44:81:E3:9B:12:3D:12:00:EE:AB:4D:C8:F6:DB:52:98:9C:61:B9:95

They probably mean to use -i instead of -l. That is what I did to add the entry for the server referenced.

I ran the "p4 -u username login -a" command, but the behavior is still the same.

My understanding is that this isn't really a Perforce or Atlassian issue, this is lower-level networking software saying "we're not sure that we should trust that the machine that you asked to connect to is actually the one you reached, there might be some sort of man in the middle attack going on".  

First, you need to decide whether or not you trust that you're reaching the right machine.

Then, from the machine where the Atlassian tool will be running, manually connect to Perforce using a command line or GUI tool.  You should see this same kind of error, but be given the opportunity to say that you want to trust that fingerprint permanently.  Disconnect and reconnect; you should not see the error any more, and the Atlassian tool should be able to run without this issue.

I added the fingerprint manually from a command prompt on the same machine.

Here is a list of the fingerprints.

C:\_code\iafw-manifest>p4 trust -l
10.219.38.103:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.27.145.22:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.82.195.15:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.96.65.27:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.239.29.32:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
143.182.228.129:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14

I still get this error.

Unable to initialise repository Client_Skylake_2015 due to com.cenqua.fisheye.config.ConfigException:Problem communicating with repository : Unable to get repository info: Unable to login: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The authenticity of '10.27.145.22:2110' can't be established, this may be your first attempt to connect to this P4PORT. The fingerprint for the key sent to your client is 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14 To allow connection use the 'p4 trust' command.

Those code blocks don't seem to work.

C:\_code\iafw-manifest>p4 trust -l
10.219.38.103:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.27.145.22:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.82.195.15:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.96.65.27:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
10.239.29.32:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14
143.182.228.129:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14

and...

Unable to initialise repository Client_Skylake_2015 due to com.cenqua.fisheye.config.ConfigException:Problem communicating with repository : Unable to get repository info: Unable to login: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The authenticity of '10.27.145.22:2110' can't be established, this may be your first attempt to connect to this P4PORT. The fingerprint for the key sent to your client is 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14 To allow connection use the 'p4 trust' command.

You're into territory I've never visited, so sorry, I can't be of more help here.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Marketplace Apps

Tips on how to choose the best estimation method for your planning

Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...

72 views 0 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you