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

User add failed

Viewed 2234 times since Wed, Jun 14, 2017

usernames already exists

Viewed 278 times since Fri, Mar 15, 2019

no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

Viewed 3077 times since Tue, Jan 2, 2018

Unable to add server using putty private key key pair. How to convert PPK file OpenSSH format

Viewed 3460 times since Thu, Jun 15, 2017

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

Viewed 1045 times since Fri, Aug 10, 2018

Google 2 factor authentication fails randomly

Viewed 1535 times since Wed, Jun 14, 2017

unable to ssh because ip not allowed because none of user’s groups are listed in AllowGroups

Viewed 8009 times since Thu, Jun 15, 2017

error: User modify failed Cannot modify user on this node: OS=FreeBSD: Command not found. OS: Undefined

Viewed 1604 times since Wed, Jun 14, 2017

key_read: uudecode ssh user cant login with ssh key

Viewed 4215 times since Thu, Jun 15, 2017

502 on login with nginx

Viewed 2039 times since Wed, Jun 14, 2017