After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781445 - Intermittent 500 errors from id.gnome.org
Intermittent 500 errors from id.gnome.org
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Patrick Uiterwijk
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2017-04-18 11:23 UTC by Sam Thursfield
Modified: 2018-02-21 11:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sam Thursfield 2017-04-18 11:23:19 UTC 
There are regular reports of 500 errors for people using https://id.gnome.org/ to log into https://registration.guadec.org/. The error disappears when the user retries, at least in some cases.

Apologies for filing this bug against the wrong component -- there isn't an id.gnome.org component available.
Comment 1 Andrea Veri 2017-04-18 12:19:29 UTC 
Patrick, can you please have a look?
Comment 2 Sam Thursfield 2017-04-24 12:07:06 UTC 
At least one person is reporting that this is a persistent issue that prevents them from using the service altogether.
Comment 3 Sam Thursfield 2017-04-24 12:13:45 UTC 
They attempted to log in several times on Saturday 22nd and Sunday 23rd, if that helps in searching log files
Comment 4 Patrick Uiterwijk 2017-04-24 12:17:27 UTC 
Please note that April 21 - April 23 several systems were impacted by a very broad outage.

If they are still having this problem, I would much appreciate it if they can either join #sysadmin on gimpnet and ping me, or provide their username.
Without that information, there's not a lot I can begin if it's consistent.
Comment 5 Patrick Uiterwijk 2017-04-24 12:43:07 UTC 
The issue with the specific person mentioned by Sam should be fixed.
The general instability should be fixed with the new upstream release that I hope to bring live very soon.
Comment 6 Andrea Veri 2018-02-21 11:24:11 UTC 
This should be fixed by now (we updated the ipsilon* packages to version 2.1 which included a fix for the reported problem).