SamePlace

SamePlace Installation Failed - XMPP error when connecting to Jabber

Asked by Larry Hohm

SamePlace 0.9.2.2008040512
Firefox 2.0.0.12
xmp4moz 0.6.2.2008042012
Linux RHEL 4

I am having trouble getting started with SamePlace. After downloading SamePlace and restarting Firefox, I stepped through the wizard, trying to connect to my company's Jabber server, inside our firewall. I entered our jabber server's domain name, my username and password, I accepted a warning about our self-signed certificate, and a few other warnings, and I indicated that I was willing to trust the server. Eventually I got an error message about an XMPP authentication error. The connection was never established, and my browser hung for awhile with "waiting for twitter.com ..." displayed in the status bar at the bottom of the screen.

I never got the SamePlace side bar to show up in my browser. I have uninstalled and reinstalled SamePlace twice, and still no SamePlace side bar. When I check Firefox > Tools > Addons I can see SamePlace and xmp4moz; however, for SamePlace the Preferences button is disabled.

I would like to try SamePlace because it looks promising -- but I cannot get started, and I don't know what to try next. Any ideas?

Question information

Language:
English Edit question
Status:
Solved
For:
SamePlace Edit question
Assignee:
No assignee Edit question
Solved by:
Larry Hohm
Solved:
Last query:
Last reply:
Revision history for this message
Massimiliano Mirra (bard-hyperstruct) said : 		#1

Hi Larry,

any chance you could have entered the wrong password? The error you get would imply that connection was established but the next stage, authentication, went wrong. If you want, I can look into the specific reason, I'll need a log as produced by the development version, Help Menu -> Save XMPP log.

Revision history for this message
Larry Hohm (larry-hohm) said : 		#2

I resolved the problem. When I went back to Firefox > Tools > Add-ons I noticed that the Preferences button was now enabled. (Don't know why it was disabled earlier.) I was able to adjust the settings for our jabber server, to get connected. We have two domain names (old and new) that both resolve to our jabber server. In my early attempts to connect, I was using the new name, but it turns out the self-signed certificate uses the old name. After configuring SamePlace to use the old name, I got connected.

By the way - I strongly recommend to your users to check "automatically login at startup". Originally I left that box unchecked, and I think that is why the SamePlace sidebar never appeared in my browser. That made it difficult to trouble-shoot problems during the first-time connection.