-
Notifications
You must be signed in to change notification settings - Fork 11
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
Cannot connect to google apps account #24
Comments
Do you have trouble with other jabber servers or just google? Do you happen to use google's 2 step authentication? That's how I do it. I created an app specific password for vimchat and I store that in my vimchat config file. If that file gets compromised, only vimchat running on that computer would be affected. |
The other jabber server I tested was a vanilla gmail account. That one worked, just the google apps account didn't. I will try enabling two-step authentication and see if that works. Should it work without two-step auth? |
Yes, it should work without two-step auth. I used to use it with normal google auth. It is very strange that it works for regular gmail, but not google apps. |
Still not working, though instead of hanging for a bit then throwing an error, it fails immediately. Are there logs anywhere to debug? |
Just poor mans logging. To see them, try running the command |
@paulnorthup Were you able to get this working with your google apps account? I am running into the same issue. |
Just wanted to mention, google is dropping (has dropped?) support for xmpp anyway http://slashdot.org/story/13/05/20/2315216/google-drops-xmpp-support |
My bad, I did not mean to close this issue. @jwalgran I never did get it working, thought it looks like there isn't hope with google dropping xmpp. |
@ironcamel From the article you linked
Looks like there is still hope for independent XMPP clients. |
When I enter my credentials for a google apps account, vimchat hangs for 30s to 1 minute, then cannot connect. I may be doing something wrong, but would love to use it if there's an easy fix for this.
I'm on OSX 10.8.3 with vim (huge) in iterm2
The text was updated successfully, but these errors were encountered: