I'm trying to manage the freeipa-users mailing list subscription requests at https://lists.fedoraproject.org/admin/lists/freeipa-users.lists.fedorahosted.org/subscription_requests and after a lengthy timeout it consistently returns a 500 error:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
I've been seeing this since 12pm EST yesterday.
This is not urgent as users can still subscribe (one did this morning). But it would be nice to eventually be able to manage things.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation
FWIW it is still throwing a 500 error.
I tried to login and got 504, which seems to be related to https://pagure.io/fedora-infrastructure/issue/11682
Hey, I fixed a login issue on Ipsilon just now. I don't think it was the root of the issue, I'm guessing the problem is that the list returned by the mailman REST API is so long that the frontend (Postorius) times out, but that's just a guess.
Can we perhaps just increase that timeout?
@kevin I think that could probably help, but I'm not sure how much we should add to timeout. Probably we need to try something and see if that helps.
Quick update: I tried this just now and was hit with a 403 which I thought may be due to my VPN, however even without it this service still seems to return a 403.
Also upon inspecting the network requests there is 1.83s response time from the server which suggests it is still working very slowly. Firefox is stating anything above 500ms is a timeout.
<img alt="Screenshot_from_2024-05-02_11-11-38.png" src="/fedora-infrastructure/issue/raw/files/1630ce50aa736570ce41da7f539355a38d75b8cf5a5bc78a72b1552a2adec4b1-Screenshot_from_2024-05-02_11-11-38.png" />
Login to comment on this ticket.