Right, so after putting the file into “/” it now seems to be parsing it ok (I’ve replaced a few characters with xxx for security) :
23:51:18.586 DEBUG - oAuthConsumerKey: xTkBLxxxxxxxxxxxxkcPD
23:51:18.590 DEBUG - oAuthConsumerSecret: **************************************************
23:51:18.590 DEBUG - oAuthAccessToken: x22x4601-4GyZhtsxxxxxxxxxxxxxxxk92O
23:51:18.592 DEBUG - oAuthAccessTokenSecret: *********************************************
23:51:18.592 DEBUG - oAuth2TokenType: null
23:51:18.593 DEBUG - oAuth2AccessToken: null
23:51:18.593 DEBUG - oAuth2Scope: null
23:51:18.593 DEBUG - oAuthRequestTokenURL: https://api.twitter.com/oauth/request_token
23:51:18.594 DEBUG - oAuthAuthorizationURL: https://api.twitter.com/oauth/authorize
23:51:18.594 DEBUG - oAuthAccessTokenURL: https://api.twitter.com/oauth/access_token
23:51:18.595 DEBUG - oAuthAuthenticationURL: https://api.twitter.com/oauth/authenticate
23:51:18.596 DEBUG - oAuth2TokenURL: https://api.twitter.com/oauth2/token
23:51:18.596 DEBUG - oAuth2InvalidateTokenURL: https://api.twitter.com/oauth2/invalidate_token
23:51:18.597 DEBUG - restBaseURL: https://api.twitter.com/1.1/
23:51:18.597 DEBUG - streamBaseURL: https://stream.twitter.com/1.1/
23:51:18.598 DEBUG - userStreamBaseURL: https://userstream.twitter.com/1.1/
23:51:18.598 DEBUG - siteStreamBaseURL: https://sitestream.twitter.com/1.1/
23:51:18.599 DEBUG - uploadBaseURL: https://upload.twitter.com/1.1/
23:51:18.599 DEBUG - dispatcherImpl: twitter4j.DispatcherImpl
23:51:18.600 DEBUG - asyncNumThreads: 1
23:51:18.600 DEBUG - loggerFactory: null
But the error is different now (I have triple checked the keys - I have tried both the widgets Access token as well as the token generated on the Twitter Dev console)
23:52:11.880 TRACE - Incoming TwitMessage{id=2126, command=Tweet, length=14, body=‘Alarm On’}
23:52:11.940 DEBUG - Request:
23:52:11.940 DEBUG - POST https://api.twitter.com/1.1/statuses/update.json
23:52:11.947 DEBUG - OAuth base string: POST&https%3A%2F%2Fapi.twitter.com%2F1.1%2Fstatuses%2Fupdate.json&include_entities%3Dtrue%26oauth_consumer_key%3xxxkBLMSMQxxxx99TzxxPD%26oauth_nonce%3D1xxx533xx44%26oauth_signature_method%xxxHMA$
23:52:11.960 DEBUG - OAuth signature: RVItnzxxxxxxT9Srcxxp+/EU=
23:52:11.966 DEBUG - Authorization: ********************************************************************************************************************************************************************************************************$
23:52:11.967 DEBUG - X-Twitter-Client-Version: 4.0.2
23:52:11.967 DEBUG - X-Twitter-Client-URL: http://twitter4j.org/en/twitter4j-4.0.2.xml
23:52:11.967 DEBUG - X-Twitter-Client: Twitter4J
23:52:11.967 DEBUG - User-Agent: twitter4j http://twitter4j.org/ /4.0.2
23:52:11.967 DEBUG - Accept-Encoding: gzip
23:52:11.968 DEBUG - Post Params: status=Alarm%20On&include_entities=true
23:52:19.018 DEBUG - Response:
23:52:19.020 DEBUG - date: Mon, 22 Aug 2016 21:52:18 GMT
23:52:19.021 DEBUG - HTTP/1.1 401 Authorization Required
23:52:19.021 DEBUG - set-cookie: guest_id=v1%3A147xxxx83703345; Domain=.twitter.com; Path=/; Expires=Wed, 22-Aug-2018 21:52:18 UTC
23:52:19.022 DEBUG - server: tsa_f
23:52:19.022 DEBUG - content-length: 89
23:52:19.022 DEBUG - x-tsa-request-body-time: 3
23:52:19.023 DEBUG - x-response-time: 96
23:52:19.023 DEBUG - x-connection-hash: d9b1xxxx6b409xxxxx8b79xxxx0cc
23:52:19.023 DEBUG - content-encoding: gzip
23:52:19.024 DEBUG - content-type: application/json; charset=utf-8
23:52:19.024 DEBUG - strict-transport-security: max-age=631138519
23:52:19.359 DEBUG - {“errors”:[{“code”:32,“message”:“Could not authenticate you.”}]}
23:52:19.396 ERROR - Error sending twit for user xxx@xxx. Reason : 401:Authentication credentials (https://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access tok$
message - Could not authenticate you.
code - 32