unable to connect to Arlo: authentication failed #778
Comments
|
Anything in And can you try deleting |
|
Same problem here. |
Yes I tried to remove aarlo/session.pickle & restart Please have a look on a part on my log ;) Sorry, you have been blockedYou are unable to access ocapi-app.arlo.comCloudflare Ray ID: xxxxxxxxxxxx • Performance & security by Cloudflare <script>(function(){function d(){var b=a.getElementById("cf-footer-item-ip"),c=a.getElementById("cf-footer-ip-reveal");b&&"classList"in b&&(b.classList.remove("hidden"),c.addEventListener("click",function(){c.classList.add("hidden");a.getElementById("cf-footer-ip").classList.remove("hidden")}))}var a=document;document.addEventListener&&a.addEventListener("DOMContentLoaded",d)})();</script>2023-07-06 19:31:36.136 DEBUG (MainThread) [zigpy.appdb] SQLite version for <module 'sqlite3' from '/usr/local/lib/python3.10/sqlite3/init.py'>: 3.40.1 |
|
Same here, tried downgrading to all other versions and also tried the new v18 just released, still dosen't work :( aarlo: reconnect_every: 90backend: sse |
|
It's the Also, one guy found that changing the # change this
self._session = cloudscraper.create_scraper()
# to this
self._session = cloudscraper.create_scraper(ecdhCurve='secp384r1') |
There is alot of info in my log, but it seems like it's the same output "login try 1,2,3..." So i will only post the first one, please let me know if there is anything else you need. BTW, that line is in file backend.py and not background.py, and it didn't make it work for me :( Thanks!
|
|
I'm having the same issue since yesterday (July 5, 2023). I had thought it was because of 2FA (my delegated account hadn't required to have 2FA enabled yet), so I ended up enabling 2FA, in hopes that it would fix the issue. It did not... I have tried:
I'm assuming the fact that I don't get the email 2FA nor a Push 2FA notification means that Aarlo isn't getting past the logon. If it helps, please see below for my configuration.yaml excerpt. As a footnote, I have configured my Google account to have 2-Step Verification enabled and I have also created the App Specific Password. (I have even Enabled Less Secure Apps.) So, this should all work once the logon issue is resolved. |
|
same problem here from last update.. |
|
Same problem here since yesterday which is when I updated to the latest version. configuration.yamlLog
Unfortunately this did not work for me either. |
This did not work for me either. However, please see attached for my home-assistant.log file. I did not enable the entire list of custom_components.aarlo.xxx. But, I did enable Verbose Log. |
|
Hello @twrecked . |
|
Same issue here; integration reports |
I gave this a go but no joy - by the way the code is in backend.py You probably know this but I have taken a look at the cloudflare docs and it seems Arlo have setup a rule to block certain requests, e.g. empty query strings. Problem is without knowing the rules it is hard to know what they don't like about the aarlo request. My guess is that they expect some random request property to stop replay attacks - well that is what I would do. |
The response I see in the debug log is that Cloudflare says I need to enable cookies. |
Out of interest where do you see that? |
I've run into the same issue as pretty much everyone else in this thread. Tried deleting |
By adding into configuration.yaml |
|
I took a look at my home-assistant.log file and pulled out the concerning excerpts from the log: The password found in this section of the log does not coincide with what I have in my secrets.yaml file, does it mask it when logging the activity? An error regarding cookies: Error regarding a screenshot: And, finally, "Why have I been blocked?": Thanks, @twrecked for all that you do for this project and Home Assistant! |
|
@sological @usedjeans818 I might be wrong but not sure you're reading the html response correctly, the code allows for those issues but it depends on what is sent by a browser and we can't see that. |
|
@usedjeans818 We base64 encode the password that's why it looks different. You can try pasting your password in here and seeing if it lines up. As for the cookies and being blocked, I have no idea. cloudscraper should provide the cookies and Cloudflare is seeing something it doesn't like and is blocking you. But I don't know what that is. We line up our packets as close as possible to the ones sent by the web browser and that seems to work. It works for me and once it's working it just keeps on working until Arlo changes so it's hard to debug at this end. One thing to try might be changing your user agent. |
|
What is the user agent? |
|
For ref. A user agent is what a browser (e.g. chrome, edge) sends to identify itself. Don't know how to change it though, reading the cloudscraper docs I thought this was randomized. |
|
Now experiencing the same issue in NZ as of 8th July. Looks like whatever change Cloudflare or Arlo made has rolled out fully. Aarlo attempts to setup, but no 2FA code request is received at the app. |
@twrecked I just tried Neither "linux" nor "apple" worked to resolve the issue. |
|
I also just tried editing my /etc/hosts file (as suggested from It's Not Working, and switched "commenting out" between the two entries and neither worked. However, did the servers change IPs? I ran an nslookup on my desktop and ocapi-app.arlo.com resolved to: I also tried forcing connections between these two IPs and that did not help either. |
|
Try to change user agent to linux, apple -> Not working @twrecked Any idea? Thx for your help |
@juju159 where do you see this? I see it in the logs in a bunch of HTML but not convinced it is the error. |
Same problem here with brand new setup. I also try everything mention in this thread but no success. I'm blocked by cloudflare. |
Same on my side, blocked by cloudflare protection. |
|
Thanks for the honourable mention; https://github.com/twrecked/hass-aarlo/releases/tag/v0.7.4b19 |
|
Hi, back, sorry for the late response, I've been away. |
|
hi, |
|
Still failing for me in b19 2023-08-06 21:07:16.157 ERROR (SyncWorker_3) [pyaarlo] authentication failed |
|
Still failing for me as well after the update to b19 |
|
It seems that the problem is inherent in the home assistant request. If you log in via the web with the same credentials everything works correctly so it's not a user and password problem. It works even if I use the same credentials in the Arlo mobile app. |
|
Failing for me on b19 as well. Was working ok before updating to b19 (I had it working before due to making the changes to lines 659 and 854 in early July). UPDATE: @sgnagnarella and @cambuehl delete the pickle file and reboot the system. It should then work fine on b19 |
This was the fix for me. Thank you! I was only reloading the yaml config not doing a full system restart. Thanks for the info @townsmcp |
Did not work for me. Still no Arlo. |
|
Ok, follow the below and see how it goes for you:
|
Thank you for the suggestion. I've already went through that process once, and just tried it two more times today. Same results as before, home assistant is unable to connect to arlo. |
|
This got back to work again after I migrated HA from a laptop to a NUC. I
wonder if aarlo is blocking certain mac-addresses. Have you tried
regenerating the Mac Address for your VM?
…On Fri, Aug 11, 2023 at 4:27 PM cambuehl ***@***.***> wrote:
@cambuehl <https://github.com/cambuehl>
Ok, follow the below and see how it goes for you:
1. removed the aarlo addon also disable the aarlo section in the
configuration
2. reboot the host (not restart home assistant)
3. delete the aarlo.pickle file in .aarlo folder.
4. redownload the aarlo addon and enable its aarlo in the configuration
5. reboot the host
Thank you for the suggestion. I've already went through that process once,
and just tried it two more times today. Same results as before, home
assistant is unable to connect to arlo.
—
Reply to this email directly, view it on GitHub
<#778 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN4U6FKOGPPQZGMZVXUTFDXU2ITLANCNFSM6AAAAAA2AWFK7Y>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@twrecked First up thanks for your amazing tools and I ask this as someone with no real python coding experience. I notice you are supplying a User-Agent in an attempt to support the various streams and wonder if that may be the reason we all keep getting blocked by Cloudflare? The cloudscraper documentation seems to warn against doing this: https://github.com/venomous/cloudscraper#user-agent-handling
It seems cloudscraper does provide some options for limiting the user agents that it uses which might still help support the approach you're trying? https://github.com/venomous/cloudscraper#browser--user-agent-filtering |
|
just to jump in with my experience here with the same problem of authentication error. the last 2fa auth email i got was july 27 and 18th before that. Not sure exactly when it stopped working but sometime in later July. im on ubuntu bare metal, everything in docker. i was on a much older version that i couldn't update because HACS was giving me problems. I got around to removing and reloading HACS and then i was able to update integrations. I went to 19, and it didn't fix, but i didn't try to delete the pickle file and i was not rebooting the entire system, just a full ha reboot / stop start container. instead as per another issue #782 i removed aarlo entirely from HACS and then installed b12 and comented out line 644 in the backend.py re arlocamweb. after i restarted HA it worked again. i'll try to test b19 more fully with the steps mentioned above here and report back in a few days. Thanks twrecked for all of your work and to everyone contributing here. |
|
I am getting blocked by cloudflare "Source": "arloCamWeb" commented or not |
|
I've managed to resolve it by changing line 854 from self._session = cloudscraper.create_scraper(ecdhCurve='secp384r1') |
|
After days of being down and trying all sorts of things described in this thread, and more, I finally removed all cloudscraper options. And now it works... |
Did you delete the session.pickle file also? |
Yes, both pickles where deleted before that when trying other suggestions. |
|
Hi everyone
|
|
You can turn off authentication caching so it doesn't even save the session. https://github.com/twrecked/hass-aarlo#authentication-caching If you only restart home assistant once or twice a week this might be a better setting for you. |
|
Hello everyone, I have been following this thread ever since my Arlo stopped working a little while ago. I’ve since tried different permutations of the various suggestions and realised that some of the cloudscraper config has already made it into the deployment for 7.4. Short is, none of the approaches has given me any luck, so I am wondering if anyone has found a solution that hasn’t been mentioned above. Ie deleting pickles, editing backend in various ways. I am using PUSH for tfa. When I delete the *.pickle files before a restart, I do receive a login request, but still the integration shows the error that “Name does not resolve”, and it takes reference to MQTT. Also when I login to my tfa Arlo account, I get a splash screen “do you trust this browser”, which I assume is the culprit when the integration tries to login, but I can’t see manually trying to turn up as the User Agent that I just whitelisted to be a sustainable solution. If there is anything else I can or should try, I am keen to hear what other suggestions are out there. For the sake of completeness, here is the log: 2023-11-07 22:00:29.615 DEBUG (SyncWorker_1) [pyaarlo] waiting for stream up |
|
I think you are logging in ok. I think the mqtt server is the issue. Try these solutions in turn to fix it:
aarlo:
# your current config
mqtt_hostname_check: False
mqtt_host: mqtt-cluster-z1.arloxcld.com
aarlo:
# your current config
backend: sse |
Thank you @twrecked! Backend: sse did the trick. Sorry, I thought I had read that Arlo had moved to MQTT backend only, so didn’t even consider the sse option. Apologies. |
This configuration finally made Aarlo work! |
|
unbelievable but after month of trying i got it finally to work - awesome...: #Aarlo aarlo: camera:
|
|
Analyzing logs, it point that cloudflare is blocking the configuration of arlo. So, I thought about where I set the URL to let them access my hassio. |
and others
Hello @twrecked
Since the begin of this week, i have authentication failed issue when aarlo plugin is starting up even with the b18 version
unable to connect to Arlo: attempt=1,sleep=15,error=authentication failed
unable to connect to Arlo: attempt=2,sleep=30,error=authentication failed
unable to connect to Arlo: attempt=3,sleep=60,error=authentication failed
unable to connect to Arlo: attempt=4,sleep=120,error=authentication failed.
remove aarlo.pickle has no effect.
Config file
aarlo:
username: xxxxxx@gmail.com
password: xxxxxx
refresh_devices_every: 2
verbose_debug: True
stream_timeout: 120
reconnect_every: 90
backend: sse
save_session: False
BR.
J.
The text was updated successfully, but these errors were encountered: