Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

panel is setting the wrong IP for a new server #320

Closed
qvera opened this issue Dec 6, 2014 · 5 comments
Closed

panel is setting the wrong IP for a new server #320

qvera opened this issue Dec 6, 2014 · 5 comments
Labels
Milestone

Comments

@qvera
Copy link

qvera commented Dec 6, 2014

  1. I have fresh installed Admin CP and after creating NODE, there was mistake in setting IP where was set local IP (127.0.0.1) not public IP even when I was writing public IP into "Available IPs & Ports". Problem is now solved (thanks to IRC support), but please solve it for the future :)
  2. I tried to rename server run file to "bungee.jar" through admin page, but I was unable to do it. After refreshing the page, there was only blank input and in config.json was still server.jar

Thanks, Terrdus

@DaneEveritt
Copy link
Contributor

Personal notes:

  1. Issue caused is that in the node you select a public IP address, but for some reason when running the create process it set it to a local IP, possibly because there was another available IP listed that was local, could be an issue with the selector.
  2. Looks like that code is outdated since it can be updated through the user interface for the server.

@DaneEveritt DaneEveritt added the bug label Dec 6, 2014
@DaneEveritt DaneEveritt modified the milestones: 0.8.0 Beta, 0.7.6 Beta Dec 6, 2014
@LordRalex
Copy link
Member

I cannot see where any selector occurs that could replicate this, since we use the input that is given from the user to apply to the node.

@DaneEveritt
Copy link
Contributor

I believe this was caused by me not passing the game host in prior versions. Can you replicate 2?

@LordRalex
Copy link
Member

Admin page no longer has renaming through it, and so it has to be done through the server settings, which works as intended.

@qvera
Copy link
Author

qvera commented Dec 9, 2014

Thanks for investigating this problem. It was VPS fault. I triedinstall it on another machine and it works fine. I don't know problem which caused this (maybe network driver). But it was VPS fault.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants