View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0026166||2.x IDE Bugs||Web Server||Public||2017-04-06 12:33||2018-10-25 17:10|
|Reporter||Stewart Bishop||Assigned To||Alan Savage|
|Priority||Medium||Severity||C - General||Reproducibility||100%|
|Target Version||2.2.1||Fixed in Version||2.2.1|
|Summary||0026166: Web Server: GMS2 provides a different IP range than GMS1 provides, requires users to add in a different IP|
|Description||Using our IP range for example if you run a HTML5 game in GMS1 your web server will have|
Within the list of allowed IPs however if you run a HTML5 game in GMS2 your web server will have
The IP from GMS2 won't work for our network range for example and you have to manually add in the correct IP to allow mobile devices to connect to the HTML5 game.
|Steps To Reproduce||1) Create a project in GMS2|
2) Change target to HTML5
3) Run it
4) Take a note of the IP Range
5) Do steps 1 to 3 in GMS1
6) See that the IP Range is correct in this case
|2.x IDE Found In||184.108.40.206|
|2.x Runtime Found In||220.127.116.11|
|2.x IDE Verified In||18.104.22.1685|
|2.x Runtime Verified In||22.214.171.1248|
Make sure GMS1 actually auto-detects your IP and uses that, as I think this is just that you'd previously set the IP range correctly in GMS1.
There is a a legit bug, though, if GMS2 is resetting your IP back to 192.168.... each time.
And I thought the issue was that it didn't use the .0/24 bit in GMS2 and instead just specified one fixed IP?
Every time you start the web server again the list of IPs is always reset back to the default 192.168.0.0/24 regardless of what you've previously put in.
Whether GMS1 does this also needs to be checked I guess.
||updated igor to use local ip as base for allowed webserver ip (unless overridden by a specific browser device setting)|