In order to make several improvements to our infrastructure the Git SSH domain of our Gitea instance will be moved from projects.blender.org to git.blender.org.
On July 1 2025 projects.blender.org stops working as Git SSH remote
Read all the instructions below to see how you can resolve issues before the switchover.
To be able to keep using Projects via Git, please change your local remotes to use this new domain.
In the main blender repository, we’ve added functionality to make update that will automatically convert your local git remotes to the right ones.
In other cases, the steps below will most likely suffice:
The example below uses the origin remote and the repository blender/blender. Obviously, for other repositories or remotes you would need to use their respective values:
Open your terminal and change your directory to the root of your repository
Be aware that on the next time you interact with this new remote via Git you will be prompted to accept the server’s key fingerprint again under this domain name. This will look as follows:
The authenticity of host 'git.blender.org (2a01:4f8:2191:3457::2)' can't be established.
RSA key fingerprint is SHA256:ny+vcWlA5GVdVJFduVmBIyCthgqmNAXdNShi/QSv//U.
This host key is known by the following other names/addresses:
~/.ssh/known_hosts:10: projects.blender.org
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Note: It might say git.blender.org (168.119.195.207) when you are connecting via IPv4
1. Why am I receiving a REMOTE HOST IDENTIFICATION HAS CHANGED! warning?
If you get the message below, you should not panic.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:ny+vcWlA5GVdVJFduVmBIyCthgqmNAXdNShi/QSv//U.
Please contact your system administrator.
Add correct host key in /home/<user>/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/<user>/.ssh/known_hosts:1
remove with:
ssh-keygen -f '/home/<user>/.ssh/known_hosts' -R 'git.blender.org'
Host key for git.blender.org has changed and you have requested strict checking.
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Blender has a history of using different version control management systems. If you were contributing to Blender in the time when Phabricator was used, you might get this message. In that case, it’s safe to follow the instructions given to remove this fingerprint from your known_hosts file using:
For users that have Pageant/plink setup on windows for auth, when you pull with git the first time, it may ask you accept the new host key, but it won’t take any keyboard input… (yeah, i got nothing there) and get stuck, to work around that issue, run plink [email protected] once and accept the key and you should be good to go after that!
Also, I used the following script to change all remotes of all repos on my system:
#!/usr/bin/env bash
# Use current directory if no argument is provided, otherwise use the first argument
BASE_DIR="${1:-$(pwd)}"
# Find all directories containing a .git folder
find "$BASE_DIR" -type d -name ".git" | while read -r gitdir; do
repo_dir=$(dirname "$gitdir")
echo "Checking repo: $repo_dir"
cd "$repo_dir" || continue
# Get all remote names and URLs
git remote -v | while read -r name url _; do
# Check for the specific pattern
if [[ "$url" =~ ^git@projects\.blender\.org:([^/]+)/([^/]+)\.git$ ]]; then
org="${BASH_REMATCH[1]}"
repo="${BASH_REMATCH[2]}"
new_url="[email protected]:${org}/${repo}.git"
echo "Updating remote '$name' in $repo_dir"
git remote set-url "$name" "$new_url"
fi
done
done
As far as I know it’s for when people clone the repository from our GitHub read-only mirror to make sure they retrieve any missing Git LFS objects from the correct remote.
The way we handle/recommend remote naming is… confusingly annoying at best.
AFAIR, make update supports both cases:
‘github’-type, origin is own fork, upstream is git.blender.org:blender.
‘blender’-type, origin is git.blender.org:blender, me is own fork…
So I would rather recommend something more generic in that hook message, something like that:
*********************************************************************************
* IMPORTANT NOTICE *
* Blender Projects is moving its Git SSH domain to git.blender.org! *
* If you haven't already, please update your Git remotes to use the *
* [email protected] host instead of the [email protected] one. *
* *
* More information: *
* https://devtalk.blender.org/t/blender-projects-is-moving-its-git-ssh-domain-to-git-blender-org/41098 *
*********************************************************************************
Users who need more detailed explanations and instructions can follow the link to the devtalk post.
On July 1 2025
