Node connection problem after changing the node's address

[mdjvd]

Describe the bug
Suppose you have a marzban-node on your dashboard's nodes list (active, disabled, or connecting status) and you change the address of that node in order to connect it to a different server (which has marzban-node already set up on it). In that case, marzban cannot connect to that new server.

I am not using marzban-node default ports (service and xray api)
I am using rest protocol on marzban-node (also tried it on rpyc and it was the same)

Sometimes restarting marzban and marzban-node will solve this problem. Sometimes I need to do it multiple times and sometimes it will be only fixed when I reboot the servers.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'node's list on dashboard'
2. Click on 'address' and change the address to a different IP that has marzban-node set up on it.
3. You can see marzban cannot connect to it and some ssl-cert-verify errors appear in marzban logs and also, CPU usage of the Master server will be kept at 100% when this happens

Expected behavior
marzban should be able to accept a new address for a node to connect to it.

Screenshots

[mdjvd]

I have noticed that when this happens, the xray inbound ports are usually being listened to on the node's server, even though the node is not connected. So it makes sense that restarting marzban and marzban-node will fix the issue, but it happens a lot and it is a bummer.