Commit 4e10660e authored by Florent Daigniere's avatar Florent Daigniere Committed by Mergify
Browse files

Warn about rollbacks not working

(cherry picked from commit 4ff9582e139654dfbb84c972a5f88d40cb2337c0)
parent ffd8829e
......@@ -3,8 +3,7 @@ Changelog
For full details see the [releases page](https://mailu.io/1.9/releases.html)
Upgrade should run fine as long as you generate a new compose or stack
configuration and upgrade your mailu.env.
Upgrade should run fine as long as you generate a new compose or stack configuration and upgrade your mailu.env. Please note that once you have upgraded to 1.9 you won't be able to roll-back to earlier versions without resetting user passwords.
If you use a reverse proxy in front of Mailu, it is vital to configure the newly introduced env variables REAL_IP_HEADER and REAL_IP_FROM.
These settings tell Mailu that the HTTP header with the remote client IP address from the reverse proxy can be trusted.
......
......@@ -119,7 +119,7 @@ A short summary of the new features:
Upgrading
`````````
Upgrade should run fine as long as you generate a new compose or stack configuration and upgrade your mailu.env.
Upgrade should run fine as long as you generate a new compose or stack configuration and upgrade your mailu.env. Please note that once you have upgraded to 1.9 you won't be able to roll-back to earlier versions without resetting user passwords.
If you use a reverse proxy in front of Mailu, it is vital to configure the newly introduced environment variables `REAL_IP_HEADER`` and `REAL_IP_FROM`.
These settings tell Mailu that the HTTP header with the remote client IP address from the reverse proxy can be trusted.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment