Topic: iRedMail Failover Cluster
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? Downloadable Installer
- Linux/BSD distribution name and version: CentOS 7.7 1908 (Core)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
I want to try out the Failover Cluster you provide installation instructions for at https://docs.iredmail.org/haproxy.keepa … terfs.html .
I set it up following that guide and I have some questions or issues.
First one is about the concept regarding the virtual IP.
The guide lines out that there's a virtual IP which is intended to be the "access point" for the users.
What URL do the users have to enter into their web browser in order to access SOGo?
I tried the IP (https://192.168.1.10/SOGo), but the browser states, that the connection fails.
I created a DNS alias sogo.mycompany.com in our DNS server pointing to the virtual IP. I can successfully PING both the virtual IP address 192.168.1.10 and the FQDN sogo.mycompany.com.
The HA proxy setup seems to be correct: If I shut down HA1, I can still ping the virtual IP. If I shut down HA2 after having booted HA1 again, the ping still returns.
But it seems that the HTTP/HTTPS redirection from both HA1 and HA2 to the iRedMail nodes does not work.
Back to the questions:
1) Is it "as expected" that accessing SOGo by https://192.168.1.10/sogo (or its DNS alias) does not work?
2) If yes, what would I have to enter as URL to access SOGo in a "redundant" way, i.e. if one of the mail servers fail?