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.

Sign up for GitHub

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

Jump to bottom

HTTP 301 error when initializing Telegram bot #735

Closed
griffin-larson opened this issue Jan 23, 2025 · 4 comments
Closed

HTTP 301 error when initializing Telegram bot #735

griffin-larson opened this issue Jan 23, 2025 · 4 comments
Assignees
@boredazfcuk

Comments

@griffin-larson
Copy link

System:

  • OS: Unraid
  • Version 7.0.0

Describe the bug
I am attempting to set up the Telegram bot feature but running into an HTTP 301 error. I was able to work around this by creating a group chat in Telegram with myself and my bot and using that as the chat ID (including ~ in front) but was unable to get the chat commands to work. So, I decided to delete the bot and create a new one, which I saw had worked for another user, but am running into this same 301 error again. I sent a message to the Telegram bot and restarted the container as is mentioned in the debug file, but this did not change the output. Is the group chat what is causing the issue with chat commands or is that another issue entirely? If the chat commands not working is another issue entirely, using a group chat works just fine for me. But, I'd like to be able to sync on command and reauthenticate from my phone.

Expected behaviour
Telegram bot initializing with two-way chat.

Actual behaviour
HTTP 301 error when attempting to initialize bot. Using a group chat as the chat ID works for one-way notifications but chat commands do not work. Debug log shows it is polling Telegram.

Debug log file

2025-01-22 23:08:23 INFO     Initialising container...
2025-01-22 23:08:24 INFO      - Checking configuration file permissions
2025-01-22 23:08:24 INFO      - Create/update configuration file: /config/icloudpd.conf
2025-01-22 23:08:25 INFO      - Checking /config/icloudpd.conf for errors
2025-01-22 23:08:25 INFO      - Checking user:group account: user:group
2025-01-22 23:08:25 INFO      - Set owner and group on config directory: /config
2025-01-22 23:08:25 INFO      - Set owner and group on icloudpd temp directory: /tmp/icloudpd
2025-01-22 23:08:25 INFO      - Setting owner, group and permissions on: /home/user/iCloud
2025-01-22 23:08:25 DEBUG       | Set owner
2025-01-22 23:08:26 DEBUG       | Set group
2025-01-22 23:08:27 DEBUG       | Set 777 permissions on directories
2025-01-22 23:08:28 DEBUG       | Set 666 permissions on files
2025-01-22 23:08:29 INFO      - Checking directories are writable by user: user
2025-01-22 23:08:29 INFO      - Checking icloud.com is accessible
2025-01-22 23:08:31 INFO      - Checking Telegram bot initialised
2025-01-22 23:08:40 INFO        | Bot does not appear to have been initialised or needs reinitialising. Please send a message to the bot from your iDevice and restart the container
2025-01-22 23:08:40 INFO      - Checking for updates: Current version is up to date
2025-01-22 23:08:40 INFO     Initialisation complete
2025-01-22 23:08:40 INFO     ***** boredazfcuk/icloudpd container v1.0.1173_20-01-2025 started *****
2025-01-22 23:08:40 INFO     ***** For support, please go here: https://github.com/boredazfcuk/docker-icloudpd *****
2025-01-22 23:08:40 INFO     Alpine Linux 3.21.2
2025-01-22 23:08:40 INFO     Python version: 3.12.8
2025-01-22 23:08:40 INFO     icloud-photos-downloader version: 1.26.0
2025-01-22 23:08:40 INFO     Loading configuration from: /config/icloudpd.conf
2025-01-22 23:08:40 DEBUG    Running user id: 0
2025-01-22 23:08:40 DEBUG    Running group id: 0
2025-01-22 23:08:40 DEBUG    Local user: us********:99
2025-01-22 23:08:40 DEBUG    Local group: gr********:100
2025-01-22 23:08:40 DEBUG    Force GID: false
2025-01-22 23:08:40 DEBUG    LAN IP Address: 172.17.0.6
2025-01-22 23:08:40 DEBUG    Default gateway: 172.17.0.1
2025-01-22 23:08:40 DEBUG    DNS server: 1.1.1.1
1.0.0.1
2025-01-22 23:08:40 DEBUG    IP address for icloud.com: 17.253.144.10
2025-01-22 23:08:40 INFO     Debug logging: Enabled
2025-01-22 23:08:40 INFO     Apple ID: ************
2025-01-22 23:08:40 INFO     Cookie path: /config/************
2025-01-22 23:08:40 INFO     Cookie expiry notification period: 7
2025-01-22 23:08:40 INFO     Download destination directory: /home/user/iCloud
2025-01-22 23:08:40 INFO     Folder structure: {:%Y/%m/%d}
2025-01-22 23:08:40 DEBUG    Directory permissions: 777
2025-01-22 23:08:40 DEBUG    File permissions: 666
2025-01-22 23:08:40 INFO     Keep Unicode: false
2025-01-22 23:08:40 INFO     Live Photo MOV Filename Policy: suffix
2025-01-22 23:08:40 INFO     File Match Policy: name-size-dedup-with-suffix
2025-01-22 23:08:40 INFO     Synchronisation interval: 86400
2025-01-22 23:08:40 INFO     Synchronisation delay (minutes): 0
2025-01-22 23:08:40 INFO     Set EXIF date/time: false
2025-01-22 23:08:40 INFO     Auto delete: false
2025-01-22 23:08:40 INFO     Delete after download: false
2025-01-22 23:08:40 INFO     Delete empty directories: false
2025-01-22 23:08:40 INFO     Photo size: original
2025-01-22 23:08:40 INFO     Align RAW: as-is
2025-01-22 23:08:40 INFO     Single pass mode: false
2025-01-22 23:08:40 INFO     Skip download check: false
2025-01-22 23:08:40 INFO     Skip live photos: false
2025-01-22 23:08:40 INFO     Number of most recently added photos to download: Download All Photos
2025-01-22 23:08:40 INFO     Downloading photos from: Download All Photos
2025-01-22 23:08:40 INFO     Stop downloading when prexisiting files count is: Download All Photos
2025-01-22 23:08:40 INFO     Live photo size: original
2025-01-22 23:08:40 INFO     Skip videos: false
2025-01-22 23:08:40 INFO     Convert HEIC to JPEG: false
2025-01-22 23:08:40 INFO     Telegram notifications enabled
2025-01-22 23:08:40 DEBUG    Cleaned notification title: iCloudPD
2025-01-22 23:08:40 DEBUG    Telegram token: ********
2025-01-22 23:08:40 DEBUG    Telegram chat id: ********
2025-01-22 23:08:40 DEBUG    Telegram polling: true
2025-01-22 23:08:40 DEBUG    Telegram uses HTTP: true
2025-01-22 23:08:40 DEBUG    Telegram base URL: http://api.telegram.org/********
2025-01-22 23:08:40 DEBUG    Telegram notification URL: http://api.telegram.org/********/sendMessage
2025-01-22 23:08:40 DEBUG    Telegram silent file notifications: false
2025-01-22 23:08:40 DEBUG    Startup notification: Enabled
2025-01-22 23:08:40 INFO     Sending Telegram startup notification
2025-01-22 23:08:41 ERROR    Telegram startup notification failed with http status code: 301 and curl exit code: 0
2025-01-22 23:08:41 ERROR    ***** Please post the above debug log, along with a description of your problem, here: https://github.com/boredazfcuk/docker-icloudpd/issues *****
@boredazfcuk
Copy link
Owner

http error 301 means "moved" i.e your URL is wrong. I can see yours starts with http, so guess it requires https, which is usually the default.

@griffin-larson
Copy link
Author

Thank you, I think I changed the HTTP setting in troubleshooting but didn't change it back. The 301 error as well as the Telegram initialization notice went away, but now I'm getting an HTTP 403 on the same Telegram startup line. Am I configuring the bot incorrectly?

@boredazfcuk
Copy link
Owner

403 means "Forbidden" so likely your Chat ID or Token is incorrect.

Either you'll be using the correct token, but to connect to the wrong chat... or have the right chat, but wrong token.

@griffin-larson
Copy link
Author

This was it! I guess I was misunderstanding the Chat ID and had it misconfigured. Thank you!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@boredazfcuk boredazfcuk

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@boredazfcuk @griffin-larson