need to p4 trust
Asked by Chip Ueltschey:

*This question is in reference to Atlassian Documentation: [Perforce](https://confluence.atlassian.com/pages/viewpage.action?pageId=298976886)*

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.


Answers:
author: Corey Shay
body: Did anyone ever solve this issue? I'm getting the same problem. I add the fingerprint via p4 trust, verify that it exists, but still get the same message when testing the connection. I suppose this means I won't be purchasing the full license if the product is useless.

Might be worth noting that the FishEye instance and the P4 server are on the same machine, so I'm just using ssl:localhost:1666.


author: Topher Eliot
body: 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.

comments: author: Chip Ueltschey
body: I added the fingerprint manually from a command prompt on the same machine.

Here is a list of the fingerprints.

```
C:\_code\iafw-manifest&gt;p4 trust -l10.219.38.103:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:1410.27.145.22:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:1410.82.195.15:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:1410.96.65.27:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:1410.239.29.32:2110 60:C3:0B:F9:18:CB:19:CB:81:96:F8:2A:96:EC:6A:15:08:DE:9F:14143.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.
```


author: Chip Ueltschey
body: 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.


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


author: Nic Brough -Adaptavist-
body: 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.

comments: author: Chip Ueltschey
body: Yes, I am on the correct port.


author: Nic Brough -Adaptavist-
body: 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>


author: Chip Ueltschey
body: 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.


author: Brian Clair
body: Had the same issue - here's what fixed it for me: Go into Windows Services and select Properties for Atlassian Fisheye. Click the Log On tab and under This account, use your own credentials (if you're on a domain, you'll need to navigate to your domain server to select yourself). Click OK out of that and then restart the service.


Tags: documentation

fisheye-crucible-administration