Unable to re-auth. service not available #670
Comments
|
Same problem here! |
|
same here too! |
|
I confirm this! I‘ve reauthed the other 3 containers of my family yesterday where everything still was working… |
|
Just to mention I'm also impacted. Tried to reauth to no avail |
|
I think issue is happening for everyone. My containers stopped working from yesterday. |
|
Had the same problems. Think Apple has changed something here |
|
No issue authenticating/downloading here. Maybe it's temporary error, as suggested by the error, and will resolve itself soon... Or maybe it's a phased rollout of breaking changes that will hit other areas soon. I'm guessing it's region based as my containers are all fine. |
|
Can confirm too, also confirm, that i can login to icloud.com normally |
|
same issue still on, also here. Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
update: One container works fine the other one above has the problem. |
|
Yes, the containers where the reauth process is more than 2 days ago are working correctly. Only these ones which need to be reauthed don‘t start… |
|
when you login to icloud.com you get a message with the info, that the cloud experience should be better with the new version. I guess Apple made some changes. |
|
Is there a solution available? |
No. Apple seems to be disabling/limiting auth API used by icloudpd (and many other open source tools). The solution is to support new auth protocol. There are report that some tools might have done that already and |
|
Same issue here. |
|
same issue by me |
|
Deleted everything and tried to configure new Container. Same issue as well |
|
I'm still running OK... Still have 4 days until the cookies expire on my containers though. Assuming everything will die at that point. |
Pls try to create a new instance and try to authorize. Think it wont work. |
|
In another repo they are talking about the same, and think they have solved it! fastlane/fastlane#26368 |
|
Same issue here. |
|
same here |
|
Me too |
|
It's caused by Apple SRP-6a implementation |
|
could this be a part of the solution? |
|
For the sake of clarity, do you think a solution to this issue might be addressed in upcoming Home Assistant updates, or is the integration effectively deprecated? I also want to extend my sincere thanks to everyone actively working on a resolution. |
|
Same error here - started after re-authentication |
|
New container pushed with fix included. Seems that there may be a related issue that some people may experience. Please update this issue with results. |
|
Updated to the latest container, reinitialized auth, and it worked flawlessly here. 👍 |
|
it still does not work any more. Have tried with reauth.sh as well as sync-icloud.sh --initialise 2024-10-25 23:36:24 DEBUG Authenticating... The above exception was the direct cause of the following exception: Traceback (most recent call last): |
After this update works like a charm! Thanks a lot! |
|
Had to force update in unRAID, but now it's working great! Thank you!!! |
|
Works greats after update and reinitializing. Thank you! |
|
Working for me now. |
Updated, re-initialised and it works well. Thanks for the fix |
|
Just wondering if anyone know, is it possible to auto delete old photos from icloud which are may be 180 days old? Talking in regards to any settings change in icloudpd |
|
Unfortunately, I still have the same problem as dotnjet: Both reauth, initialise or a completely new container lead to this message. |
|
Pulled the latest version, confirming I am one of the folks still having an issue :S. EDIT : It seems I managed to fix this by running the Thanks for the hard work @boredazfcuk ! Much appreciated. Any other way to support you than crypto? |
|
Even after pulling the latest version I got this error: I can login into icloud as normal in any browser. |
Exactly the same response for me. |
|
I'm hitting this issue as well, I had 3 containers (two with personal account, for myself and shared library, one for my partner). My two personal accounts worked fine, my partner's does not. All configured similarly, updated and was working fine before this auth issue. I tried the normal initialize method, and reauth.sh, and also can login fine with same credentials in the browser. Any ideas how to get this container working again? |
icloud-photos-downloader/icloud_photos_downloader#975 Problem has been reported upstream. Points to a password issue. I'd try running |
Learn to code and submit pull requests :D |
Many thanks! I have tried it before and just tried it again without success. 2024-10-26 23:31:16 INFO Directory is writable: /config/python_keyring/ The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Same result for me. It seems it does not accept the correct password. |
yes exactly. One time I even had to unlock the password on iCloud.com. Other times it was fine to log into icloud during the tests |
|
Exactly the same problem here. :( Any ideas???Issue: In addition I get a message v980 is outdated, with every start of the container. That always leads to waiting time of 2min. BR, |
Just updated both of my containers on Unraid via the Docker app - new 2fa works and everything works as intended -- Thanks again @boredazfcuk and the community on getting this fixed. We all appreciate it |
Some people have reported this can be resolved by changing the password on the account. Would need to set the new one on appleid.apple.com, remove the keyring from the container, then re-initialise. |
I would agree, ashamed to say that my Apple ID password was very old. I have now updated the password on the account, and successfully re initialised the container. |
|
I can confirm, that changing the password on iCloud up front is doing the job! Running in MAIN Two-step authentication required. |
|
Glad to hear! Do we think it’s going to be possible to resolve the issue and keep the same password, or is this a necessary workaround? Since I’m backing up for another person, changing their password isn’t ideal. |
|
I´m sorry, but it doesn´t work for me :-(
2024-11-01 02:20:42 INFO ***** boredazfcuk/icloudpd container for icloud_photo_downloader v1.0.716 started ***** The above exception was the direct cause of the following exception: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
|
Changing the password worked for me on two accounts and three dockers. |
|
In my case w/o changing the password it works well now with setting up the container new with new yaml file. |
and others
Describe the bug
My iCloudpd container suddenly stopped being able to connect to iCloud. Log says no MFA cookie and when I try to re-authenticate, it shows a service temporary unavailable.
I tried deleting the keyring_pass.cfg and running the initialization script but iCloud did not accept my password even though I can use the same password to log into iCloud web. Advanced Data Protection is not turned on.
System (The following information must be entered or the issue will be closed):
Debug log file
2024-10-19 17:34:43 INFO Container initialisation complete
2024-10-19 17:34:43 INFO Script launch parameters: --Initialise
2024-10-19 17:34:43 DEBUG Group, users:100, already created
2024-10-19 17:34:43 DEBUG User, Moses:1026, already created
2024-10-19 17:34:43 DEBUG Set owner and group on icloudpd temp directory
2024-10-19 17:34:43 DEBUG Set owner and group on config directory
2024-10-19 17:34:43 INFO Directory is writable: /config/python_keyring/
2024-10-19 17:34:43 DEBUG Configure password
2024-10-19 17:34:43 DEBUG Using password stored in keyring file: /config/python_keyring/keyring_pass.cfg
2024-10-19 17:34:43 INFO Starting container initialisation
2024-10-19 17:34:43 DEBUG 2024-10-19 17:34:43 INFO Correct owner on config directory, if required
2024-10-19 17:34:43 DEBUG 2024-10-19 17:34:43 INFO Correct group on config directory, if required
2024-10-19 17:34:43 DEBUG Generate MFA cookie using password stored in keyring file
2024-10-19 17:34:43 DEBUG Authenticating...
2024-10-19 17:34:44 ERROR Service Temporarily Unavailable (503)
Traceback (most recent call last):
File "pyicloud_ipd/base.py", line 211, in authenticate
File "requests/sessions.py", line 637, in post
File "pyicloud_ipd/session.py", line 122, in request
File "pyicloud_ipd/session.py", line 196, in _raise_error
pyicloud_ipd.exceptions.PyiCloudAPIResponseException: Service Temporarily Unavailable (503)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "starters/icloudpd.py", line 6, in
File "click/core.py", line 1157, in call
File "click/core.py", line 1078, in main
File "click/core.py", line 1434, in invoke
File "click/core.py", line 783, in invoke
File "icloudpd/base.py", line 745, in main
File "icloudpd/base.py", line 1179, in core
File "icloudpd/authentication.py", line 53, in authenticate_
File "pyicloud_ipd/base.py", line 157, in init
File "pyicloud_ipd/base.py", line 219, in authenticate
pyicloud_ipd.exceptions.PyiCloudFailedLoginException: ('Invalid email/password combination.', PyiCloudAPIResponseException('Service Temporarily Unavailable (503)'))
[783] Failed to execute script 'icloudpd' due to unhandled exception!
2024-10-19 17:34:45 ERROR Multifactor authentication information missing from cookie. Authentication has failed
2024-10-19 17:34:45 ERROR - Was the correct password entered?
2024-10-19 17:34:45 ERROR - Was the multifactor authentication code mistyped?
2024-10-19 17:34:45 ERROR - Can you log into icloud.com without receiving pop-up notifications?
2024-10-19 17:34:45 INFO Container initialisation complete
Moses@DS923plus:
$ sudo docker exec -it icloudpd re-auth.sh$ sudo docker exec -it icloudpd reauth.shOCI runtime exec failed: exec failed: unable to start container process: exec: "re-auth.sh": executable file not found in $PATH: unknown
Moses@DS923plus:
2024-10-19 17:36:50 DEBUG Authenticating...
2024-10-19 17:36:51 ERROR Service Temporarily Unavailable (503)
Traceback (most recent call last):
File "pyicloud_ipd/base.py", line 211, in authenticate
File "requests/sessions.py", line 637, in post
File "pyicloud_ipd/session.py", line 122, in request
File "pyicloud_ipd/session.py", line 196, in _raise_error
pyicloud_ipd.exceptions.PyiCloudAPIResponseException: Service Temporarily Unavailable (503)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "starters/icloudpd.py", line 6, in
File "click/core.py", line 1157, in call
File "click/core.py", line 1078, in main
File "click/core.py", line 1434, in invoke
File "click/core.py", line 783, in invoke
File "icloudpd/base.py", line 745, in main
File "icloudpd/base.py", line 1179, in core
File "icloudpd/authentication.py", line 53, in authenticate_
File "pyicloud_ipd/base.py", line 157, in init
File "pyicloud_ipd/base.py", line 219, in authenticate
pyicloud_ipd.exceptions.PyiCloudFailedLoginException: ('Invalid email/password combination.', PyiCloudAPIResponseException('Service Temporarily Unavailable (503)'))
[854] Failed to execute script 'icloudpd' due to unhandled exception!
The text was updated successfully, but these errors were encountered: