The Unreal Engine GitHub integration on my Epic Games account remains stuck showing “Never used,” and access to the GitHub repository is now unavailable.
Until roughly a day ago, access was working normally with this same account. No changes were made on either Epic or GitHub during that time. The loss of access occurred suddenly without any user-side action.
When attempting to open the linked repository, GitHub displays its unicorn error page, which only appears when the authentication or linking process fails internally. This confirms that the issue originates from Epic’s side of the integration, not from GitHub or my account.
All account connections, permissions, and email associations have been fully verified and remain correct. There is no misconfiguration or permission issue on my side.
This is clearly an internal Epic-side authentication or cache consistency failure. Please investigate and resolve this issue promptly, as it currently prevents valid access to the Unreal Engine GitHub repository and disrupts ongoing development work.
I have spent all day to figuring out this issue, and I found that if I have successfully linked Epic account with github , and “EpicGames (Member)“ can be found in my github Organizations , then all any other issues are relative to Github settings other than EpicGames , Github’s authorization changed a lot this two year….
In Short , if you can’t browse EpicGames’s source repository , that’s NOT mean you can’t download them….
I gonna make a short video to record what I’v done for accessing unreal source code.
Multiple new Epic accounts, created over the past few days solely to test this issue, all cannot access Unreal Engine GitHub repositories.
Even when GitHub shows the Epic account as “Last used within the last week” in the account linkage status, access still fails.
Over 30 hours have passed since the initial access failure, no account can access anything.
Error is not 404 but “unicorn”, confirming this is clearly an internal Epic processing error, not a problem with my browser, cookies, or accounts.
Verified across multiple browsers, including freshly installed ones with all cookies and caches cleared; the issue persists in all cases. I see no fault on my side.
