search

boredazfcuk / docker-icloudpd

An Alpine Linux container for the iCloud Photos Downloader command line utility
1.69k stars 161 forks source link

Bark startup notification failed with status code: 400 #382

Closed HuLuXi closed 8 months ago

HuLuXi commented 1 year ago

like the title, then it dont go next (nothing happan like the log) and i have update the image, the older could run well, and the newest couldnot with the same setting.

HuLuXi commented 1 year ago

2023-08-29 23:34:25 INFO Apple ID: 11 2023-08-29 23:34:25 INFO Authentication Type: MFA 2023-08-29 23:34:25 INFO Cookie path: /config/1** 2023-08-29 23:34:25 INFO Cookie expiry notification period: 7 2023-08-29 23:34:25 INFO Download destination directory: /photos 2023-08-29 23:34:25 INFO Folder structure: {:%Y/%m} 2023-08-29 23:34:25 INFO Synchronisation interval: 86400 2023-08-29 23:34:25 INFO Synchronisation delay (minutes): 0 2023-08-29 23:34:25 INFO Set EXIF date/time: true 2023-08-29 23:34:25 INFO Auto delete: false 2023-08-29 23:34:25 INFO Delete after download: false 2023-08-29 23:34:25 INFO Photo size: original 2023-08-29 23:34:25 INFO Single pass mode: false 2023-08-29 23:34:25 INFO Skip download check: true 2023-08-29 23:34:25 INFO Skip live photos: false 2023-08-29 23:34:25 INFO Number of most recently added photos to download: Download All Photos 2023-08-29 23:34:25 INFO Downloading photos from album: Download All Photos 2023-08-29 23:34:25 INFO Stop downloading when prexisiting files count is: Download All Photos 2023-08-29 23:34:25 INFO Live photo size: original 2023-08-29 23:34:25 INFO Skip videos: false 2023-08-29 23:34:25 INFO Convert HEIC to JPEG: true 2023-08-29 23:34:25 INFO Bark notifications enabled 2023-08-29 23:34:25 INFO Bark device key: V* 2023-08-29 23:34:25 INFO Bark server: ap* 2023-08-29 23:34:25 INFO Sending Bark startup notification 2023-08-29 23:34:26 ERROR Bark startup notification failed with status code: 400 2023-08-29 23:34:26 ERROR Please report problems here: https://github.com/boredazfcuk/docker-icloudpd/issues 2023-08-29 23:36:12 INFO boredazfcuk/icloudpd container for icloud_photo_downloader v1.0.627 started 2023-08-29 23:36:12 INFO For support, please go here: https://github.com/boredazfcuk/docker-icloudpd *****

boredazfcuk commented 11 months ago

The code used in Bark notifications was submitted via a PR. I have no way of debugging/testing it myself, so unless someone else can step up and diagnose the fault/submit a PR to fix it, then I'll just close it off in a month as unplanned.

Arnold4869 commented 11 months ago

我用中文说了，你试试把bark地址改为192.168开头的地址，别用域名，我现在就这么使用的

HuLuXi commented 11 months ago

我用中文说了，你试试把bark地址改为192.168开头的地址，别用域名，我现在就这么使用的

我试了 不顶用

ershouqingge commented 10 months ago

发一下你的配置

HuLuXi commented 8 months ago

The code used in Bark notifications was submitted via a PR. I have no way of debugging/testing it myself, so unless someone else can step up and diagnose the fault/submit a PR to fix it, then I'll just close it off in a month as unplanned.

i found that the service of bark should contain the port, and http:// or https:// can not there so only 192.6.X.X:XXX or XX.X.com:80 will goes well if not the photo download will never starts, and it will post 400(for the prefixes : http or https) or 000(for port) error code

boredazfcuk commented 8 months ago

i found that the service of bark should contain the port, and http:// or https:// can not there so only 192.6.X.X:XXX or XX.X.com:80 will goes well if not the photo download will never starts, and it will post 400(for the prefixes : http or https) or 000(for port) error code

Thanks for this. I've updated the configuration guide to explain the errors that will be reported if the server is not configured in this specific way.

HuLuXi commented 8 months ago

i found that the service of bark should contain the port, and http:// or https:// can not there so only 192.6.X.X:XXX or XX.X.com:80 will goes well if not the photo download will never starts, and it will post 400(for the prefixes : http or https) or 000(for port) error code

Thanks for this. I've updated the configuration guide to explain the errors that will be reported if the server is not configured in this specific way.

e.g. https://server.domain.com:443: or http://127.16.0.1:80. Failure to include the http/https prefix with result in error code 400 and failure to include the port will result in a 000 error.

no, the correct is "server. domain. com:443" or "127.16.0.1:80" the "http" or "https" must not be included