Tue Sep 19, 2017 7:14 am by bob
Looking through ISBEL code, the timeout is being set to 5 seconds for both 1 and 2, so if the response is taking longer than that, then that will be the problem. Maybe the CCP launcher has a longer wait time. A longer response time will depend on a number of factors, not the least of, where you are located.
If, as you said before, it works when you reset your modem, then presumably any issue is not with your computer or any software on it, but rather the device itself is shutting down the connection? (IDK, but that would be my guess based on the information provided). The requests that ISBEL is making are standard webrequests on HTTPS, so it does seem a little odd. Of note, the URI's being used do have some hard coded values in them, for referrers and things which are needed regarding redirects and language, which might cause issues if the login of your account somehow is objecting to that, which if I had to guess could be due to language settings, but IDK, that's just a guess (again).
As we aren't seeing the issue in a wider audience, then it really requires a deeper bit of troubleshooting for your particular setup, which, as we are not there, is really up to you if you want to use the ISBEL. It is open source, so you are free to get it, and modify it as necessary to make it work for you. The alternative is to wait until some additional tracing can be added to see if it can help track down your issue.