Error testing connection for Perforce repository - The authenticity can't be established
Problem
When attempting to setup a Perforce repository for the first time, the following appears in the Fisheye/Crucible UI:
Error testing connection.
Unable to get repository info: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | The authenticity of '10.10.10.10:1666' 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
44:81:E3:9B:12:3D:12:00:EE:AB:4D:C8:F6:DB:52:98:9C:61:B9:95
To allow connection use the 'p4 trust' command.
at com.cenqua.fisheye.perforce.client.P4Client.info(P4Client.java:83)
at com.cenqua.fisheye.perforce.P4ScmConfig.testConnection(P4ScmConfig.java:161)
at com.cenqua.fisheye.perforce.P4ScmConfig.testConnection(P4ScmConfig.java:154)
at com.cenqua.fisheye.RepositoryConfig.testConnection(RepositoryConfig.java:441)
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(DefaultRepositoryAdminService.java:845)
Connection failed.Cause
- The Perforce client has never connected to the Perforce server at 10.10.10.10 and does not trust it.
- If you are using ticket-based authentication you may have invalid outstanding tickets.
Resolution
As the user that runs the Fisheye/Crucible instance, run the following command to tell the Perforce client that this server is trusted:
p4 trust -i 10.10.10.10:1666 44:81:E3:9B:12:3D:12:00:EE:AB:4D:C8:F6:DB:52:98:9C:61:B9:95More information about the
p4 trustcommand line options can be found in Perforce documentation.Add a ticket to the user running Fisheye with a command like:
p4 -u fisheye_user login -a
The values above will need to be updated for what is displayed from the error message.
Last modified on Apr 11, 2022
Powered by Confluence and Scroll Viewport.