Legit login attempts yield, "An error occurred while processing your request."
Hi friends.
Following up on my message over the weekend about getting web (Django) logins for users who were ported from MM2 to MM3, I now have some people trying to create a new username.
Something broke following a system update and reboot. MM3 is installed using the venv method, and the services (mailman and mailman-web) seem to be running ok. Mailing list delivery is happening as usual.
I've now come upon a few related situations where a 500 error results, "Server error. An error occurred while processing your request."
My primary question is: *How can I find out what's causing this*?
I've looked in all the MM and web logfiles, by "tail -f" while generating the error, and nothing is logged there. Apache logs shows something like this:
x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0"
I've come across this error while trying to do authentication-related activities that worked before the reboot: the address (might not be the same problem)
- "Forgot password" (happens whether or not the entered email existed in MM2 or already exists in MM3)
- Sign up (ditto)
- Email unsubscribes gave a verification email, but then didn't unsubscribe
Thanks for any breadcrumbs that might guide me to the solution. ~ Greg
On 8/14/24 3:18 PM, Greg Newby wrote:
My primary question is: *How can I find out what's causing this*?
I've looked in all the MM and web logfiles, by "tail -f" while generating the error, and nothing is logged there. Apache logs shows something like this:
x.x.y.y- - [13/Aug/2024:21:46:41 -0700] "POST /accounts/password/reset/ HTTP/1.1" 500 1448 "https://lists.pglaf.org/accounts/password/reset/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36 Edg/127.0.0.0"
This is django-allauth. Errors should be logged in Django's log which, if yoiu followed our virtual env install doc is /opt/mailman/web/logs/mailmanweb.log.
I've come across this error while trying to do authentication-related activities that worked before the reboot:
Did django-allauth get upgraded to >=64.0. There are currently issues with that. It should be >=0.63,<64.0.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Greg Newby
-
Mark Sapiro