Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
CumulsMX not updating Twitter...
Moderator: mcrossley
-
DemonTraitor
- Posts: 49
- Joined: Sun 05 Aug 2012 5:50 pm
- Weather Station: Maplin N96GY
- Operating System: Windows 7 Professional x64
- Location: United Kingdom
CumulsMX not updating Twitter...
I have moved CumulusMX build 3039 from a Pi1 to a Pi3, and since then I'm not getting any Twats...
Nothing had changed (apart from the Pi)
I have updated everything, and ran "sudo mozroots --import --ask-remove", which seems to have stopped working.. "Couldn't retrieve the file using the supplied information."
So, how can I turn on a log to check what's going on? I cannot see an option in the Dashboard.
Thank you.
Demon
Nothing had changed (apart from the Pi)
I have updated everything, and ran "sudo mozroots --import --ask-remove", which seems to have stopped working.. "Couldn't retrieve the file using the supplied information."
So, how can I turn on a log to check what's going on? I cannot see an option in the Dashboard.
Thank you.
Demon
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: CumulsMX not updating Twitter...
Instructions for turning on extra ("debug") logging are in this post - https://cumulus.hosiene.co.uk/viewtopic.php?f=27&t=12991
You should also be able to turn it on from the Options section of the Station settings.
There may well be messages about Twitter in the diags file even without debug logging, if it is failing.
If importing the root certificates is failing, it isn't going to work. Someone else had the same problem recently, it seems to be a problem with the server. Retrying can help, and I believe there was a way to use a different server. Searching for "mozroots" should find it.
You should also be able to turn it on from the Options section of the Station settings.
There may well be messages about Twitter in the diags file even without debug logging, if it is failing.
If importing the root certificates is failing, it isn't going to work. Someone else had the same problem recently, it seems to be a problem with the server. Retrying can help, and I believe there was a way to use a different server. Searching for "mozroots" should find it.
Steve
-
DemonTraitor
- Posts: 49
- Joined: Sun 05 Aug 2012 5:50 pm
- Weather Station: Maplin N96GY
- Operating System: Windows 7 Professional x64
- Location: United Kingdom
Re: CumulsMX not updating Twitter...
Thanks Steve. I'll look further 
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: CumulsMX not updating Twitter...
A post here - https://github.com/KSP-CKAN/CKAN/issues/1787 - says that Mozilla have withdrawn this facility and you have to use certmgr instead. I'm not sure how you do that, though. You could try:
mono certmgr.exe -ssl https://api.twitter.com
mono certmgr.exe -ssl https://www.twitter.com
You might need to be in the directory containing the certmgr.exe file, and I don't know where that is. I don't have a Linux box to try this myself at the moment since the lightning took out my Pi2, but I do have an old Pi that I need to set up again when I get chance.
mono certmgr.exe -ssl https://api.twitter.com
mono certmgr.exe -ssl https://www.twitter.com
You might need to be in the directory containing the certmgr.exe file, and I don't know where that is. I don't have a Linux box to try this myself at the moment since the lightning took out my Pi2, but I do have an old Pi that I need to set up again when I get chance.
Steve
-
DemonTraitor
- Posts: 49
- Joined: Sun 05 Aug 2012 5:50 pm
- Weather Station: Maplin N96GY
- Operating System: Windows 7 Professional x64
- Location: United Kingdom
Re: CumulsMX not updating Twitter...
Oh, thanks.. I shall try this out... just enabled logging... could not find the option before... *blind*
Demon
Demon
-
DemonTraitor
- Posts: 49
- Joined: Sun 05 Aug 2012 5:50 pm
- Weather Station: Maplin N96GY
- Operating System: Windows 7 Professional x64
- Location: United Kingdom
Re: CumulsMX not updating Twitter...
2016-07-26 19:54:02.246 Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from server. Error code: 0xffffffff800b010a
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.RemoteValidation (Mono.Security.Protocol.Tls.ClientContext context, AlertDescription description) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X509CertificateCollection certificates) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:Process ()
at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStream handMsg) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Net.Http.HttpResponseMessage].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<HttpPostAsync>d__39.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.String].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<PostAccessTokenAsync>d__15.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.XAuthAuthorizer+<AuthorizeAsync>d__1.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at CumulusMX.Cumulus+.MoveNext () [0x00000] in <filename unknown>:0
MXDiags....
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.RemoteValidation (Mono.Security.Protocol.Tls.ClientContext context, AlertDescription description) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X509CertificateCollection certificates) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:Process ()
at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStream handMsg) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Net.Http.HttpResponseMessage].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<HttpPostAsync>d__39.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.String].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<PostAccessTokenAsync>d__15.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.XAuthAuthorizer+<AuthorizeAsync>d__1.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at CumulusMX.Cumulus+.MoveNext () [0x00000] in <filename unknown>:0
MXDiags....
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: CumulsMX not updating Twitter...
That's the error you get when the certificates aren't installed.
Steve
-
DemonTraitor
- Posts: 49
- Joined: Sun 05 Aug 2012 5:50 pm
- Weather Station: Maplin N96GY
- Operating System: Windows 7 Professional x64
- Location: United Kingdom
Re: CumulsMX not updating Twitter...
I did run the commands again, and they say they are installed...
Ahhh, it says the signature is invalid....
grrr
Ahhh, it says the signature is invalid....
grrr
-
DemonTraitor
- Posts: 49
- Joined: Sun 05 Aug 2012 5:50 pm
- Weather Station: Maplin N96GY
- Operating System: Windows 7 Professional x64
- Location: United Kingdom
Re: CumulsMX not updating Twitter...
X.509 Certificate v3
Issued from: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2006 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G5
Issued to: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 EV SSL CA - G3
Valid from: 31/10/2013 00:00:00
Valid until: 30/10/2023 23:59:59
*** WARNING: Certificate signature is INVALID ***
This certificate is already in the CA store.
X.509 Certificate v3
Issued from: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 EV SSL CA - G3
Issued to: OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.2.5.4.15=Private Organization, OID.2.5.4.5=4337446, C=US, OID.2.5.4.17=94103-1307, S=California, L=San Francisco, STREET=1355 Market St, O="Twitter, Inc.", OU=LON3 Point of Presence, CN=twitter.com
Valid from: 21/01/2015 00:00:00
Valid until: 21/01/2017 23:59:59
This certificate is already in the AddressBook store.
No certificate were added to the stores.
Issued from: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2006 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G5
Issued to: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 EV SSL CA - G3
Valid from: 31/10/2013 00:00:00
Valid until: 30/10/2023 23:59:59
*** WARNING: Certificate signature is INVALID ***
This certificate is already in the CA store.
X.509 Certificate v3
Issued from: C=US, O=Symantec Corporation, OU=Symantec Trust Network, CN=Symantec Class 3 EV SSL CA - G3
Issued to: OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.2.5.4.15=Private Organization, OID.2.5.4.5=4337446, C=US, OID.2.5.4.17=94103-1307, S=California, L=San Francisco, STREET=1355 Market St, O="Twitter, Inc.", OU=LON3 Point of Presence, CN=twitter.com
Valid from: 21/01/2015 00:00:00
Valid until: 21/01/2017 23:59:59
This certificate is already in the AddressBook store.
No certificate were added to the stores.
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: CumulsMX not updating Twitter...
Something else to try:
wget https://hg.mozilla.org/mozilla-central/ ... rtdata.txt
sudo mozroots --import --ask-remove --file certdata.txt
wget https://hg.mozilla.org/mozilla-central/ ... rtdata.txt
sudo mozroots --import --ask-remove --file certdata.txt
Steve
-
rad-t2
- Posts: 5
- Joined: Wed 06 Jan 2010 8:03 pm
- Weather Station: WH 1080
- Operating System: Debian 8.5
- Location: Kampinos, Poland
Re: CumulsMX not updating Twitter...
posting to twitter still not working, even after this command:
"wget https://hg.mozilla.org/mozilla-central/ ... rtdata.txt
sudo mozroots --import --ask-remove --file certdata.txt"
does anybody have a solution?
error log:
"wget https://hg.mozilla.org/mozilla-central/ ... rtdata.txt
sudo mozroots --import --ask-remove --file certdata.txt"
does anybody have a solution?
error log:
Code: Select all
2016-08-06 17:40:00.722 Starting Twitter update
2016-08-06 17:40:00.723 Obtaining Twitter tokens
2016-08-06 17:40:02.769 Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from server. Error code: 0xffffffff800b010a
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.RemoteValidation (Mono.Security.Protocol.Tls.ClientContext context, AlertDescription description) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X509CertificateCollection certificates) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:Process ()
at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStream handMsg) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Net.Http.HttpResponseMessage].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<HttpPostAsync>d__39.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.String].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<PostAccessTokenAsync>d__15.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.XAuthAuthorizer+<AuthorizeAsync>d__1.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at CumulusMX.Cumulus+<U+E015>.MoveNext () [0x00000] in <filename unknown>:0
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: CumulsMX not updating Twitter...
Have you tried the following, as suggested above?
mono certmgr.exe -ssl https://api.twitter.com
mono certmgr.exe -ssl https://www.twitter.com
I'm not sure whether you need to use mono for these commands, so possibly
sudo certmgr -ssl https://api.twitter.com
sudo certmgr -ssl https://www.twitter.com
is what is required.
mono certmgr.exe -ssl https://api.twitter.com
mono certmgr.exe -ssl https://www.twitter.com
I'm not sure whether you need to use mono for these commands, so possibly
sudo certmgr -ssl https://api.twitter.com
sudo certmgr -ssl https://www.twitter.com
is what is required.
Steve
-
rad-t2
- Posts: 5
- Joined: Wed 06 Jan 2010 8:03 pm
- Weather Station: WH 1080
- Operating System: Debian 8.5
- Location: Kampinos, Poland
Re: CumulsMX not updating Twitter...
Yes I did.
I think this is the problem:
Code: Select all
Mono Certificate Manager - version 3.2.8.0
Manage X.509 certificates and CRL from stores.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.
X.509 Certificate v3
Issued from: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert High Assurance EV Root CA
Issued to: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert SHA2 High Assurance Server CA
Valid from: 2013-10-22 12:00:00
Valid until: 2028-10-22 12:00:00
*** WARNING: Certificate signature is INVALID ***
This certificate is already in the CA store.
X.509 Certificate v3
Issued from: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert SHA2 High Assurance Server CA
Issued to: C=US, S=California, L=San Francisco, O="Twitter, Inc.", OU=Twitter Security, CN=api.twitter.com
Valid from: 2016-06-29 00:00:00
Valid until: 2019-09-19 12:00:00
This certificate is already in the AddressBook store.
No certificate were added to the stores.
Code: Select all
*** WARNING: Certificate signature is INVALID ***- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: CumulsMX not updating Twitter...
I think it's the api.twitter.com certificate which is the one that matters, and that appears to be correct. I'm afraid I have no idea why you get the error when the certificate is apparently valid. Twitter is a complete pain.
Steve
-
rad-t2
- Posts: 5
- Joined: Wed 06 Jan 2010 8:03 pm
- Weather Station: WH 1080
- Operating System: Debian 8.5
- Location: Kampinos, Poland
Re: CumulsMX not updating Twitter...
I've made upgrade to mono 4.4.2 (from 3.2.8) to try resolve problem with certification, and now cumulus lost connection via usb to station. 