#11793 Issues with logging in (500 Internal Server Error)
Closed: Fixed with Explanation 3 months ago by zlopez. Opened 3 months ago by mrc0mmand.

Hey!

For the past couple of minutes I've been trying to log in into our Weblate interface, but even though I'm pretty sure I'm entering the correct password every attempt ends with "Authentication failure". However, when trying to log in directly through https://accounts.fedoraproject.org/, I get a slightly more informative message:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>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.</p> <p>More information about this error may be available in the server error log.</p> </body></html> 

So it looks like there's something wrong with the auth server(s).


kinit is failing as well.

[4162580] 1708952570.214063: Received error from KDC: -1765328324/Generic error (see e-text)
kinit: Generic error (see e-text) while getting initial credentials

Similarly, can't get a ticket:

$ kinit -V pghmcfc@FEDORAPROJECT.ORG
Using existing cache: 1000
Using principal: pghmcfc@FEDORAPROJECT.ORG
kinit: Generic error (see e-text) while getting initial credentials

kinit is failing as well.

[4162580] 1708952570.214063: Received error from KDC: -1765328324/Generic error (see e-text)
kinit: Generic error (see e-text) while getting initial credentials

Just came to say the same thing.

The issue is probably caused by ipa01 server running out of space. @darknao is currently trying to find out what could be deleted and will restart the ipa service.

Metadata Update from @zlopez:
- Issue priority set to: None (was: Needs Review)
- Issue tagged with: high-gain

3 months ago

kinit just worked for me now.

The issue is now resolved, closing this ticket.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

3 months ago

Issue status updated to: Open (was: Closed)

3 months ago

Metadata Update from @zlopez:
- Issue tagged with: low-trouble, ops

3 months ago

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

3 months ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog