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

Article Rating (No Votes)

Rate this article

Attached Files

There are no attachments for this article.

Related Articles

Getting "Could not load configuration" or 500 error on login page

Viewed 1919 times since Wed, Jun 14, 2017

404 error on login with nginx

Viewed 2052 times since Wed, Jun 14, 2017

Blank page in GUI and an error in SSH/backed shell ’ license expired!’

Viewed 1441 times since Wed, Aug 16, 2017

You don’t have permission to access /ezlogin/index.php/auth/login on this server

Viewed 818 times since Fri, Aug 10, 2018

Connection has been closed. Another user may have logged in on the remote windows machine

Viewed 1875 times since Thu, Jun 15, 2017

Class ’DOMDocument’ not found

Viewed 381 times since Thu, Oct 25, 2018

How to search using IP or other fields instead of host name in jump server ssh interface or gui?

Viewed 1035 times since Fri, May 4, 2018

Configure Automatic su or sudo

Viewed 2938 times since Thu, Jun 15, 2017

How do i disable google 2 factor authentication or other 2factor mechanisms?

Viewed 3256 times since Wed, Jun 14, 2017

License cache outdated but its not time yet

Viewed 1438 times since Wed, Jun 14, 2017