1. Hey Guest, is it this your first time on the forums?

    Visit the Beginner's Box

    Introduce yourself, read some of the ins and outs of the community, access to useful links and information.

    Dismiss Notice

KAG Server isn't registering on server list

Discussion in 'Server Help' started by Chaosed0, Dec 7, 2013.

  1. Chaosed0

    Chaosed0 Catapult Fodder

    Messages:
    15
    I'm running a server on a VPS, hosted by NodePop. I can connect to it fine through IP, but I can't seem to find it in the server browser.

    Here's my autoconfig.cfg and the latest console.txt from the Logs folder. If you need any other information to diagnose the issue, let me know.
     
    Chaosed0, Dec 7, 2013
    #1
  2. Downburst

    Downburst Mindblown Global Moderator Forum Moderator Donator Tester

    Messages:
    1,813
    Your server doesn't seem to be connectable according to the api. Is there any kind of firewall that's blocking the API from connecting your server?
    edit: I am not able to join myself using that IP and port.
     
    Downburst, Dec 8, 2013
    #2
  3. Chaosed0

    Chaosed0 Catapult Fodder

    Messages:
    15
    That isn't the right IP address; it's actually "216.218.208.61". Otherwise, that info looks correct. That's probably why, but I can't imagine why the IP would be wrong. I don't think the server is firewalled.
     
    Chaosed0, Dec 8, 2013
    #3
  4. Downburst

    Downburst Mindblown Global Moderator Forum Moderator Donator Tester

    Messages:
    1,813
    There might be something wrong with your host's ipv6 settings. Could you try turning ipv6 off in the autoconfig?
     
    Downburst, Dec 8, 2013
    #4
  5. Chaosed0

    Chaosed0 Catapult Fodder

    Messages:
    15
    Ok, I've set "sv_enableIPv6 = 0". Doesn't seem like anything's changed. The server is currently running.
     
    Chaosed0, Dec 8, 2013
    #5
  6. Downburst

    Downburst Mindblown Global Moderator Forum Moderator Donator Tester

    Messages:
    1,813
    Did you turn the server off before changing the settings because it still shows your ipv6 for some reason.
     
    Downburst, Dec 8, 2013
    #6
  7. Chaosed0

    Chaosed0 Catapult Fodder

    Messages:
    15
    Yeah, I restarted the server. Did it again just now, in case.
     
    Chaosed0, Dec 8, 2013
    #7
  8. Downburst

    Downburst Mindblown Global Moderator Forum Moderator Donator Tester

    Messages:
    1,813
    Yea very weird, the api thinks your server has a different IPv4.

    What is the output of ifconfig on your vps?
     
    Downburst, Dec 8, 2013
    #8
  9. Chaosed0

    Chaosed0 Catapult Fodder

    Messages:
    15
    Here you are:

    Code:
    lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:433 errors:0 dropped:0 overruns:0 frame:0
          TX packets:433 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:44384 (43.3 KiB)  TX bytes:44384 (43.3 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.2  P-t-P:127.0.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: 2001:470:1:3ed::f7a4:e651/128 Scope:Global
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:366563 errors:0 dropped:0 overruns:0 frame:0
          TX packets:362759 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:163509165 (155.9 MiB)  TX bytes:82992002 (79.1 MiB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:216.218.208.61  P-t-P:216.218.208.61  Bcast:216.218.208.61  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
    EDIT: Just read up a bit on the API. I did a wget on v4-whoami.kag2d.com, and it did give me back an address of "64.62.178.187". Wonder what's up with that. Seems like at this point, it's either an issue on the developer's end or the host's.

    EDIT2: Ok, definitely an issue on my host's part - ipv4.icanhazip.com returns the same IP. Time to contact them. Though, I wonder why we are still able to connect through the correct IP...

    EDIT3: Never did get this fixed. The host (NodePop) took three days to respond to my ticket, and told me to "change my main IP" through a control panel I couldn't log into. Ended up switching to another VPS provider, which "solved" the problem. To sum up: it was a problem with the VPS, not with the server.
     
    Last edited: Dec 19, 2013
    Chaosed0, Dec 8, 2013
    #9