404 on fresh install (Debian11)
Hello, very new to mailman3, I used to manage mailman2 on a Debian 10 server. The server has been upgraded to Debian 11 and mailman2 disappear…
I try fresh install of mailman3, prerequisite to data migration, but without success. If some can help, I would be really greatful.
Here is my path:
mailman3-full
install with apt. MySQL config since I have this DBMSpython3-pymysql
install with apt after seeing errors in logs- Apache2 configuration (other virtual hosts are present)
<VirtualHost *:80>
ServerName newsletter.mydomain.tld
Alias /static /var/lib/mailman3/web/static
Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico
DocumentRoot /var/lib/mailman3/web/static
<Directory "/var/lib/mailman3/web/static">
Require all granted
</Directory>
ProxyPassMatch ^/static !
ProxyPass / http://localhost:8001/
ProxyPassReverse / http://localhost:8001/
ErrorLog ${APACHE_LOG_DIR}/newsletter_error.log
CustomLog ${APACHE_LOG_DIR}/newsletter_access.log combined
</VirtualHost>
And now I have a 404 answer when consulting my http page.
When trying to access /static
sub-path, I get Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found
.
I also tried ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost
but also fails with No protocol handler was valid for the URL / (scheme 'uwsgi')
I am a bit lost with that.
Thanks for your help
On 3/22/23 3:42 AM, thomas--- via Mailman-users wrote:
Hello, very new to mailman3, I used to manage mailman2 on a Debian 10 server. The server has been upgraded to Debian 11 and mailman2 disappear…
I try fresh install of mailman3, prerequisite to data migration, but without success. If some can help, I would be really greatful.
Here is my path:
mailman3-full
install with apt. MySQL config since I have this DBMS
The packaged version included with Debian 11 is out of date. You would be much better off installing Mailman3 and mailmanweb in a virtual environment using pip:
https://docs.mailman3.org/en/latest/install/virtualenv.html
https://docs.mailman3.org/en/latest/config-web.html
dn
python3-pymysql
install with apt after seeing errors in logs- Apache2 configuration (other virtual hosts are present)
<VirtualHost *:80> ServerName newsletter.mydomain.tld Alias /static /var/lib/mailman3/web/static Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico DocumentRoot /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> ProxyPassMatch ^/static ! ProxyPass / http://localhost:8001/ ProxyPassReverse / http://localhost:8001/ ErrorLog ${APACHE_LOG_DIR}/newsletter_error.log CustomLog ${APACHE_LOG_DIR}/newsletter_access.log combined </VirtualHost>
And now I have a 404 answer when consulting my http page.
When trying to access
/static
sub-path, I getCannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found
.I also tried
ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost
but also fails withNo protocol handler was valid for the URL / (scheme 'uwsgi')
I am a bit lost with that.
Thanks for your help
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/...
This message sent to dnewman@networktest.com
On 3/22/23 03:42, thomas--- via Mailman-users wrote:
Hello, very new to mailman3, I used to manage mailman2 on a Debian 10 server. The server has been upgraded to Debian 11 and mailman2 disappear…
I try fresh install of mailman3, prerequisite to data migration, but without success. If some can help, I would be really greatful.
<VirtualHost *:80> ServerName newsletter.mydomain.tld
Alias /static /var/lib/mailman3/web/static Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico DocumentRoot /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted
You can probably fix the below error by adding options +Indexes here, but see below.
And now I have a 404 answer when consulting my http page.
When trying to access
/static
sub-path, I getCannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found
.
It is unclear to me what is doing a GET of /static/admin/ and why. GETs should by of actual files, e.g., things like /static/admin/css/base.css
I am a bit lost with that.
So are we. Questions about the Debian package are better asked of Debian. See https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB2...
We can provide much better help and support if you install via the resources mentioned in the reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks both of you. I didn't know Debian11 version is out of date. I will try using pip.
On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < mailman-users@mailman3.org> wrote:
Thanks both of you. I didn't know Debian11 version is out of date. I will try using pip.
No. Debian 11 is _not_ out of date. It's just that the preferred and easy to support installation method is using the virtualenv.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
On 3/23/23 08:42, Odhiambo Washington wrote:
On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < mailman-users@mailman3.org> wrote:
Thanks both of you. I didn't know Debian11 version is out of date. I will try using pip.
No. Debian 11 is _not_ out of date. It's just that the preferred and easy to support installation method is using the virtualenv.
The Debian stable mailman packages definitely ARE out of date.
bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2.
bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2023-03-23 09:07:02 -0700 (-0700), Mark Sapiro wrote: [...]
bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install.
And those will also become out of date over time, because Debian is a stable server distribution so intentionally freezes the versions of software it supplies and backports only critical/security fixes to those increasingly outdated versions when warranted.
Basically it's a question of whether users value stability with a bit of security support over newest versions of software and new features. The upstream Mailman packages on PyPI (and container images) cater to users who want the latest versions of the software, packages in stable server distros like Debian cater to users who want to safely go years between behavior changes in software. Both are valid choices, it just comes down to the user's specific situation.
That said, when you have trouble with the packaged versions of software in Debian, the expectation is that you ask on Debian mailing lists and possibly report bugs in the Debian bug tracker, rather than burdening upstream software maintainers with details that might be specific to choices or mistakes in Debian's packages. The package maintainers in Debian generally forward bug reports upstream if they determine the issue you've encountered isn't related to how it's been packaged, isn't already fixed upstream (in which case they might backport the fix), et cetera.
Jeremy Stanley
Can you setup Mailman3 for me? I have done apt install mailman3-full but I have no clue whaat I am doing.
Jim
On 3/28/23 5:00 PM, comprepair_jimberg--- via Mailman-users wrote:
Can you setup Mailman3 for me?
I can't. But I previously provided a pointer to setup instructions using virtualenv, which is MUCH preferable to the older, buggier version packaged with Debian 11. Mark Sapiro also provided a link to a list of providers who help with setup for a fee.
If it's any consolation, I practiced with test VMs about 4 or 5 times before attempting a production migration from Mailman 2. Much of my misery was caused by the initial Debian install setting the wrong ownership on some files. For that reason, things got much better when I snapshotted a brand-new Debian 11 VM and rolled back to there each time. I still made mistakes, multiple times, but at least I was no longer fighting with two installations that do things differently.
dn
I strictly follow documentation, and it works without pain! 👍 Many thanks for this quality documentation
participants (6)
-
comprepair_jimberg@icloud.com
-
David Newman
-
Jeremy Stanley
-
Mark Sapiro
-
Odhiambo Washington
-
thomas@lydra.fr