Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No route to icloud.com.cn found #381

Closed
Alano-i opened this issue Aug 29, 2023 · 9 comments
Closed

No route to icloud.com.cn found #381

Alano-i opened this issue Aug 29, 2023 · 9 comments

Comments

@Alano-i
Copy link
Contributor

Alano-i commented Aug 29, 2023

After upgrading to the latest version latest, it fails to start and reports an error No route to icloud.com.cn found.

2023-08-29T04:44:41.777062658Z
2023-08-29 12:44:41 INFO     ***** boredazfcuk/icloudpd container for icloud_photo_downloader v1.0.627 started *****
2023-08-29 12:44:41 INFO     ***** For support, please go here: https://github.com/boredazfcuk/docker-icloudpd *****
2023-08-29 12:44:41 INFO     Alpine Linux 3.18.2
2023-08-29 12:44:41 INFO     Python version: 3.11.4
2023-08-29 12:44:41 INFO     Loading configuration from: /config/icloudpd.conf
2023-08-29 12:44:41 ERROR    No route to icloud.com.cn found. Please check your container's network settings - exiting
2023-08-29 12:44:41 ERROR    Error debug - traceroute: socket(AF_INET,3,1): Operation not permitted
@boredazfcuk
Copy link
Owner

Hi,

The traceroute check, which confirms that the container can connect to iCloud, was introduced 2021-09-21. It requires root privileges to run.

Your error is complaining that it does not have permission. So something must have changed when the container was re-created, as it seems the permissions it previously had, has now been removed.

Have you also upgraded your container software? Maybe that has changed the default from creating privileged containers to creating non-privileged ones.

@Alano-i
Copy link
Contributor Author

Alano-i commented Aug 29, 2023

image I checked the permissions when icloudpd.conf was automatically generated, and it was root. But the error was still reported. How should I solve this problem?

@boredazfcuk
Copy link
Owner

The permissions problem relates to the Docker configuration of the container, not within the container itself.

What container package are you running?

@Alano-i
Copy link
Contributor Author

Alano-i commented Oct 10, 2023

The system I am currently running is TrueNAS Scale, utilizing the latest version of the iCloudPD application through community-customized app deployment. Interestingly, all other Docker applications running in a similar manner and configuration do not encounter any networking issues, except for iCloudPD.

Allow me to present my configuration in the following manner:

albums_with_dates=false
apple_id=*****@qq.com
auth_china=true
authentication_type=MFA
auto_delete=true
bark_device_key=
bark_server=
convert_heic_to_jpeg=false
debug_logging=false
delete_accompanying=false
delete_after_download=false
delete_notifications=true
dingtalk_token=
directory_permissions=777
discord_id=
discord_token=
download_notifications=true
download_path=/Photo/iCloud/Alano
file_permissions=777
folder_structure={:%Y/%Y-%m/%Y-%m-%d}
gotify_app_token=
group=apps
group_id=568
icloud_china=true
iyuu_token=
jpeg_path=
jpeg_quality=90
libraries_with_dates=false
nextcloud_delete=false
nextcloud_password=
nextcloud_upload=false
nextcloud_url=
nextcloud_username=
notification_days=7
notification_type=WeCom
photo_album=
photo_library=
photo_size=original
prowl_api_key=
pushover_sound=
pushover_token=
pushover_user=
recent_only=500
set_exif_datetime=false
single_pass=false
skip_album=
skip_check=true
skip_download=false
skip_library=
skip_live_photos=false
skip_videos=false
synchronisation_delay=0
synchronisation_interval=43200
synology_ignore_path=false
telegram_chat_id=
telegram_polling=true
telegram_server=
telegram_silent_file_notifications=
telegram_token=
trigger_nextlcoudcli_synchronisation=
until_found=
user_id=1000
webhook_https=false
webhook_id=
webhook_path=/api/webhook/
webhook_port=8123
webhook_server=
wecom_id=ww*****708
wecom_proxy=
wecom_secret=0-*****lw

1
2

@boredazfcuk
Copy link
Owner

I installed TrueNAS-SCALE in a VM this morning, set up a container and it works fine:
image

@boredazfcuk
Copy link
Owner

boredazfcuk commented Oct 10, 2023

This is how i configured it:
image
image
image
image
image
image
image
image
image
image

@boredazfcuk
Copy link
Owner

boredazfcuk commented Oct 10, 2023

Actually, I've spotted the problem in your config:

image

The container uses traceroute to determine if there is a route to the Internet available and the traceroute command requires additional privileges. I would guess it would just need cap_add: - NET_ADMIN in docker compose, or --cap-add=NET_ADMIN using docker run. I'm guessing mine works because I have the above box ticked though.

@Alano-i
Copy link
Contributor Author

Alano-i commented Oct 10, 2023

Thanks!

@Alano-i Alano-i closed this as completed Oct 10, 2023
@billxsand
Copy link

O.M.F.G. I have been tearing my hair out for months trying to figure this out!! Thank you guys so much 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants