Modify

#1297 closed defect (duplicate)

GTalk: Certificate verification problem 0x14

Reported by: adrianna.pinska@… Owned by:
Priority: major Milestone:
Component: Jabber Version: devel
Keywords: gtalk, oauth, certificate Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description

This just started happening (server: im.bitlbee.org:6697; username/password edited out):

08:30:46 <root> Welcome to the BitlBee gateway! 08:30:46 <root> 08:30:46 <root> Running BitlBee 3.5.1+20171005+master+27-g861de54-git 08:30:46 <root> 08:30:46 <root> If you've never used BitlBee before, please do read the help information using the help command. Lots of FAQs are answered there. 08:30:46 <root> If you already have an account on this server, just use the identify command to identify yourself. 08:47:28 <> identify 08:47:28 <root> Password accepted, settings and accounts loaded 08:47:28 <root> Trying to get all accounts connected... 08:47:28 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:47:28 <root> jabber - Logging in: Signing off.. 08:47:28 <root> jabber - Logging in: Reconnecting in 5 seconds.. 08:47:33 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:47:33 <root> jabber - Logging in: Signing off.. 08:47:33 <root> jabber - Logging in: Reconnecting in 15 seconds.. 08:47:48 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:47:48 <root> jabber - Logging in: Signing off.. 08:47:48 <root> jabber - Logging in: Reconnecting in 45 seconds.. 08:48:33 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:48:33 <root> jabber - Logging in: Signing off.. 08:48:33 <root> jabber - Logging in: Reconnecting in 135 seconds..

Attachments (0)

Change History (2)

comment:1 Changed at 2017-10-11T06:57:28Z by adrianna.pinska@…

Argh, sorry! Should have previewed! Here's the log properly formatted:

08:30:46 * Topic for &bitlbee is "Welcome to the control channel. Type help for help information."
08:30:46 * Topic set by root!root@im.bitlbee.org on 2017-10-11 06:30:46 UTC
08:30:46 <root> Welcome to the BitlBee gateway!
08:30:46 <root>  
08:30:46 <root> Running BitlBee 3.5.1+20171005+master+27-g861de54-git
08:30:46 <root>  
08:30:46 <root> If you've never used BitlBee before, please do read the help information using the help command. Lots of FAQs are answered there.
08:30:46 <root> If you already have an account on this server, just use the identify command to identify yourself.
08:47:28 <********> identify ********
08:47:28 <root> Password accepted, settings and accounts loaded
08:47:28 <root> Trying to get all accounts connected...
08:47:28 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer)
08:47:28 <root> jabber - Logging in: Signing off..
08:47:28 <root> jabber - Logging in: Reconnecting in 5 seconds..
08:47:33 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer)
08:47:33 <root> jabber - Logging in: Signing off..
08:47:33 <root> jabber - Logging in: Reconnecting in 15 seconds..
08:47:48 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer)
08:47:48 <root> jabber - Logging in: Signing off..
08:47:48 <root> jabber - Logging in: Reconnecting in 45 seconds..
08:48:33 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer)
08:48:33 <root> jabber - Logging in: Signing off..
08:48:33 <root> jabber - Logging in: Reconnecting in 135 seconds..

comment:2 Changed at 2017-10-12T08:36:23Z by wilmer

Resolution: duplicate
Status: newclosed

Modify Ticket

Action
as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.