Multiserver 2.0

[Zelphir]

Zelphir (Click to View)

Hi, I recently discovered a strange issue with Multiserver 2.0, in which it differs from Multiserver 1.

It's been working fine, when I had 192.168.0.13 as internal IP. Then one day the internal IP address changed to 192.168.0.12. I had to change my port forwarding accordingly and all other ways of connecting worked fine again, however, when I started Multiserver 2, it complained, that it could not bind to the port and address 192.168.0.13, although to my knowledge I didn't have that internal IP address anymore in my home network (router + a few machines).

I am not sure why this happens. Does Multiserver 2.0 somehow memorize my internal IP address and reuse the memorized value? As long as I don't get 192.168.0.13 assigned from my router again, I'll probably not be able to use it

This is a wild guess, but try going to your Firewall settings and delete MultiServer from the allowed app list. When you open it again it will ask for permissions. Let us know if this works.

This is a Linux OS The firewall never asks me and I do have only a rule there for port 12345 TCP. This rule is not bound to a specific 192.168.X.Y address though, as the system knows its own IP address in the home network and does not need this specification. The only other firewall is in the router. In the router firewall I always have to change the rule according to what my home network internal IP is, which seems natural to me. If I take that rule away, no one will be able to connect to me even when using Multiserver 1.

It's not really about not being able to connect, but about Multiserver 2 complaining not being able to bind to an IP address, which I don't have anymore, locally in my home network. If it only took the correct IP address to bind to, I am sure it would work just fine, just like Multiserver 1 does.