it seems that when installing Nethserver based on the latest nethserver-7.9.2009-x86_64.iso there is some configuration mistake that leads to the rpsamd webinterface configuration page (h**ps://192.168.2.218:980/rspamd/#configuration) not being able to properly login.
I will post the information like passwords unscrambled, they are from a local test installation anyhow.
Opening the page (regardless if opened from Cockpit or standalone, providing credentials) makes the page request two addresses:
Results in a “403 Forbidden”.
Results in a “200 OK” and seems to return the expected JSON object.
This results in the webinterface in showing two messages:
- “local > Request failed: Forbidden”
- “Request failed”
How to reproduce
Start with nethserver-7.9.2009-x86_64.iso
No special instructions for installation. Root password has been set, no user created.
Once installation is done, login to cockpit on port 9090 as root.
Set FQDN and install the mail server from the software collection.
No need to update the packages first (also tested with updating first, no change).
Further information/tests done
Previously used (on another server) nethserver-7.8.2003-x86_64.iso does not show this problem.
Upgrading and updating 7.8.2003 to the latest version available via the “Software Center” does not show this problem, which is the reason why I myself and most other users might not have ran into this yet when using their existing installations.
When upgrading and updating 7.8.2003, it does not matter if you install the mail server package before or after the upgrade/update. Both ways result in a working configuration page.
Using different credentials to open the Rspamd interface (with credentials of a user in domain admin group does not work either). Easiest way:
You might have to setup a port forwarding to use another port (or reconfigure the Rspamd web port from 980 to something else) if your browser does not allow you to use other credentials. This can be done for example using “socat”:
socat tcp-listen:9800,reuseaddr,fork tcp:localhost:980
I did find other promising topics but in the end they did not match this specific problem and ended in solutions that do not seem to be related to this behavior.
Hope this helps to identify/solve this problem if other are experiencing this as well (which new users most likely do).