-
Notifications
You must be signed in to change notification settings - Fork 11
Description
This is probably not the fault of this project, but my VM is where I am experiencing it, so maybe someone can lend some insight.
I used these scripts to set up a Windows VM, which got assigned the IP address 192.168.1.123. This is the address it serves Sunshine from, so it's the address assigned to the connection in Moonlight. To make sure it stayed the same, I assigned this IP as static in my router. For months, this has worked perfectly.
Recently, Moonlight has been unable to find the connected device when the VM is running, and I was unable to connect to Sunshine's management page in the browser. I opened the VM manually and looked at Sunshine, and saw that the IP assigned to the VM had somehow changed to 192.168.1.456. (I also looked on my router admin page, and did not see any connected device with that IP address.) Ok, weird but whatever. I re-added the VM to Moonlight with the new IP.
However, when I next ran the VM a few days later, Moonlight again could not find it. Opening the VM, I saw its IP had changed back to 192.168.1.123! And the next time I ran the VM after that, it again switched back to 192.168.1.456. Any idea why this might be happening??