From e70dafd785a2fdba147dfc7a343f5865e449860a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=96zcan=20O=C4=9Fuz?= Date: Sat, 31 Dec 2022 06:35:23 +0300 Subject: [PATCH] Add a reminder for SNAT_TO_SOURCE variable after migration I have moved our mailcow server from one server to another by following this tutorial, but [mailcow/mailcow-dockerized#4627](https://github.com/mailcow/mailcow-dockerized/issues/4627) has occured, and the problem was the misconfiguration for this variable, I've spent around half an hour on investigation. A reminder has added for this situation in order to prevent some tears :) --- docs/i_u_m/i_u_m_migration.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/i_u_m/i_u_m_migration.en.md b/docs/i_u_m/i_u_m_migration.en.md index 9f8c8ae1e..793fbf12a 100644 --- a/docs/i_u_m/i_u_m_migration.en.md +++ b/docs/i_u_m/i_u_m_migration.en.md @@ -44,4 +44,4 @@ docker compose pull docker compose up -d ``` -**9\.** Finally, change your DNS settings to point to the target server. +**9\.** Finally, change your DNS settings to point to the target server. Also check the `SNAT_TO_SOURCE` variable in your `mailcow.conf` file if you have changed your public IP address, otherwise SOGo may not work.