Dear Maintainer,

I recently installed mailman3-full to make the switch from mailman 2.x before it's being discontinued. While the installation was quite a hassle since both mailman3 and mailman3-web had severe issues talking to mysql I was eventually able to install them. Importing the mailing lists was also no problem, but the use of mailman3-web is.

At first I was at least able to open the web site, log in and confirm the admin mail adress after figuring out how to incorporate the automatically generated apache2 config into the previously used one, but the website kept telling me it was not able to connect to the REST API.

I have already tried quite a few solutions while talking to someone on the mailman3 mailing list [1] but nothing has worked so far to get the website work propperly. I have already posted all relevant config files and steps taken over there so I'll just link the thread. Maybe you can tell what's wrong since there are some subtle differences between the packaged version and how it's generally expected to work.

Sincerely
Richard

[1]:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/3NT7E3EH7OIV3QDFO5XD5H7G7MTIDTYE/

The problem has now been solved. The solution was to use http instead of uwsgi as protocol. Also, communication is running through http instead of a socket. I can't tell if http protocol would also work through a socket, but uwsgi wasn't working through either. Maybe the uwsgi.ini should contain a hint to that possibility in the future. Also, the apache config that is created during installation seems to be incomplete, as it only contains mailman3 but not hyperkitty, django and admin, plus mailman3 also isn't working and had to be replaced by postorius. Not sure though if that was only a problem for me or if that should be added.