Unable to build 4.27 from source: Setup.bat 403 forbidden error.

After pulling branch 4.27 from source, running Setup.bat gives me the following error:

Checking dependencies...
Updating dependencies:   0% (3/10656), 0.7 MiB cached...
Failed to download 'http://cdn.unrealengine.com/dependencies/UnrealEngine-16624087/135d2dfcfa4bbe7dd725f03f844323624525ed4a': The remote server returned an error: (403) Forbidden. (WebException)
Press any key to continue . . .

I’ve tried every fix under the sun for this one; I’ve turned off firewall and windows defender, I’ve changed the link url in commit.gitdeps to use https, made sure the path doesn’t have any spaces, and moved the folder to somewhere with a shorter file path. Nothing I do is working, and the file is inaccessible in my browser.

Begging for help, I’ve never had an issue using the source build before now.

is the server down basically? just need to know…

If it’s down, it’s been down for several days

Okay, Staff made a post about this issue- Upcoming Disruption of Service Impacting Unreal Engine Users on GitHub

OK, I’m seeing this error as well for all 4.24 versions. bing AI brought me to this upload, and I found a fix - this error is coming from this file: Engine/Build/Commit.gitdeps.xml
Just be sure to download the xml file for your release tag.

1 Like

Hi mschifer,
Could you provide me the xml file for 4.24 or guide me how to downlad for 4.24 version?
Thanks!

Hi debipe,
Did you end up getting the 4.24 xml file?
If you did, can you provide me with it please?
Thanks.

watch this video https://www.youtube.com/watch?v=bOCO3W_Zb3Y

5 Likes

Just got to :

https://github.com/EpicGames/UnrealEngine/releases/download/{your_version}-release/Commit.gitdeps.xml

it should look like this for 4.25.0 : “https://github.com/EpicGames/UnrealEngine/releases/download/4.25.0-release/Commit.gitdeps.xml

and put the downloaded “Commit.gitdeps.xml” in the “Root\Engine\Build” folder.

You should be ready to relaunch the “setup.bat” !

8 Likes

Thank you so much, it works as you said. You’re the man.

1 Like

Thank you, DiabloFox. I was just about ready to panic, but this fixed it immediately.

1 Like

I had this error because I was switching to the 5.0-5.1 tag but it seems these tags don’t update when fixes like these are pushed so the fix for me was to switch to the 5.0 branch which includes additional fixes.

Truly many thanks