Configuring / Using / Fault Finding Twitter

[TweedleDude]

Hello

Sorry if this causes a massive faux paus, but I have searched and scoured the wiki and forums but have been unable to resolve my issue.

I am using Cumulus 1.9.2 Build 1022
My weather station is WH3080

My setup is behind a proxy / firewall (SWGFL) as I work in a Devon school, but I have opened the SSL 443 port so I thought I was ok. I am able to access twitter through my browser but It appears that I am not getting my twitter tokens as my .ini file displays

OauthToken=unknown
OauthTokenSecret=unknown

I tried tethering my laptop (which is what's running the software and connected to the weather station) with my phone, and although I was able to upload the data to the http://instow.vivatek.co.uk/ website, and I was able to access twitter through my browser but I am still not getting my tokens / tweeting.

I have tried removing the twitter login settings restarting and entering them again.

I have checked and ensured that my laptop is on time and is checking with the NTP sever so it doesn't slip and ensured that my sensor is also synced to the correct time.

I have ensured that my software is installed in C:\Cumulus

The diag folder shows when I was tethering

12/01/2012 11:50:10.136 : Access token response:
12/01/2012 11:50:10.136 : HTTP response code: 0
12/01/2012 11:52:12.209 : FTPRequestDone ftpPutAsync Errcode = 426
12/01/2012 11:55:00.861 : Requesting Twitter tokens
12/01/2012 11:55:05.884 : Socket Error # 10060
Connection timed out.


And this when I am going through the proxy

12/01/2012 12:35:21.900 : Access token response:
12/01/2012 12:35:21.900 : HTTP response code: 0
12/01/2012 12:40:00.821 : Requesting Twitter tokens
12/01/2012 12:40:21.881 : Socket Error # 10060
Connection timed out.


Does the software use the Internet Settings specified in the control panel to access the Internet or do I need to set the proxy settings within Cumulus?


Everything else with my setup appears to work, just this one little niggle, unfortunately I am now at a loss as to what else I can do, check or authorise to make twitter work.

Any ideas or suggestions would be greatly appreciated


Lewis

[steve]

Twitter requires a secure connection and the corresponding code in Cumulus has no support for proxies; sorry. I'm not sure that just opening port 443 will help.

I don't know what 'tethering' is; if it doesn't involve a proxy then I don't know why it doesn't work. You could try turning on the debug log in Cumulus; this will cause extra messages to be logged to the diags files, and also to the debug.log file. But the error you're getting suggests no response from the server, so I don't think the Cumulus logging will help much.

[TweedleDude]

Hi Steve

Thanks for the quick reply.

Tethering, I was attaching my phone and using the data connection through the phone, rather than the schools broadband connection. this would eliminate the proxy issues, so like I said I am unsure why this one feature is not working.

I will try debug mode next time I am in there, maybe there is some clue.

Just out of curiosity, can I remove the laptop from the school and its connection to the weather station & broadband. Then take it home and use my home internet connection to get the tokens and to see if it works on Twitter, or does the software need to have a connection to the weather station in order to work / tweet / establish a connection to twitter?

[steve]

It tries to avoid doing uploads until it has received valid data from a station.

What you could try is to unzip the attachment in this post into a folder and run the application. Put your Twitter user and password into the boxes and click 'Go'. If you get your tokens back, you could try editing them into the cumulus.ini file (with Cumulus stopped).

[TweedleDude]

Excellent, I will try and get someone on site to test this.

Many thanks for helping and I will let you know the outcome.

[steve]

Excellent, I will try and get someone on site to test this.

I suspect that on site it will behave in exactly the same way as Cumulus; it's effectively the same code. You could try it off site, and assuming it works, put the tokens into Cumulus.