Hi all,
https://lists.qno.de/mailman3 shows an internal server error.
I followed https://docs.mailman3.org/en/latest/install/virtualenv.html with MariaDB instead of PostgreSQL.
Python 3.13.0 pip 25.3 mailman 3.3.11b mailman-web 0.0.10.dev14?g0997bd postorius 1.3.13
Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi listens on [::1]:8000, apache2 is configured accordingly. Ports show up in netstat.
No errors show in logs.
If /mailman3 was a directory, i would have thought of user permission problems. But not with TCP ports.
As :8000 is available, i would have thought that there is a problem with uwsgi. Requests arrive there and are processed:
[pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0)
So uwsgi gets the request and delivers data. The problem seems that apache2 does not get the result, and i cannot find any reason. Any help?
TIA QNo
On Wed, Nov 5, 2025 at 1:44 PM Christian H. Kuhn via Mailman-users < mailman-users@mailman3.org> wrote:
Hi all,
https://lists.qno.de/mailman3 shows an internal server error.
I followed https://docs.mailman3.org/en/latest/install/virtualenv.html with MariaDB instead of PostgreSQL.
Python 3.13.0 pip 25.3 mailman 3.3.11b mailman-web 0.0.10.dev14?g0997bd postorius 1.3.13
Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi listens on [::1]:8000, apache2 is configured accordingly. Ports show up in netstat.
No errors show in logs.
If /mailman3 was a directory, i would have thought of user permission problems. But not with TCP ports.
As :8000 is available, i would have thought that there is a problem with uwsgi. Requests arrive there and are processed:
[pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0)
So uwsgi gets the request and delivers data. The problem seems that apache2 does not get the result, and i cannot find any reason. Any help?
What do you have in the log files for mailman, mailmanweb, and Apache2?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
Hi, sounds like an apache config problem. You might show your apache config and apache error log.
Regards, Andreas
On Mittwoch, 5. November 2025 11:44:32 CET Christian H. Kuhn via Mailman-users wrote:
Hi all,
https://lists.qno.de/mailman3 shows an internal server error.
I followed https://docs.mailman3.org/en/latest/install/virtualenv.html with MariaDB instead of PostgreSQL.
Python 3.13.0 pip 25.3 mailman 3.3.11b mailman-web 0.0.10.dev14?g0997bd postorius 1.3.13
Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi listens on [::1]:8000, apache2 is configured accordingly. Ports show up in netstat.
No errors show in logs.
If /mailman3 was a directory, i would have thought of user permission problems. But not with TCP ports.
As :8000 is available, i would have thought that there is a problem with uwsgi. Requests arrive there and are processed:
[pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0)
So uwsgi gets the request and delivers data. The problem seems that apache2 does not get the result, and i cannot find any reason. Any help?
TIA QNo
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message /4R6RER25GZLZW7XNWCXYFTGKUW5STBNH/
This message sent to andreas.vetter@uni-wuerzburg.de
-- Mit freundlichen Gruessen, Andreas Vetter
Stellv. IT-Bereichsmanager Fakultaet fuer Physik und Astronomie Tel.: +49 (0)931 31-82264
Informations- und Kommunikationstechnik Tel: +49 (0)931 31-85890
Ticketsystem: physik-it@uni-wuerzburg.de
Hi Andreas,
Am 05.11.2025 um 12:08 schrieb Andreas Vetter:
sounds like an apache config problem.
That was it. And the solution came from an info in the ssl.log: Module proxy was loaded, but it did not load the specific modules.
After activating proxy_uwsgi, access was possible.
KR QNo
On 11/5/25 02:44, Christian H. Kuhn via Mailman-users wrote:
Hi all,
https://lists.qno.de/mailman3 shows an internal server error.
The most common cause of this is an uncaught exception thrown in Mailman core.
No errors show in logs.
That's strange. There should be something. If it's a core error, it should be logged in /opt/mailman/mm/var/logs/mailman.log. Also, there is a Django log, probably at opt/mailman/web/logs/mailmanweb.log. Have you looked at those? Are they being written at all?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Andreas Vetter -
Christian H. Kuhn -
Mark Sapiro -
Odhiambo Washington