Truly it would be most beneficial if you did post the solution rather than deleting the thread. Plenty of times I had a question to ask I would create a thread, and then when nobody was able to resolve my queries I would eventually find my own solution just as you appear to have done here.
However, it's reasonable to assume one's problem could easily happen to others so as a courtesy I have always posted my solutions as well. It would be awesome if you did the same.
Based on your error I'm guessing you configured your proxy incorrectly and resolved it by correcting that error either within your actual browser settings, or within the account settings for the effected account in followliker. Is that correct, or if not - how did you resolve this challenge?
How did you solve this problem? I have had this for 3 days and Support is suuuuper slow on responding.. First suggestion was to restart and that was suggested yesterday..
And don't delete the thread, adding the solution is more helpful..
gturban - your proxy settings are likely incorrect within the followliker account setup or in the proxies section of the FL software. Proxies must be in the correct format as demonstrated in the FL guide. IP

ORT:USERNAME

ASSWORD ... you probably have a semi-colon ";" somewhere instead of a colon. This error might also be caused by having the proxy incorrectly set in your browser itself, but this is far less likely than a direct PROXY input error within followliker.
Supports general recommendations will include: remove and reinstall, check firewall settings, did your AV(anti-virus - for example AVAST can be quite aggressive in blocking things created with Ubot Studio) block these connections? If so, open the virus chest and add appropriate exceptions to firewall and AV. Check your internet connection, and ensure all appropriate ports are opened. Try the EMAIL test using a Pop3 enabled email account to see if FL connects to the internet that way. If it does, you KNOW something is wrong with your account entry information. Anyway ... one of those solutions should work for you, but honestly you probably typed the proxy wrong ... it's also possible that is just 1 bad proxy, so be sure to try another perhaps.