An error occurred while fetching folder content

I can log into gitlab.com using a browser - no issues. I can view the list of projects. But when I click on a project to view it, the error appears “An error occurred while fetching folder content.” and I can’t view any files.

I can create a new project, but then when I go to view it as described above, I get the same error.

I don’t believe that I’ve made any changes that would affect this (eg proxy, web connection, etc).

UPDATE: Different browsers on different machines give the same result - files in a project cannot be viewed.

image1110×782 23.1 KB

I am having the exact same problem. Tried different browsers and all easy solutions as above.

I’m having this issue as well. I had it a few weeks ago and it seemed to just eventually resolve itself. I think it’s an issue Gitlab is having with their service.

Interestingly, the ‘search’ function at the top of the gitlab banner works to get to a certain piece of code… but not to a certain branch.

Hey @ngeorgas, @the_aia, and @bakerc, welcome to the GitLab Community Forum!

We believe this might be a symptom of one of (1, 2) the incidents that we’re currently wrangling on GitLab.com. I’d keep an eye on those and let us know if you’re still seeing the issue once we’re declared the all clear on both.

@tristan, it seems that one of the two issues you noted is resolved (?) but still not able to get to branches.

The situation has resolved. I checked for incidents before posting but did not see any. It’s good to know that the GitLab team was on it.

Unfortunately, the situation has not resolved for me. I am still getting this.

image1670×158 8.19 KB

I’m still getting this today as well.

I’ve had this problem related to my own login issues, see this forum thread:

We are experienceing the same issue for some users with our Gitlab CE. We upgraded from 12.10 to 13.1 last week.

UPDATE: It does work in Firefox but not with the new Edge Browser or via git clone in WSL or inside a Docker Container.

@ngeorgas @arcandio As GitLab.com users, are you still seeing this issue?

I am not, personally, but I’ve not been on Gitlab as much the past few days.

No, not for the past week or so.

I am having this issue as well.
Started today - was fine yesterday. Can no longer access repo through git either - not sure if that issue is related.

Some users are having the same error on omnibus instance after upgrade to 13.12.3.
The content of the page is not fully loaded.

13.12.1 works for us, 13.12.2 or 13.12.3 don’t.

We’re running Gitlab CE in a VM, and we always take snapshots before upgrades - this has saved us several times during the last few weeks.

We are on 13.12.0 (haven’t tried 13.12.1), but upgrading to 13.12.2 through 13.12.4 doesn’t work. We are also running Gitlab in a VM and have to roll back the snapshot.

I report that I also have this problem. When trying to upgrade from version 13.12.1 to either version 13.12.2, 13.12.3 or 13.12.4, it gives the same problem reported in this thread.

Same issue here, after upgrading to 13.12.4. Has anyone created a issue about this?