Connection problems
If the Administrator Panel cannot connect to the server module, work through the steps below to identify and resolve the issue.
1. Verify services are running
Check that both services are active:
systemctl status msh-pm-settings
systemctl status msh-pm-milter
If either service is not running, restart it:
sudo systemctl restart msh-pm-settings
sudo systemctl restart msh-pm-milter
If a service fails to start, check the log files in /opt/msh-pm/var/log/ for details.
Log entries are only written when diagnostic logging is enabled. See Enable diagnostic logging for instructions.
2. Check /etc/hosts configuration
Connection errors referencing 127.0.1.1 typically indicate a misconfiguration in /etc/hosts. Make sure your hostname is mapped to the actual IP address of the server rather than a non-standard loopback address. Restart the services after editing the file.
3. Configure RMI hostname
If the connection fails and the error references 127.0.0.1, the server may be advertising the wrong address. Edit /opt/msh-pm/bin/msh-pm-settings and add the following Java parameter, replacing <YOUR_IP> with the actual IP address of the server:
-Djava.rmi.server.hostname=<YOUR_IP>
Restart the services after making this change.
4. Force IPv4
If your system prefers IPv6 and this causes connectivity issues, add the following parameter to the settings startup script to force IPv4:
-Djava.net.preferIPv4Stack=true
Restart the services after making this change.
5. Check firewall rules
The Administrator Panel communicates with the server module over ports 1207 and 1208. Ensure these ports are open on any firewall between the two machines. To test, temporarily disable the firewall and attempt to connect. If that resolves the issue, add permanent rules to allow traffic on those ports.