Skip to content
This repository has been archived by the owner on Aug 21, 2018. It is now read-only.

IP Bindings Not Properly Applying #227

Open
philip-ulrich opened this issue Aug 1, 2016 · 0 comments
Open

IP Bindings Not Properly Applying #227

philip-ulrich opened this issue Aug 1, 2016 · 0 comments

Comments

@philip-ulrich
Copy link

philip-ulrich commented Aug 1, 2016

Expected Behavior

When editing MySuperCoolServer.json located in /path/to/houston/config/servers/, I expect the line "host": "127.0.0.1", within the following context to change the binding IP on the server:

"limits": {
        "memory": "6000",
        "port": "1337",
        "host": "127.0.0.1",
        "enforce": null,
        "maxPlayers": 60
},

Current Behavior

Currently this modifies the line server-host= within server.properties, whereas it should be modifying the line server-ip= within server.properties.

Steps to Reproduce (for bugs)

  1. Modify server.json in config
  2. Restart server in SpaceCP
  3. ???
  4. Failure

If you check server.properties you will see that it changed the line server-host=.

Context

It makes it so I have to manually change the server.properties file. When choosing an IP becomes a thing, it will cause issues then as well.

Your Environment

  • Daemon version used: 0.0.1
  • Server OS (eg. Ubuntu 16.04): CentOS 7.2
  • Server environment (e.g. node.js 5.4): node.js 4.4.7
  • Client browser (e.g. Chrome 39): Chrome 51

<-- Any other information that may be odd about your environment -->

  • Other info: I eat grilled cheese over top my keyboard. It gets messy sometimes.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant