Ali_a

Results 3 comments of Ali_a

I experienced the same problem, and when I disabled my HTTP proxy, the issue was resolved!

I'm currently using version 1.0.5, and this error no longer appears, regardless of the proxy settings.