Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: jason_xtreme on August 12, 2009, 08:13:16 pm
-
I've followed all the instructions i can find but cant seem to get the jabber service in 1.2 to work with my clients.
They are stuck in connection mode. I can see that changes i make take effect such as SSL and domain name but i cant get anyone connected. anyone else here has had a similar problem?
-
Yes, if you're talking about people on the internal network being able to use Jabber -- "interoffice IM." That was something that the developers had targeted to be "fixed" after 1.0, if I understood right, and I looked forward to that, but I haven't able to get it to work yet either.
-
Thank you ill just try to get openfire working again. wasnt a watse tho I learnt alot trying to figure out what was going wrong :)
-
did you see http://trac.ebox-platform.com/wiki/Document/Documentation/Module/Jabber ?
-
Yes, and that's an excellent document. Thank you.
I haven't given up (I could easily be doing something wrong) because this is a functionality I had "sold" to the boss back with 1.0. Still, it's true that I haven't been able to get it to work. So far, it behaves like I remember 1.0 behaving. You can see members of the domain, but you can't communicate with them. I'll need more time to give it a more careful going over.
-
just tried again with ebox-jabber 1.2 and psi 0.12.1-2 and works like a charm. could you post your jabber client version and attach an screenshot of the configuration ?
-
If you don't mind, I'd like to start troubleshooting at the beginning. Pidgin reports that it can't resolve the default Jabber domain "ebox." So the first problem "out of the box" is that "ebox" can't be resolved.
-
If I remember correctly, the ebox-jabber package has been updated fixing some "ebox" domain stuff. Please try to upgrade to the new version to see if that corrects your problem ;)
Regards,
J. A. Calvo
-
Software Management doesn't show an available update. Unless there is a newer version than 1.2.1 of the Jabber module, I'm already up to date. Is there something else I could look at, to provide more information?
-
No, you are right. If you have the 1.2.1 version you are up to date.
As jsalamero says, could you give us a screenshot of your pidgin configuration? maybe there is something wrong...
Regards,
J. A. Calvo
-
Sure. Here you go. Notice the trailing slash in the third image ... that's the only thing I see that seems different from normal.
-
That means "ebox" is not resolved to any IP address.
You must set up a DNS entry indicating "ebox" IP address. You may change jabber domain from "ebox" to "ebox.samgraf.lan" assuming that your local DNS network is "samgraf.lan" and it has a hostname called "ebox" whose IP address is the internal interface eBox address.
Best regards,
-
Right, that's what I said earlier, that "ebox" isn't being resolved. Since that's actually correct behavior "out of the box," I suggest taking an "eBox for Dummies" approach to this, then, and not supply a default Jabber domain, so nobody assumes that that should work. Since it shouldn't. Thanks. :)
I'll give it a try later and report back. I'm looking forward to getting this working.
-
The "ebox" name doesn't need to be resolved in order to make work the jabber service. You only have to put the eBox ip address (or any other domain name that resolves to it) in the field "connect server" of the advanced tab, that you have currently in blank.
Regards,
J. A. Calvo
-
Super. I'll give it another try.
Perhaps that could be added to the documentation?
-
Well, this is interesting -- and encouraging.
I set up Pidgin for an eBox Jabber account on a computer I use, where Pidgin is already in use. Then I installed Pidgin on another computer, and set up another user. Both are XP machines, both are using the same (current) version of Pidgin.
Here's the interesting part. I can see "me" on the other computer in a perfectly normal fashion; online, just as normal. On my computer, the test user appears off line and "not authorized." But it's possible to IM between both machines. So it does work, but not exactly as one would expect if for no other reason than that Pidgin (or Windows) is behaving differently on a per machine basis for the eBox Jabber account only.
So progress is being made. Now if I can sort out the off line/not authorized thing (which will just confuse people on the network), I'm home! :) Thanks for everybody's patience and helpfulness.
-
What is the safest way to "start fresh" with Jabber on a machine already in production? I've done that with Pidgin on the XP boxes but problems persist. I'm thinking maybe I hosed up Jabber with earlier tinkering. In any case, I'd like to start fresh.
-
The pidgin configuration is already on the documentation:
http://doc.ebox-platform.com/en/jabber.html#setting-up-a-jabber-client (http://doc.ebox-platform.com/en/jabber.html#setting-up-a-jabber-client)
About the "start fresh" thing, I'm sorry but I can't understand you (probably because my english is very bad :P)
The "not authorized" stuff it's a very common problem, it also happens often to me with another servers (even google talk). The solution usually is to re-add your friend or ask him/her to re-add you. In some clients there is also a "request authorization" option.
Regards,
J. A. Calvo
-
Your English is MUCH better than my Spanish. :)
The documentation recommended earlier (http://forum.ebox-platform.com/index.php?topic=1733.msg7119#msg7119) is different. There, the server address is blank and the reason it was blank in my setup. ;)
I use Pidgin only with MSN (for a year or so) and have never had to re-authenticate a buddy, so this is new to me. But I want to start as if Jabber was a clean install because now I get a 404 not found when trying to re-authenticate or re-add a user. I am thinking that in my playing around I have somehow "lost" at least some Jabber users and cannot re-add them to Pidgin. So my question was about the safest way to clean up the configuration/installation as if Jabber was a clean install. Sorry I wasn't clearer. :-[
-
Ok, I can understand you now.
First of all, the re-authenticate problem comes always with the Jabber protocol (maybe due to slightly different implementations on the client), so it's normal that you didn't have any problem with MSN.
For the fresh start, I recommend you to execute "apt-get remove --purge jabber.*" and then "apt-get install ebox-jabber".
Hope this helps!
Regards,
J. A. Calvo
-
Executing apt-get remove --purge jabber.* attempts to remove 37 packages -- looks like most or all of eBox. Am I understanding you correctly that this is safe? :)
-
Mmm... most of eBox, maybe it's becuase the jabber event dispatcher. Try with "apt-get remove --purge jabberd.*" that should only remove the jabber server and ebox-jabber related packages. Sorry for the inconvenience.
Regards,
J. A. Calvo
-
No inconvenience at all. And after all, I think I might be the one who messed it up in the first place.
Four packages this time: ebox-all*, ebox-communication*, ebox-jabber*, and jabberd2* -- which sounds safe to me but thought I'd better check.
-
ebox-communication and ebox-all are metapackages that depends on several ebox packages, so if you remove one of them the metapackage gets remove, but this is not harmful at all, you can remove it safely.
-
The reinstall went without problem. At first I was still getting 404s. Then it all started working. I don't know why, but that's OK. Thank you again for your help and patience.
One more question, if I may: Is it possible to connect across a VPN? If so, what would be the correct procedure? I tried making sure that the LAN and VPN subnets could communicate across the firewall on the appropriate ports (5222 and 5269) but it's not working.
-
Could you give us more data? When you say it's not working, which is the error message do you get?
-
No errors. Pidgin just waits to connect. I don't think it's a case of the server not being reachable (we use eGroupware served from the same machine across the VPN connection, for example), but I could very easily be missing something Jabber/Pidgin need beyond reaching the server, something to do with authentication perhaps. As time permits I'll play around some more, to see what I can learn.
-
from the client, check with nmap the ports on the server are open. could you post a screenshot of your client configuration ? what did you set ssl option to in the jabber module ?
-
Sorry, Nmap apparently won't install on my notebook -- fails every time at the Visual C++ installation part. Pidgin screen shots are on page 1, with the difference that the "Connect server" field is filled in (the address at the remote end of the VPN). SSL is set to "Optional" in the Jabber module.
-
Finally got back to this and sorted my mistake with Nmap installation (the Visual C++ package has to be downloaded and installed separately). At the client end of the VPN, Nmap does not report 5222 as being open on the VPN/Jabber server. Neither is it closed. Jabber works on the server's home LAN but connections are not successful across the VPN connection.
-
OK, slowly but surely I'm getting through my eBox to-do list. For completeness, here's the conclusion of my question on Jabber across VPN connections.
Keeping in mind that the server is running both the Jabber and VPN services, the only way I could get Jabber port 5222 open across the VPN was to create a service and set an allow rule on "Filtering rules from internal networks to eBox." Jabber worked fine on the home LAN without the rule, but connections across the VPN were not allowed until I set the rule. I had tried several other approaches to getting it to work, but the firewall rule seems to be what's needed.
If that's not supposed to be the way it works, I'm open to further discussion ... so long as nobody expects me to be real prompt in my replies. :)
Thanks to everybody for their patience and help.