1. Welcome to the Starbound support forums. Please check the support FAQs before posting: http://playstarbound.com/support

Closed Error Failed To Connect: Definatly the Game

Discussion in 'Starbound Support' started by Lokai, Dec 20, 2013.

Thread Status:
Not open for further replies.
  1. Lokai

    Lokai Void-Bound Voyager

    So after exhausting pretty much every avenue i can think of, and doing everything people had suggested i'm now convinced that the game itself is bugged for multiplayer.

    Issue: When trying to connect to private server get the following message " Error, Failed To connect to server "

    FixesTried
    1: Opening ports, on both router itself and the firewall, shutting firewall down AND even enabled DMZ to see if it was indeed a port issue its not a port problem.

    2: Local Static IP: Setting it up, and getting it to run still failed to resolve the issue, i have same basic connection issue i had before.

    3: Tunngle/Hamachi programs: None of them work get same basic error as if the netcode itself is broken and blocking or not connecting properly.

    4: Full Reinstall, with deleting everything in the folder still a no go.

    5: Deleting the passwords in both config file and .cfg file

    6: Changed the port 21025 to 7777 same as terraria

    7 Reset my router to factory defaults and complete re input all data for port forwarding.

    8: combining all of the above in various ways and sacrificing the traditional virgin to the net gods that be!

    So after exhausting all of these options i am convinced that this is NOT us but rather the game itself. Either you guys REALLY don't want us to play, or you made it intentionally bad so we'd buy servers? i'm going to give you benefit of the doubt and say is a big netcode issue needs to be looked at. Because its mind boggling as to why we cant have a private server! i know beta is beta and hence why i am posting everything i did and how i got exactally NO where! what so ever!

    Edit: we both got the game via steam i thought i'd put that here as well.

    Edit 2: we just managed to get tunngle working again, not sure if it'll last but so far its not lagging may test more tomorrow and see how it functions.
     
    Last edited: Dec 20, 2013
  2. RvLesh

    RvLesh Parsec Taste Tester

    What's the first octet of the IP address to which you're attempting to connect?
     
  3. Lokai

    Lokai Void-Bound Voyager

    66.215 though doing a trace seems to die at this address 96.34.100.85,
     
  4. RvLesh

    RvLesh Parsec Taste Tester

    Should be 127.0.0.1 for you, and your external IP for them.
     
  5. Lokai

    Lokai Void-Bound Voyager

    i'm connecting to him he's hosting, so no its right he can get into his server fine i cant access his.

    Edit: so i did get tunngle to work just now, minor user error on our parts BUT we'll see how the lag holds up before was so bad we couldn't play really. Will update this later if its resolved.
     
  6. GreyMaria

    GreyMaria Existential Complex

    Does it disconnect instantly or does it take a while?
     
  7. Lokai

    Lokai Void-Bound Voyager

    Takes awhile it definatly tries to connect but just errors after a minute or two.
     
  8. GreyMaria

    GreyMaria Existential Complex

    Alright, that rules out version mismatch. For the record, that's what happens when there's a version mismatch between client and server; it' just instantly disconnects with a generic "error" without describing what went wrong.
     
  9. Lokai

    Lokai Void-Bound Voyager

    Yea was first thing we did was check versions when this started its not a version issue is definatly in the netcode and our routers arent the issue, something causing the error....
     
Thread Status:
Not open for further replies.

Share This Page