Bug #200
Sign in fails for encrypted connections with certain setup (Jabber server on different domain)
| Status: | Closed | Start date: | 07/03/2012 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | v12 - March Mantra | |||
| Component: |
Description
Hi,
when signing in, I get this error notification:
Gibberbot: domain check failed
*.hosted.im:hosted.im does not contain 'simplicidade.org' or 'simplicidade.org'
Service record (SRV record) _xmpp-client._tcp.simplicidade.org points to hosted.im. The hosted.im certificate is alright but it's not checked correctly by Gibberbot. IIRC I haven't seen this error in version 0.0.8-FINAL.
Workaround:
Go to "Advanced Account Settings" and set "Connect Server" to one that's defined per service record (SRV record) in the DNS (in the example above you would check for _xmpp-client._tcp.example.com using dig or nslookup). BTW, "Connect Server" seems to be a textarea instead of a textbox.
Keep up the good work! Guess it's time for a donation.
/H
Associated revisions
Merge pull request #200 from n8fr8/v11-beta-bug-fixes
V11 beta bug fixes
History
#1 Updated by n8fr8 almost 5 years ago
- Target version set to v12 - March Mantra
#2 Updated by n8fr8 over 4 years ago
- Status changed from New to Resolved
The new Certificate prompt dialog should handle cases like this where we need to pass the trust option to do the user.
#3 Updated by n8fr8 about 4 years ago
- Status changed from Resolved to Closed