How to fix authentication error with Perforce server on horde server based on docker-compose

Development Getting Started & Setup
,
1

Hi!

I’ve set up a Horde server in Docker Compose and configured p4 with:

p4 configure set ssl.client.cert.validate=2
p4 configure set ssl.client.trust.name=0

but still can’t manage this error:

horde-server-1 | [14:46:03 wrn] Failed checking Perforce server health via info command. Reason Failed: The authenticity of ‘ssl:ipofserver:1666’ can’t be established,
horde-server-1 | this may be your first attempt to connect to this P4PORT.
horde-server-1 | The fingerprint for the key sent to your client is
horde-server-1 | fingerprint here
horde-server-1 | To allow connection use the ‘p4 trust’ command. (Generic=Comm)

I tried exec into container, but p4 doesn’t work there directly, tried also put some commands in docker-compose but without effect as well.

I’m unsure how to bypass this p4 trust command. Any suggestions?

2

To repair authentication mistakes with the Perforce server on a Horde server based totally on Docker Compose:

  1. Verify the Docker Compose configuration.

  2. Check Perforce server settings.

  3. Test Perforce server connectivity.

  4. Review the horde configuration.

  5. Examine error logs for clues.

  6. Update Docker pix and dependencies.

  7. Consult documentation and neighborhood resources.

  8. Test unique authentication mechanisms.

  9. Check firewall and networking settings.

  10. Seek an expert guide if needed.

3

Hi Muata,

I am also using the default docker-compose.yml (5.4) and had the same issue.

I am not sure what the right way would be, but the following worked for me.

What I have done is to run ‘p4 trust’ in my host machine. Not inside the container, as you said p4 command is not available there.

If the fingerprint is the right one and to be trusted, accepting it creates a p4trust.txt (or .p4trust) file in your user directory.

Just copy this p4trust file into your horde-server docker container, inside the root home directory (/root). So you should have a file /root/.p4trust

If you restart the server, perforce should now be healthy.

Hope it helps.

// If anyone has a better idea on how this should be better handled, it would be very welcome to ehar about it.

2 Likes
4

Thanks a lot.

5

Hello,

I’m encountering the same issue where the P4 trust is already established on the agent, but when running through Horde, it prompts for the trust again. Did you encounter it and solve?

6

I am getting the same error on UE5.4, even though the trust file definitely has the entry present.

I was first getting it on the agent when running a build, but somehow, while trying to fix this, I’ve broken the server too, which no longer can connect to Perforce, despite me trying everything I can think of to ensure the trust file is correct.

NOTE: this is using the Horde installer, not the Docker container.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.