_p.png "Advocate")
Advocate
•
635 Messages
App Login Issue
I checked my app to see when the system was turned off and had to sign in (the last time I used the app, I was signed in). After pressing the "Sign In" button, I encountered the following message:
"Your connection is not private
Attackers might be trying to steal your information from auth.simplisafe.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
To get Chrome's highest level of security, turn on enhanced protection"
When I clicked Advanced, I saw the following:
"auth.simplisafe.com normally uses encryption to protect your information. When Chrome tried to connect to auth.simplisafe.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be auth.simplisafe.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit auth.simplisafe.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later."
I did not sign in. Is anyone else experiencing this problem? The app is updated (4.3.0 Android), Chrome is updated, and I am on my home Wi-Fi network. I was able to sign in on my computer without encountering the error (with Chrome). I am at a loss. I do not know if it is a SimpliSafe issue or not. There is no chance my phone has any malware, spyware, or viruses.
"Your connection is not private
Attackers might be trying to steal your information from auth.simplisafe.com (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID
To get Chrome's highest level of security, turn on enhanced protection"
When I clicked Advanced, I saw the following:
"auth.simplisafe.com normally uses encryption to protect your information. When Chrome tried to connect to auth.simplisafe.com this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be auth.simplisafe.com, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit auth.simplisafe.com right now because the website uses HSTS. Network errors and attacks are usually temporary, so this page will probably work later."
I did not sign in. Is anyone else experiencing this problem? The app is updated (4.3.0 Android), Chrome is updated, and I am on my home Wi-Fi network. I was able to sign in on my computer without encountering the error (with Chrome). I am at a loss. I do not know if it is a SimpliSafe issue or not. There is no chance my phone has any malware, spyware, or viruses.
Accepted Solution
worthing
Advocate
•
417 Messages
Il y a 10 m
Second, proceed at your own risk with this. There's very little risk (arguably none, actually) in disabling a root CA that has expired but you have to decide if you want to give it a go or not. You can always re-enable afterwards.
On Android please check the following:
Open Settings application
Select Security
Select Encryption & Credentials
Select Trusted Credentials
Scroll down and look for the following:
"Internet Security Research Group / ISRG Root X1"
Make sure this certificate exists and then click on it and confirm the expiration date is some date in the future. This is the new certificate that replaced the one that expired on 09/30.
While you're in this menu, check for this certificate as well:
"Digital Signature Trust Co. / DST Root CA X3"
Click on that certificate and you should see the expiration date was September 30, 2021. You can disable this certificate, reboot your device and try again to see if it helps. I've seen instances in WIndows where the presence of this certificate caused issues so disabling it to test might be worth your time.
If you're on Apple, I got nothing for you but maybe someone else can chime in or you can Google how to find and check the CA stores.
1
shiherlis
Advocate
•
635 Messages
Il y a 10 m
0
0
worthing
Advocate
•
417 Messages
Il y a 10 m
More info at https://www.darkreading.com/risk/companies-face-issues-as-let-s-encrypt-root-certificate-expires if you're interested.
1
shiherlis
Advocate
•
635 Messages
Il y a 10 m
0
0
davey_d
Community Admin
•
2.9K Messages
Il y a 10 m
Glad to hear that you were able to get logged in after all. Worthing might have been on the right track with that issue relating to the root certificate. We haven't gotten reports of this being widespread, so our site wizards might have already gotten the issue resolved. Are you still seeing the issue when trying to log into the app? Keep me updated!
- Johnny M.
SimpliSafe Home Security
0
0
shiherlis
Advocate
•
635 Messages
Il y a 10 m
Thank you for the response, Johnny. Unfortunately, the error remains (i.e., I logged out and attempted to sign in again via the app only).
Update: I went into the site via my browser on my phone again, signed in, and when I went into the app, it gave the following error message:
"CONNECTION ERROR
The SimpliSafe App is temporarily unavailable
Your home is still secure. App availability does not affect your system or monitoring service. Please try again later."
Logout"
The error was after I was signed into it from my Saturday workaround. So I exited the app, immediately reaccessed it, and received the regular sign-in prompt (within the app itself). This time, the sign-in behaved as it should. So I will leave it alone until later and then test it again, so I do not have any issues while away from home.
Additionally, when trying to reply to your message, Johnny, I encountered the following forum error numerous times:
"403 ERROR
The request could not be satisfied.
Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: 17y20DNpDawKRZEjWiA6nAHC3SikzRvmxNevfsaCZAiA4PtVbE799A=="
I have experienced SimpliSafe errors galore over the past few days.
(edited)
0
0
worthing
Advocate
•
417 Messages
Il y a 10 m
This is definitely a bigger issue than the other expired certificate still hanging around and may cause issues with all kinds of services as this is definitely not a SimpliSafe specific problem.
I'm a little surprised the root CAs for Android 10 don't include the certificate above. Actually, more than a little surprised. When I said "older" above I was thinking Android 8/9 kind of old.
I'm not aware of a way to force a refresh of available root CAs for Android w/o rooting your device by the way. You can probably secure a copy of the certificate and manually import it but I would proceed with extreme caution here. If you import the wrong certificate as a trusted CA you could open yourself to a host of the most serious kinds of security issues.
I'll do some more digging when I have free time and let you know if I find anything.
0
0
whyamistilltalking
21 Messages
Il y a 10 m
@Johnny M I wasn't able to log onto to the SimpliSafe forums until I manually installed a new certificate, so that maybe why you haven't heard from many people that are having the problem, that can't log on! I spent the last several hours troubleshooting my browsers (because that's what I assumed the problem was) Luckily I found Worthing's post
0
0
worthing
Advocate
•
417 Messages
Il y a 10 m
Glad you found the post helpful!
The only issue I've found related to the root CA expiration was with a WIndows 10 system and a web service I use. In that case, the new root CA was there but the presence of the old and expired root CA was an issue. Once I (backed it up first) and deleted the old certificate everything worked just fine.
There will be different fixes for different systems and services which makes troubleshooting and fixing even more challenging.
0
0
whyamistilltalking
21 Messages
Il y a 10 m
Yes Windows systems, I believe going back to XP SP3, will update their root certificates. But that is a newer feature for Macs, that Apple added only to a few of their most recent operating systems.
0
0
shiherlis
Advocate
•
635 Messages
Il y a 10 m
Again, thank you for all of your help, Worthing. I doubt I would have figured it out. I am uncertain as to why the Root CA was missing. Perhaps with some spare time on my hands, I will research it.
0
0
worthing
Advocate
•
417 Messages
Il y a 10 m
Yikes. Sorry to hear about this. Is the app not compatible with Android 11? That seems really unlikely so maybe purge the cache, reinstall, reboot, etc. and contact support.
In this instance you should be able to have your cake and eat it too.
0
0
cezornow
6 Messages
Il y a 10 m
I'm running Android 7.0 because my phone is several years old and doesn't support any newer versions.
Any news on other fixes/workarounds?
0
0
captain11
Captain
•
4.6K Messages
Il y a 10 m
0
0
hondaman88
Advocate
•
108 Messages
Il y a 10 m
It was at the bottom of the iOS post.
0
0