1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. 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

Linux Either no ping or not in server list

Discussion in 'Server Help' started by bunnie, Aug 4, 2016.

  1. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    Hello, I have a problem

    When I set sv_ip to 0 (autodetection), the server appears in the list, but it has no ping. When you try to connect to it, it tries to connect to 0.0.0.0, but you can connect directly to it by normal ip:port (92.222.105.241 instead of 0.blablabla)

    When i set sv_ip to the actual ip, 92.222.105.241, the server doesn't appear in the list, but you still can connect to it directly.

    Tried restarting my machine, changing ports, didn't help.
     
    Blue_Tiger likes this.
  2. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    Beo and PUNK123 like this.
  3. Beo

    Beo Bison Rider Tester

    Messages:
    62
    Yeah, wtf.
     
    bunnie and PUNK123 like this.
  4. Furai

    Furai THD Team THD Team Administrator

    Messages:
    3,124
    Servers are connectable?
     
  5. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    Yeah, in both cases you can connect by "Connect to..."

    Also, I've been messing with autoconfig a bit. This is my new one:
    http://pastebin.com/WpkPYCk7

    New stuff appeared in logs:
    [17:28:01] WARNING: API call failed: serverPort or serverAddress not present for putStatus()
    This error is being spammed at the end of the log

    and
    [17:27:50] WARNING: An issue was encountered while detecting the server's external IPv4/IPv6 address(es): cURL Error in determineOutboundIPv6Address(): Failed binding local connection end

    Full log: http://pastebin.com/NJfgvxt0
     
  6. Furai

    Furai THD Team THD Team Administrator

    Messages:
    3,124
  7. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    Server is visible in the browser only when sv_ip is set to autodetection (0), but you can't connect because it tries to connect to 0.0.0.0 when you do that.
    If i set sv_ip to the actual ip it doesn't appear in the browser.

    I did the curl:

    {"IPv6Address":"2001:41d0:d:e38::1:241"}bunnie@bunnieservers:~$
    from ds-whoami and v6-whoami

    v4-whoami
    {"IPv4Address":"92.222.105.241"}bunnie@bunnieservers:~$

    when u try to join by server browser, it still tries to connect to 0.0.0.0 (even when sv_ipv6 is properly set to 2001:41d0:d:e38::1:241 and sv_ip is set to 92.222.105.241)

    server is still connectable by "connect to..." (92.222.105.241)
     
  8. Furai

    Furai THD Team THD Team Administrator

    Messages:
    3,124
    Set sv_prefAF to 4, leave ipv6 set to 0, in the sv_ip put your actual IP from the ds test. V4 one. Leave v6 out completely. I can't now look up exact var names in config.
     
  9. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    So
    sv_prefAF = 4
    sv_enableIPv6 = 0
    sv_ip = 92.222.105.241
    sv_ipv6 = 0
    ?
    If yes, i get this error:
    [10:13:43] WARNING: An issue was encountered while detecting the server's external IPv4/IPv6 address(es): Your server appears to be IPv4 and IPv6 enabled. If you want to bind a specific address, you must have both sv_ip and sv_ipv6 configured
    [10:13:43] WARNING: As a result, sv_register has been forced to 0 and will not show up in the server list!
     
  10. Furai

    Furai THD Team THD Team Administrator

    Messages:
    3,124
    Wat? This does make no sense. What if you leave sv_ipv6 blank? I'll have a look at that part of code. Anyway, it's going to change quite a lot. @cameron1010
     
  11. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    Tested blank sv_ipv6 too, I got the same error
    --- Double Post Merged, Aug 10, 2016, Original Post Date: Aug 8, 2016 ---
    You told me to post furai, so i'm posting

    I tried running a fresh server with only port changed, this is what i got:

    [17:22:49] WARNING: API call failed: Unexpected HTTP Status (expected 200) in putStatus(): 500: Internal API error
    [17:22:55] Closing console device: Signal 2 received
     
  12. cameron

    cameron THD Team THD Team Tester
    1. Practitioners of War Extreme Revolution - POWER

    Messages:
    77
    I think that this is caused by the API client only registering your IPv6 address with the API. Without an IPv4 address registered too, clients cant connect using the server list. This is a bug with the API client, and it should be fixed soon, but I think a temporary workaround would be to disable your IPv6 address (not using the autoconfig).
     
  13. bunnie

    bunnie Haxor Tester

    Messages:
    1,319
    It worked, thanks.
    @Beo
     
    blackjoker77777 and Beo like this.