Home » Categories » Common Errors & Troubleshooting

Primary node showing the public ip instead of lan ip when cluster is configured

Article ID: 243 | Rating: Unrated | Last Updated: Wed, Nov 21, 2018 at 6:16 AM

The cluster tab of master node shows the licensed secondary ip and not the lan ip of the slave node. This happens when the slave node is behind a NAT. 

secondary node ip

In order to correct the other node ip, run the following command

/usr/local/ezlogin/ez_queryrunner.php "update prefix_settings set value='192.168.56.112' where name='remote_ip'"

 Now the cluster tab would show the lan ip of the other node instead of the public ip

secondary-fixed

 
Posted - Wed, Nov 21, 2018 at 6:14 AM. This article has been viewed 688 times.
Filed Under: Common Errors & Troubleshooting
0 (0)
Article Rating (No Votes)
Rate this article
    Attached Files
    There are no attachments for this article.
    Related Articles RSS Feed
    "Blank page" error in webssh console
    Viewed 1518 times since Tue, Jan 30, 2018
    How to search using IP or other fields instead of host name in jump server ssh interface or gui?
    Viewed 1478 times since Fri, May 4, 2018
    How to fix: “EPROTO” Error after upgrading Node’s version in RDP?
    Viewed 36 times since Wed, May 20, 2020
    ERROR for site owner: Invalid domain for site key
    Viewed 5162 times since Thu, Jun 28, 2018
    unable to start mysql in ubuntu 14 " logger command not found"
    Viewed 2640 times since Thu, Jun 15, 2017
    Install not allowed on this server
    Viewed 90 times since Fri, Mar 20, 2020
    PHP extension ’mcrypt’ is required.
    Viewed 4998 times since Wed, Jun 14, 2017
    Google 2 factor authentication fails randomly
    Viewed 1817 times since Wed, Jun 14, 2017
    ’Failed to establish SSH session ’
    Viewed 2103 times since Fri, Jun 22, 2018
    Could not download binary package. Please manually download it from downloads.ezeelogin.com
    Viewed 520 times since Thu, Apr 4, 2019