I am using apache to run the web interface, and my Postel port, and
  I have the proxy routs

    ProxyPass "/mailman3" "http://127.0.0.1:4386/mailman3";          works
    ProxyPass "/archives" "http://127.0.0.1:4386/archives";          works
    ProxyPass "/accounts" "http://127.0.0.1:4386/accounts";          is broken
    ProxyPass "/admin" "http://127.0.0.1:4386/admin";                works 
    ProxyPass "/user-profile" "http://127.0.0.1:4386/user-profile";  works

  What does "is broken" mean here? Well, since I have debug on,

GET "http://127.0.0.1:4386/accounts";

  yields something like (shortened to cut to the salient matter)

| <body>
|   <p>
|     Using the URLconf defined in <code>mailman_web.urls</code>,
|     Django tried these URL patterns, in this order:
|   </p>
|   <ol>        
|     <li>postorius/</li>        
|     <li>hyperkitty/</li>
|     <li>mailman3/</li>
|     <li>archives/</li>
|     <li>^user-profile/delete$
|     [name='mm_user_account_delete']</li>             
|     <li>^user-profile/$
|     [name='mm_user_profile']</li>
|     <li>accounts/</li>
|     <li>admin/</li>
|   </ol>
|   <p>
|     The current path, <code>accounts</code>, didn’t match any of these.
|   </p>
| </body>

  Sure I have accounts/ rather than accounts, but neither are working routes
  endowed with a trailing slash. Digging for mailman_web.urls, I am lead
  to believe this is related to my settings, and as I inspect them, I am
  reminded that I appended

del ACCOUNT_AUTHENTICATION_METHOD
ACCOUNT_LOGIN_METHODS = {'email', 'username'}
del ACCOUNT_EMAIL_REQUIRED
ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*']

  to my settings file. Commenting these lines out, restarting mailmanweb, still 
the
  same error.

  Ideally an error like this should be shown to the user. Instead it leads
  to a endlessly repeated requests for users to verify their email address, as 
seen
  in my live system at say

https://lists.repec.info/accounts/confirm-email/

  These have no CSS, pointing to an apache missconfiguration
  For what it's worth, here is my current apache configuration

| <VirtualHost *:443>
|   ServerName lists.repec.info
|   ServerAlias www.lists.repec.info
|   ServerAlias list.repec.info
|   ServerAlias www.list.repec.info
|   ServerAdmin webmaster@localhost
| 
|   RewriteEngine On
|   RewriteRule "^/?$" "https://lists.repec.info/mailman3/lists/"; [R]
| 
|   Alias /static "/usr/local/mailman/web/static"
|   <Directory "/usr/local/mailman/web/static">
|      Require all granted
|   </Directory>
| 
|   Alias /favicon.ico  
"/usr/local/mailman/web/static/postorius/img/favicon.ico"
| 
|   <IfModule mod_headers.c>
|     RequestHeader unset X-Forwarded-Proto
|     <If "%{HTTPS} =~ /on/">
|         RequestHeader set X-Forwarded-Proto "https"
|     </If>
|   </IfModule>
| 
|   <IfModule mod_proxy.c>
|     ProxyPreserveHost On
|     ProxyPassMatch ^/static/ !
|     ProxyPass "/mailman3" "http://127.0.0.1:4386/mailman3";
|     ProxyPass "/archives" "http://127.0.0.1:4386/archives";
|     ProxyPass "/accounts" "http://127.0.0.1:4386/accounts";
|     ProxyPass "/admin" "http://127.0.0.1:4386/admin";
|     ProxyPass "/user-profile" "http://127.0.0.1:4386/user-profile";
|   </IfModule>
| 
|   LogLevel debug
|   ErrorLog /var/log/apache2/lists.repec.info_error.log
| 
|   CustomLog /var/log/apache2/lists.repec.info_access.log combined
|   ServerSignature On
| 
|   Include /etc/letsencrypt/options-ssl-apache.conf
|   SSLCertificateFile /etc/letsencrypt/opt/live/repec.info/fullchain.pem
|   SSLCertificateKeyFile /etc/letsencrypt/opt/live/repec.info/privkey.pem
| 
| </VirtualHost>



-- 
  Written by Thomas Krichel http://openlib.org/home/krichel on his 22209th day.
_______________________________________________
Mailman-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at: 
https://lists.mailman3.org/archives/list/[email protected]/message/OXXYIE5P33ABRI5LVE5J77W6PH7VKFOU/

This message sent to [email protected]

Reply via email to