I can't reproduce this. Here are the repository policies:

Here's the repository detail screen:

Here's a clone working fine:

$ git clone ssh://local@localvault.phacility.com/diffusion/45/newer-hosted-git.git local-clone
Cloning into 'local-clone'...
# Fetch received by "local001.phacility.net", forwarding to cluster host.
# Waiting up to 120 second(s) for a cluster read lock on "local001.phacility.net"...
# Acquired read lock immediately.
# Device "local001.phacility.net" is already a cluster leader and does not need to be synchronized.
# Cleared to fetch on cluster host "local001.phacility.net".
remote: Counting objects: 3, done.
remote: Total 3 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (3/3), done.
Checking connectivity... done.

Any idea what I can do differently to reproduce the issue?

I cannot change the Space by default

I can reproduce this, I'll make a note on T10923. See also T10922.

The difference with our interface : I have not installed "http git" only ssh git

Any idea what I can do differently to reproduce the issue?

Where can I find the log about this message on the server ?

The difference with our interface : I have not installed "http git" only ssh git

You are the only one who can reproduce the issue, so you need to provide valid reproduction steps which we can follow to reproduce the issue.

If you think HTTP being enabled is the critical difference between our environments, enable HTTP operations on your server, verify that this fixes the problem, then update the reproduction steps to include this information. We don't have the resources to debug this by going back and forth. See Providing Reproduction Steps.

Where can I find the log about this message on the server ?

There are no additional logs generated for policy errors.