1. Guest, as per the stickied thread, this forum has not been in use since 2014. All bugs and feature requests should be posted to JIRA.

Rejected Everyone has same IPi

Discussion in 'Bugs & Feature Requests' started by Silverbrit, Sep 1, 2013.

Thread Status:
Not open for further replies.
  1. Hello, last time I asked this question LiLChris instantly rejected my thread. I had a problem were everyone had the same IP. He suggested to put 127.0.0.1 under the bungee cord address, which I already did. I do have the plugin OnlyProxyJoin and that is using my 198.***.**.*** ip. I need that plugin because I don't want other people joining as me and destroying the world (Which happened :C). As far as I know when first making the bungeecord server it does tell me how I can resolve this issue? When I remove the proxyonlyjoin plugin, every has their unique IP again but it takes away my protection from the offline thing.

    Here is a link to all my configs:

    spigot.yml - http://pastebin.com/zU8Yjbjs
    bungeecord config.yml http://pastebin.com/RtK97LH7
    OnlyProxyJoin config.yml http://pastebin.com/mFde4RZD

    I starred out the 198.***.**.*** IP but they are all the same.

    I would appreciate help this time and without getting instantly rejected.
     

  2. Bukkit.yml set server-ip to 127.0.0.1 or use iptables instead


    Edit: hmm binding the servers to 127.0.0.1 wont work as the bungee is on another ip I assume. Check the wiki for iptable instructions
     


  3. You meant spigot.yml right? Since bukkit.yml has no where you can insert an ip.My spigot.yml is already set to 127.0.0.1 if you were to actually read the thread I made you would've known this....
     
  4. I meant server.properties sorry
    But its irrelevant as your bungee isnt pointing to a local host read the edit :)
     

  5. I remember doing this but the ProxyOnlyJoin plugin throws out an error.

    There must be a way where people don't have to use that plugin, I know most servers don't use it. What am I missing here?

    Edit: In response to your edit, the server only uses that the 198.**.*** ip
     
    #5 Silverbrit, Sep 1, 2013
    Last edited: Sep 1, 2013
  6. LiLChris

    LiLChris Retired Moderator
    Retired

    Again this is not a bug with Spigot/Bungeecord, stop reporting it as such.

    Try this instead.
    Bungeecord Config: http://pastebin.com/raw.php?i=3j286CLs

    Remove Onlyproxyjoin, use IPtables or bind your servers to 127.0.0.1.
    If you have any sort of DDOS protection this can interfere depending on how it is setup.
     
  7. How do I go about binding my servers to 127.0.0.1, sorry?
     
  8. joehot200

    Supporter

    In bungee-proxies in the spigot.yml, add on a new line:
    - 198.**.***

    That should solve same IP problems.

    In server.properties, set server-ip to 127.0.0.1
     
  9. Th
    Thank you, so I've removed ProxyOnlyJoin and I've binded my server.properties to 127.0.0.1 and I also used the bungeecord config LiLChris. I'll let you know how it goes.
     
  10. i9hdkill

    i9hdkill Retired Moderator
    Retired Supporter

    Add your real BungeeCord address in every spigot.yml to BungeeCord adress

    AND

    bind every spigot server to 127.0.0.1
    this only works when all servers are on the same physical host!

    OR

    use iptables (its easy!)
    In this thread iptables rules are explained well:
    http://www.spigotmc.org/threads/1-6-2-bungeecord.392/
     
  11. I did add my 198.***.**.*** ip to all spigot.yml and I also binded my servers 127.0.0.1 and now everyone has their unique IP, yay!

    I don't need to use iptables anyways, do I? Since all my servers are on the same box, currently.
     
  12. joehot200

    Supporter

    I dont use IPTables, and if i dont, you probably dont have to :3
     
  13. i9hdkill

    i9hdkill Retired Moderator
    Retired Supporter

    No you dont need to. (because all on the same box)
     
  14. LiLChris

    LiLChris Retired Moderator
    Retired


    Glad it solved.
    No you do not need to use iptables, of course make sure by trying to log in through the back end ports.

    Closing this as its been resolved and marking as rejected as it's not a bug.
     
    • Agree Agree x 1
Thread Status:
Not open for further replies.