Hey, not sure if this is the right place to report, but the login to the GNOME Gitlab is having problems this morning (as Mo reported in #gnome on Libera) and tested myself and having the same problem
500: We’re sorry, something went wrong on our end
Request ID: 01JCZ1GR8BY5S4X1J782E6XKPZ
Try refreshing the page, or going back and attempting the action again.
Please contact your GitLab administrator if this problem persists.
GNOME gitLab is having issues since the weekend.
Retrying the request seems to work after few attempts.
znalo
also ‘problems’ fetching issues and merge requests according to alert at top of pages for non-logged in users.
We’re likely getting hit by another wave of web scrapers for AI training, which is causing issues on the back end of the GitLab UI.
This is well known: we aggressively rate limit non-logged in users because that’s what a lot of automated scraping comes from.
Duplicate of 500 returns on GNOME GitLab requests (#1794) · Issues · Infrastructure / Infrastructure · GitLab.
I’m having the same issue. No matter how much I retry I cannot log in.
I think 2FA/Passkey is interfering with my ability to retry. Since I have to go through verification, I cannot simply “retry” the request, as the passkey or 2FA code are invalidated after the first attempt. Refreshing with passkey continues to return Error 500. Refreshing with 2FA code results in an email about an incorrect 2FA code.
This effectively prevents login.
Getting 5xx when git pulling glib, gnome-software etc.
$ git pull
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: expected flush after ref listing
$ git pull
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: expected 'acknowledgments'
Accessing via Web browser works fine. So, probably issue with SSH (22) service.
Actually the HTTPS interface doesn’t work, but SSH works fine.
$ git clone https://gitlab.gnome.org/GNOME/gnome-software.git
Cloning into 'gnome-software'...
error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
fatal: expected 'packfile'
$ git clone git@ssh.gitlab.gnome.org:GNOME/gnome-software.git
Cloning into 'gnome-software'...
remote: Enumerating objects: 83533, done.
...
I seem to have the same issue. I was able to reset the password but I get 500 error with Request ID: 01JD9HZHVVEWBFZJ4AMCGPX7NR when I try to login.
I would report this to the Issues · Infrastructure / Infrastructure · GitLab , but when I try it just returns 500 and good bye. Hence I’m here.
When I try to add a comment into an issue (for example to this one: Autocrypt header uses wrong email address (#2905) · Issues · GNOME / evolution · GitLab), I only get a red banner above the comment box saying “Your comment could not be submitted! Please check your network connection and try again.”. Please check your connection thus I could try again.
This is getting worse and worse during the week (or more?).
I encountered the same problem.
When I attempt to:
Comment the undermentioned markup at gitlab.gnome.org/GNOME/gimp/-/issues/7413:
@Jehan, what you're saying fundamentally doesn't make sense — imagine if GIMP bundled XTerm on Linux-based OSes, instead of using GNOME Terminal or Konsole! However, when in `cmd.exe`, specifically:
1. Their font preferences shall not be respected.
1. Duplicating text into the clipboard is more difficult.
1. The launch size overrides shall not be respected.
…Or comment the undermentioned markup at gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/1799:
> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/1799#note_ffe6c1409c13150014148da29da338659405c7e7
Incredibly, although it failed 6 times in a row, leaving it for 30s appeared to work.
…I see the undermentioned quote:
Your comment could not be submitted! Please check your network connection and try again.
Additionally, as the 1st aforereferenced bug states, I am occasionally unable to modify issue descriptions. Summarily, I see the undermentioned quote:
Error updating issue. Request failed with status code 500
Coincidentally, I’m seeing Unable to edit comment - timeline error is displayed. · community · Discussion #145307 · GitHub too… Could there be something which your instance of GitLab shares with GitHub, whose performance is degraded?
Those comments of mine were transferred into this thread. Irrespective, this has been remediated, per Unable to update issue description. (#1799) · Issues · Infrastructure / Infrastructure · GitLab.
Having multiple threads covering the exact same thing isn’t really conducive to a good experience on a discussion forum. We have known transient issues with GitLab that are going to be mitigated by the planned migration.
Yeah, it’s not a criticism, @ebassi; needn’t explain. I mentioned it because because unlike other Discourse instances, this one doesn’t indicate when a thread has been merged, so they might have seemed chronologically redundant. Thanks though.
This seems resolved for me now.
@cheywood, aye - me too.
Well, that could be just a bright Saturday. I cannot add comments again. Opening “Commits” tab in a merge request results (after several seconds) into:
Error 503 No healthy backends
No healthy backends
Error 54113
Details: cache-vie6360-VIE 1732523232 2555364406
Varnish cache server
and the https://status.gnome.org/ lies about “All systems are operational.”. I’d really like to do my job again, but I cannot even release a software, because of these recent problems. I do not recall seeing the infrastructure such buggy for a decade, it was always rock solid, with some rare exceptions, but what it does for the past weeks… Wherever the infrastructure went, it feels backward. I’m sorry.
Quoting from Ebassi’s post above:
We’re likely getting hit by another wave of web scrapers for AI training, which is causing issues on the back end of the GitLab UI.
IIUC,
Infrastructure team is active on matrix room '#infrastructure:gnome.org', but regular updates in GNOME Discourse would be helpful too.