-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac client keeps contacting the server when new authorization is being issued #502
Comments
@maxadamo: The "Getting server info" step doesn't need any authorization tokens. The next step (getting the available profiles) needs authorization, but the log indicates the next step didn't start. (The "Request explicitly cancelled" is when you toggled the switch off, I presume.) If the app is stuck at "getting server info" for 40 secs, it might mean there was a problem with the network. Do you think that might have been possible? Are you able to connect now, or are you still facing this problem? |
Please reopen if you're still facing this problem. |
@roop I'm not re-opening for now (I also know that you have a new Go client in the works, and I can live with this glitches) but I don't think that I had a problem with the network. I hear also from other colleagues that from time to time they have to have this problem. with Mac. |
@roop do you mind re-opening the ticket? I'm not allowed. |
I also experienced such a problem, and sometimes, it connected to the server successfully but cannot open any website. However, the network was accessible again after I closed the connection to EduVPN. |
I have been using the Linux client for more than 3 years, and I have never seen an issue.
Since I use the client for Mac, I am experiencing a problem when the token has to be renewed, and the client keeps trying to contact the server as follows:
Unfortunately, the logs do not seem to be very chatty, but you can see that there is 40 seconds timeout until I terminate the application, otherwise, it hangs in an endless operation:
The text was updated successfully, but these errors were encountered: