Facebook
Twitter- Server operating system version
- Debian 12.7
- Plesk version and microupdate number
- Plesk Obsidian 18.0.64 Update 1 Web Pro Edition
Since Mailman3 has been available, I have upgraded my server to Debian 12 and also installed Mailman3. Basically, everything is now working properly (I had to deal with a few access rights problems and a Comodo rule that went awry at the beginning, but these have now been fixed).
Now I only have one problem that Mailman support can't help me with.
Hyperkitty is unfortunately not archiving my mails to the mailing lists.
In mailman.log i'm finding:
in mailman-hyperkitty.cfg there is:
an in mailman-web.py
(only for test, if it works i will use my domains/IPS)
The Keys in mailman-hyperkitty.cfg and mailman-web.py are the same Keys.
I Think the error is produced from nginx :-/
the nginx.conf-file (/etc/nginx/plesk.conf.d/server.conf) says
(the ist lists.domain.tld, therefore th...s [URL='https://[ip]:7081/']https://[IP]:7081;
proxy_hide_header upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For
$proxy_add_x_forwarded_for;
}
}
[/QUOTE]
Has anyone an idea, how i geht hyperkitty working with Plesk?
Now I only have one problem that Mailman support can't help me with.
Hyperkitty is unfortunately not archiving my mails to the mailing lists.
In mailman.log i'm finding:
in mailman-hyperkitty.cfg there is:
an in mailman-web.py
(only for test, if it works i will use my domains/IPS)
The Keys in mailman-hyperkitty.cfg and mailman-web.py are the same Keys.
I Think the error is produced from nginx :-/
the nginx.conf-file (/etc/nginx/plesk.conf.d/server.conf) says
(the ist lists.domain.tld, therefore th...s [URL='https://[ip]:7081/']https://[IP]:7081;
proxy_hide_header upgrade;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For
$proxy_add_x_forwarded_for;
}
}
[/QUOTE]
Has anyone an idea, how i geht hyperkitty working with Plesk?
