Connection refused(something about java?)

[SerenityHaven]

I recently tried downloading the ftb client and the console will say the following;
Connection refused: connect: java.net.ConnectException: Connection refused: connect
Unhandled exception in Thread[Thread-2,5,main]: java.lang.NullPointerException
[i18n] Could not retrieve version info, skipping update.: java.net.ConnectException: Connection refused: connect
Failed to load modpacks, loading from backup: java.net.ConnectException: Connection refused: connect
Loading modpack information for modpacks.xml...
Failed to read modpack file - falling back to direct download: java.io.FileNotFoundException: C:\Users\Username\AppData\Roaming\ftblauncher\ModPacks\modpacks.xml (The system cannot find the file specified)
Connection refused: connect: java.net.ConnectException: Connection refused: connect
Completely unable to download the modpack file - check your connection: java.net.ConnectException: Connection refused: connect
loading map information...
loading texture pack information...
Connection refused: connect: java.net.ConnectException: Connection refused: connect
Connection refused: connect: java.net.ConnectException: Connection refused: connect
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Not a single modpack will load...Not unleashed, not direwolf, not regular ftb. nothing. please help!
I have no idea what is wrong with it. ive tried to uninstall and re-install again but it didnt fix it.
My Download location is set to Automatic(if that even means anything, probably irrelevant) But yeah, can anyone help me

 

[Hoff]

Identical error for me as well. Working on a solution myself but have yet to find a sensible solution. As a note I can dl modpacks but texture packs and maps do not load at all.

Debug console output: http://pastebin.com/HPgVrM2R

 

[Ashzification]

Please go to this forum thread and report the issue.
http://forum.feed-the-beast.com/thr...ng-please-report-them-here.33823/#post-464556

I apologize for not having a user-level fix at this time. Hopefully the issue is resolved soon.