Open jameskitt616 opened 4 months ago
Known issue, discussion open here:
https://github.com/m1k1o/neko-rooms/issues/62
But its good to keep the issue open on neko itself. Since neko rooms just passes ip to the neko as env it cannot do anything else as env variables cannot be changed upon starting the container. There might be other solutions - get ip regularly, resolve IP using hostname.
Pretty sure i had that same issue on regular standalone neko. Before i used neko rooms.
Maybe it's possible to pass an hostname/domain to neko and it re-resovles the IP in case of DNS warning? or sth similar to this.
Maybe it's possible to pass an hostname/domain to neko and it re-resovles the IP in case of DNS warning? or sth similar to this.
https://github.com/m1k1o/neko/issues/402
That would be the next step.
I noticed if my dynamic IP changes, while the room was started, Neko breaks and you cannot login anymore. Here is the Error log