You are not logged in.

#1 2012-04-28 05:57:32

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

so I recently starting using Bitlbee with Gmail chat and it works just fine... its a really good application. However, I can't connect to Twitter after requesting the 0Auth token.

I am using Weechat 0.3.7 with curses and I am using the localhost for the /connect option. Here is exactly how I made the account:

@ricky | account add twitter edge_breaker
 @root | Account successfully added with tag twitter
 @root | No need to enter a password for this account since it's using OAuth
@ricky | account 1 on
 @root | twitter - Logging in: Connecting
   --->| twitter_edge_breaker (twitter_edge_breaker@twitter)
       | &bitlbee
    -- | Mode &bitlbee [+v twitter_edge_breaker] by localhost        
 @root | twitter - Logging in: Requesting OAuth request token    

after this.. it just hangs... and nothing happens. Should my twitter handle be with @? What could be wrong here?

Offline

#2 2012-04-29 01:30:26

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

After a day or so looking through the wiki pages and trying to see what the problem might be... I still can't find a solution to this problem. Has anyone else experienced this same problem..if so is there an article or bug report that I can take a look at? I am completely stumped on this one.

I think this might have something to do with either SSL or this could be related to something on Twitter's end.

rgedit: I found this message after I turned the account off for twitter:

account 0 off                           │
20:33:21   @root | twitter - Logging in: Signing off..     │
20:33:21   @root | twitter - Logging in: If you're having  │
                 | problems logging in, try re-requesting  │
                 | an OAuth token: account twitter set     │
                 | password ""   

I tried this as well... and nothing happens.

Last edited by rg_arc (2012-04-29 01:34:06)

Offline

#3 2012-04-29 04:13:01

iv597
Member
From: United States
Registered: 2011-09-18
Posts: 96
Website

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

Nothing productive to say here besides "Me too".

No clue what's up, other than the fact that identi.ca is affected, as well.


Currently running Arch on a Samsung Chromebook Pro (dual booted with ChromeOS), and various VPSes and Docker containers.

Dotfiles on Github

Offline

#4 2012-04-29 04:16:22

Jristz
Member
From: America/Santiago
Registered: 2011-06-11
Posts: 1,048

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

@root | twitter - Logging in: Requesting OAuth request token
Requesting OAuth request token
request token

If I read good, They want the "token" you know, the autoritation nuber that twitter give to an app in a acount for runing, the token the inser randomnumber here
in other words I ask?

in tweeter you give autoritation to run this app?
(how i dont know, i use silverbird in chrome, so sorry)


Lenovo ThinkPad L420 modified
:: Intel i7 2560QM :: 8 GB RAM :: SSD 256 GB ::
:: DVD read+Writter :: 3 USB 3.0 Expresa Card ::
:: a Favulous 1 mins lasting Io-Li battery ::cry::

Offline

#5 2012-04-29 08:59:51

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I uncommented the CAfile section of /etc/bitlbee/bitlbee.conf and that caused gmail to not work. So I commented that back again and gmail started working again. So I don't believe it has anything to do with openssl.

Offline

#6 2012-04-30 01:19:37

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

https://dev.twitter.com/docs/api/1/get/oauth/authorize
This explains the 0Auth process... but I haven't found anything enlightening.

Offline

#7 2012-04-30 03:05:26

doug piston
Member
From: Seattle
Registered: 2011-09-11
Posts: 387
Website

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I use bitlbee but I haven't used the twitter side, this thread made me give it a go...

http://wiki.bitlbee.org/HowtoTwitter

^^ I followed that and have twitter up and running within ~5mins. I use Irssi but I would assume the same process would work.


        jarvis@ > account add twitter dougpiston
08:02 @root > Account successfully added with tag twitter
08:02 @root > No need to enter a password for this account since it's using OAuth
08:02        jarvis@ > account on
08:02 @root > Trying to get all accounts connected...
08:02 @root > twitter - Logging in: Connecting
08:02  twitter_dougp > has joined

Last edited by doug piston (2012-04-30 03:07:41)

Offline

#8 2012-04-30 03:14:03

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

ah... maybe when I say account add twitter I put in my actual @----- twitter handle. So you put in your whole name for the account right? Also, you put in account on instead of account 0 on..

Offline

#9 2012-04-30 03:14:28

doug piston
Member
From: Seattle
Registered: 2011-09-11
Posts: 387
Website

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

no "@" but your twitter ID yes.

Last edited by doug piston (2012-04-30 03:15:48)

Offline

#10 2012-04-30 03:22:13

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

mine is black_sphere48 so:

account add twitter black_sphere48
no need to enter a password for this account since it's using 0Auth
account on
Trying to get all accounts connected...
twitter - Logging in: Connecting
(twitter_black_sphere48@twitter) has joined &bitlbee
Mode &bitlbee [+v twitter_black_sphere48]
by localhost
twitter - Logging in: Requesting 0Auth request token

It is still hanging there. Do I have to wait for 5 minutes?

Offline

#11 2012-04-30 03:28:43

doug piston
Member
From: Seattle
Registered: 2011-09-11
Posts: 387
Website

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

On mine I got a message from my twitter account with a link to click that gave me a password. Replied with the password, Bitlbee did the rest. I didn't have to wait at all.

Offline

#12 2012-04-30 03:31:53

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

something must be wrong with my config maybe? I am connecting with localhost... what is your /etc/bitlbee/bitlbee.conf? Maybe that is the problem for me

Offline

#13 2012-04-30 03:39:18

doug piston
Member
From: Seattle
Registered: 2011-09-11
Posts: 387
Website

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I never even touched that. Simply add the twitter account and turned it on. Pm came, I replied. Maybe delete all twitter accounts you added and start over? Sorry I'm not as helpful but seriously it was that simple for me.

Offline

#14 2012-04-30 23:47:04

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I guess I will try removing the package. By the way I am using Bitlbee with the daemon method. If I remove the package and delete all files configurations associated with it and then get the package again... hopefully that will fix this problem. I just don't understand how Facebook and Gtalk both work just fine but Twitter won't authorize.

Offline

#15 2012-05-02 02:50:03

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

Could this be something related to my network settings? I am using the localhost.localdomain setup

Topic set by root (root@localhost.localdomain)

and I have only changed a few settings in my /etc/bitlbee/bitlbee.conf:

## BitlBee default configuration file
##
## Comments are marked like this. The rest of the file is INI-style. The
## comments should tell you enough about what all settings mean.
##

[settings]

## RunMode:
##
##  Inetd -- Run from inetd (default)
##  Daemon -- Run as a stand-alone daemon, serving all users from one process.
##    This saves memory if there are more users, the downside is that when one
##    user hits a crash-bug, all other users will also lose their connection.
##  ForkDaemon -- Run as a stand-alone daemon, but keep all clients in separate
##    child processes. This should be pretty safe and reliable to use instead
##    of inetd mode.
##
RunMode = ForkDaemon

## User:
## 
## If BitlBee is started by root as a daemon, it can drop root privileges,
## and change to the specified user.
##
User = bitlbee

## DaemonPort/DaemonInterface:
##
## For daemon mode, you can specify on what interface and port the daemon
## should be listening for connections.
##
# DaemonInterface = 0.0.0.0
# DaemonPort = 6789

## ClientInterface:
##
## If for any reason, you want BitlBee to use a specific address/interface
## for outgoing traffic (IM connections, HTTP(S), etc.), set it here.
##
# ClientInterface = 0.0.0.0

## AuthMode
##
##  Open -- Accept connections from anyone, use NickServ for user authentication.
##    (default)
##  Closed -- Require authorization (using the PASS command during login) before
##    allowing the user to connect at all.
##  Registered -- Only allow registered users to use this server; this disables
##    the register- and the account command until the user identifies himself.
##
# AuthMode = Open

## AuthPassword
##
## Password the user should enter when logging into a closed BitlBee server.
## You can also have a BitlBee-style MD5 hash here. Format: "md5:", followed
## by a hash as generated by "bitlbee -x hash <password>".
##
# AuthPassword = ItllBeBitlBee   ## Heh.. Our slogan. ;-)
## or
# AuthPassword = md5:gzkK0Ox/1xh+1XTsQjXxBJ571Vgl

## OperPassword
##
## Password that unlocks access to special operator commands.
##
# OperPassword = ChangeMe!
## or
# OperPassword = md5:I0mnZbn1t4R731zzRdDN2/pK7lRX

## HostName
##
## Normally, BitlBee gets a hostname using getsockname(). If you have a nicer
## alias for your BitlBee daemon, you can set it here and BitlBee will identify
## itself with that name instead.
##
# HostName = localhost

## MotdFile
##
## Specify an alternative MOTD (Message Of The Day) file. Default value depends
## on the --etcdir argument to configure.
##
# MotdFile = /etc/bitlbee/motd.txt

## ConfigDir
##
## Specify an alternative directory to store all the per-user configuration
## files. (.nicks/.accounts)
##
ConfigDir = ~/.nicks

## Ping settings
##
## BitlBee can send PING requests to the client to check whether it's still
## alive. This is not very useful on local servers, but it does make sense
## when most clients connect to the server over a real network interface.
## (Public servers) Pinging the client will make sure lost clients are
## detected and cleaned up sooner.
##
## PING requests are sent every PingInterval seconds. If no PONG reply has
## been received for PingTimeOut seconds, BitlBee aborts the connection.
##
## To disable the pinging, set at least one of these to 0.
##
# PingInterval = 180
# PingTimeOut = 300

## Using proxy servers for outgoing connections
##
## If you're running BitlBee on a host which is behind a restrictive firewall
## and a proxy server, you can tell BitlBee to use that proxy server here.
## The setting has to be a URL, formatted like one of these examples:
##
## (Obviously, the username and password are optional)
##
# Proxy = http://john:doe@proxy.localnet.com:8080
# Proxy = socks4://socksproxy.localnet.com
# Proxy = socks5://socksproxy.localnet.com

## Protocols offered by bitlbee
## 
## As recompiling may be quite unpractical for some people, this option
## allows to remove the support of protocol, even if compiled in. If
## nothing is given, there are no restrictions.
## 
# Protocols = jabber yahoo

## Trusted CAs
##
## Path to a file containing a list of trusted certificate authorities used in
## the verification of server certificates.
##
## Uncomment this and make sure the file actually exists and contains all
## certificate authorities you're willing to accept (default value should
## work on at least Debian/Ubuntu systems with the "ca-certificates" package
## installed). As long as the line is commented out, SSL certificate
## verification is completely disabled.
##
## The location of this file may be different on other distros/OSes. For
## example, try /etc/ssl/ca-bundle.pem on OpenSUSE.
##
# CAfile = /etc/ssl/certs/ca-certificates.crt

[defaults]

## Here you can override the defaults for some per-user settings. Users are
## still able to override your defaults, so this is not a way to restrict
## your users...

## To enable private mode by default, for example:

## private = 1

I also have bitlbee listed in the daemon array in /etc/rc.conf...

Last edited by rg_arc (2012-05-02 02:57:51)

Offline

#16 2012-05-03 09:39:16

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I still haven't been able to fix this issue yet. Can someone post their configuration? Possibly their network configuration for bitlbee... I am under the assumption that it has something to do with Twitter itself... but that is just an assumption.

Last edited by rg_arc (2012-05-03 09:40:05)

Offline

#17 2012-05-05 09:48:07

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I found this closed bug report helpful http://bugs.bitlbee.org/bitlbee/ticket/768

Also, was that bitlbee package the bzr version?

Offline

#18 2012-05-07 05:38:22

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I opened up a bug report at Bitlbee.com:

(http://bugs.bitlbee.org/bitlbee/ticket/954)

Offline

#19 2012-05-09 12:17:15

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I think this might have something to do with Twitter updating ssl. I really think this issue has something to do with ssl because I have tried just about everything I can think of. Does anyone else have something to add to shed light on this issue?

Offline

#20 2012-05-12 01:58:45

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

When you get a message for the 0Auth token, how do you receive it? Is the link put on the screen like any other message.. or is the message found elsewhere in the Bitlbee control channel? I still can't find any solution to this issue yet. If anyone is able to log into Twitter successfully can you explain your Bitlbee configuration, what mode are you using, how is "localhost" connecting to the internet. Furthermore, what server configuation are you using for localhost? Is it 127.0.0.1 : 667 or 0.0.0.0 : 667 or anything in particular? I am having a hard time troubleshooting what could be preventing me from getting that 0Auth token.

Offline

#21 2012-05-15 02:38:28

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

*bump*

I still haven't had any luck figuring out what is wrong.

Offline

#22 2012-05-16 13:25:29

rg_arc
Member
Registered: 2011-03-20
Posts: 510

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

I wonder if it has anything to do with a firewall from my internet provider?

Offline

#23 2012-05-19 11:59:20

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,281

Re: Unable to log into Twitter using Bitlbee (Weechat 0.3.7)

Closed on demand of rg_arc.
Continue here: https://bbs.archlinux.org/viewtopic.php … 4#p1103834


To know or not to know ...
... the questions remain forever.

Offline

Board footer

Powered by FluxBB