Sandaysoft

The connect timeout in the component used by the test app (and Cumulus) is 2 minutes by default, I believe. That message is coming from Winsock, so Windows is timing out before the application.

It looks very much like something is blocking the connect attempt.

_________________
Steve
Sanday Weather
----------------------------------------------------------------------------------------------------------------------------------
Like Cumulus and want to support it? Please donate!

Ok wow that's freaky. When I use my 3G datacard from my laptop it works fine.
Time to go debug my router. Thanks for the time, and apologies for any wasted.

After manually copying the oAuth strings I got when using the data card, Twitter updates work from the main PC.
Very, very weird. Other https sites work fine.

I have the same problem, just will not tweet anything, I have tried redoing the tokens as stated in a prev post, have re booted router, pc. But it just will not tweet. Mine stopped working on the 27/07 the day before I went on holiday I am on v1.9.0.

Anyone got any ideas??

_________________

Are you getting exactly the same error as in the first post in this thread?

_________________
Steve
Sanday Weather
----------------------------------------------------------------------------------------------------------------------------------
Like Cumulus and want to support it? Please donate!

I donk know what it was but it has started working again.

_________________

When I discovered the Twitter option (on v1.9.0 955) the other day I switched it on for my default twitter a/c and it was working fine. I then created a new twitter a/c just for the wx and it didn't work. (no info, just didn't update. I reverted back to my normal a/c and it now doesn't work either. I tried your twitter test prog, and this comes up with a popup box 'HTTP/1.1 401 Unauthorized' error for both a/cs. My twitter client is working fine. Any suggestions please?

There's an assumption that you will only use one Twitter account with Cumulus; it saves the authentication strings in cumulus.ini. To switch accounts, you have to delete the "OauthToken=" and "OauthTokenSecret=" lines before starting Cumulus, so it gets the new strings.

I don't know why it didn't work when you switched back, except I see that mine hasn't updated for the last 12 hours. I'll see if I can find out why that is; Twitter often seem to have problems.

The '401' problem while trying to authenticate has also been reported by someone else on the Twitter development forum.

_________________
Steve
Sanday Weather
----------------------------------------------------------------------------------------------------------------------------------
Like Cumulus and want to support it? Please donate!

I turned logging on for mine and it's also getting 401. I guess we'll have to wait till Twitter fix the problem, it's already been reported.

_________________
Steve
Sanday Weather
----------------------------------------------------------------------------------------------------------------------------------
Like Cumulus and want to support it? Please donate!

It appears that they fixed a bug in Twitter where they were accepting timestamps which were off by a long way (so now they don't). This exposed a bug in the library routine I use to calculate a Unix timestamp where it didn't take daylight savings into account. I've fixed this in build 956:

http://www.nybbles.co.uk/downloads/beta190/CumulusSetup.exe

_________________
Steve
Sanday Weather
----------------------------------------------------------------------------------------------------------------------------------
Like Cumulus and want to support it? Please donate!

[quote="steve"]It appears that they fixed a bug in Twitter where they were accepting timestamps which were off by a long way (so now they don't). This exposed a bug in the library routine I use to calculate a Unix timestamp where it didn't take daylight savings into account. I've fixed this in build 956:

Steve you're a star - works perfectly now, thanks!