The initial reasoning for the creation of this thread has been resolved. That issue read as "Connection refused". I am leaving this thread open so that the staff from CreeperHost can continue to keep tabs on the issues we sometimes see when connecting with the launcher to download modpacks, texture packs, maps, etc.
I have "spoilered" the items from the original post that should not apply to future issues. They will remain in this original posting for the thread in the off chance they help someone else with their connection issues.
I'll post the information I have from my experience, in the format I would like to see people report their issues.
Format:
I will be asking that if anyone who posts their experience outside of the requested format to have their post deleted. The exceptions will be: for users posting a suggestion for a user-level workaround, or suggestions by Creeperhost staff and/or the launcher dev team, or information provided by official means. I will be asking this of the moderation staff so that it will be easier for Creeperhost and the launcher dev team to work on a solution for everyone.
Per Luke from Creeperhost: On your forum thread, can you ask people to ping new.creeperrepo.net and post results?
I have "spoilered" the items from the original post that should not apply to future issues. They will remain in this original posting for the thread in the off chance they help someone else with their connection issues.
For the last several days there have been some serious issues with connection. While I cannot speak for everyone encountering this issue, I have been able to replicate it.
Format:
Operating System, bit type:
Internet Service Provider:
Java version/update, bit type:
Anti-malware software:
Location you are (generalized):
Location you're downloading from:
Launcher version:
Completed the troubleshooting guide (y/n):
Console log, pastebin.com link:
Ping Results:
I've spoken to unv_annihilator and Luke from Creeperhost. Presently I do not have a user-level solution for this connection problem. This is why I've decided on this thread. All parties who are able to contribute to a solution for everyone can view a thread on the forums. They cannot all see what I see on the Help Desk. All future reports about this connection issue that are reported on the Help Desk will be referred to this thread.
unv_annihilator has suggested this for users having this issue:
.You could tell people to change their ftblaunch.cfg and either add or modify the "downloadServer=" line to either be "Los Angeles" or..."Nottingham"
I will be asking that if anyone who posts their experience outside of the requested format to have their post deleted. The exceptions will be: for users posting a suggestion for a user-level workaround, or suggestions by Creeperhost staff and/or the launcher dev team, or information provided by official means. I will be asking this of the moderation staff so that it will be easier for Creeperhost and the launcher dev team to work on a solution for everyone.
Per Luke from Creeperhost: On your forum thread, can you ask people to ping new.creeperrepo.net and post results?
Hello,
Glad to see some information gathering.
You can guarantee accuracy of the location you're connecting to, by, on windows, opening command prompt and running 'ping new.creeperrepo.net'
This will return the following;
Code:Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved. C:\Windows\system32>ping new.creeperrepo.net Pinging new.creeperrepo.net [78.129.148.36] with 32 bytes of data: Reply from 78.129.148.36: bytes=32 time=48ms TTL=51 Reply from 78.129.148.36: bytes=32 time=51ms TTL=51 Reply from 78.129.148.36: bytes=32 time=50ms TTL=51 Reply from 78.129.148.36: bytes=32 time=49ms TTL=51 Ping statistics for 78.129.148.36: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 51ms, Average = 49ms
As you can see this gives an IP, this is enough for me to know which machine it is at the least, but if you're actually curious as to where you're connecting, you can try pinging england1.creeperrepo.net, england2.creeperrepo.net, chicago1.creeperrepo.net, chicago2.creeperrepo.net, atlanta1.creeperrepo.net, losangeles1.creeperrepo.net and seeing which matches the IP.
At the moment we're working on a new geo location platform which will increase accuracy for diverting traffic, at the moment the current one is a little 'dumb' and some people even from LA get sent to Chicago or Atlanta instead of to the LA location.
Now thanks to Ash's original post once I was made aware of this thread about 8 minutes ago, I checked the Chicago repo mirror and found it had been rebooted without my knowledge, likely in the night some time recently, and was running the old repo software (for some reason, guess I was tired when I rolled the new stuff out), which would've been causing some pretty serious issues with MD5 hashes.
While I understand this is frustrating, however the importance of information for debugging a system as spread out as the repo is really really important, and I'm glad everyone came together to help collect information.
Hopefully anyone experiencing this from this point forward can include the result from their ping so I can find the machine causing the issues and move forward with resolving it, the chances are it's a 30 second fix, but I don't know where it is broken without you guys!
~Paul T
Last edited: