-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sympa 6.2.66 web interface returns "400 bad request" after upgrading to apache 2.4.52-1ubuntu4.10 #1863
Comments
Check this discussion: |
Thank you very much, this discussion gave the solution, modifying these files and adding localhost in this line: after reloading apache sympa web interface is working again. |
Thanks, this solution works for me too. Apache 2.4.52-1ubuntu4.11, Sympa 6.2.66~dfsg-2 on Ubuntu 22.04.4 LTS |
The same happened on Debian 12 bookworm. The workaround works too. |
Fixed in Debian package 6.2.72~dfsg-1. |
I saw Ubuntu oracular also followed. |
Thank you. This saved me some time.
Upgrade happened back in July. :/
|
We have an Ubuntu 22.04 server with Sympa "6.2.66" and apache2 "2.4.52-1ubuntu4.9" installed.
After an automatic packages update, apache packages with "2.4.52-1ubuntu4.10" new version has been installed and it seems this new version has broken sympa web interface that returned an error like this:
Version
sympa 6.2.66~dfsg-2
apache 2.4.52-1ubuntu4.10
ubuntu 22.04
Installation method
https://www.sympa.community/manual/install/install-sympa-distribution-debian.html
https://www.sympa.community/manual/install/configure-http-server-systemdsocket.html
Expected behavior
Sympa web interface would have to work after ubuntu apache packages upgrading
Actual behavior
Sympa web interface URL
https://server/wws
returns an 400 error like this:
Steps to reproduce
apt-get install apache2 apache2-bin apache2-data apache2-utils
Additional information
No issues after automatic upgrades to these ubuntu apache versions:
Apache access.log shows this:
Apache error.log shows errors like this:
The text was updated successfully, but these errors were encountered: