[BUG] Telegram Node Fails to Retrieve File with Local API Server

Based on the documentation and implementation details, the Telegram node does use the custom base URL defined in your Telegram credentials for all API requests. The Get File operation constructs its URL based on the baseUrl property that you provide. In other words, there isn’t a separate implementation for Get File that overrides your custom URL.

Here are a few suggestions to troubleshoot and resolve the issue:

• Double-check your base URL:
  Make sure the URL you provided in your credentials for your local API server is correctly formatted (for example, having no trailing slashes) and fully supports all of the endpoints used by Telegram’s Bot API.

• Local API server compatibility:
  The Telegram Bot API’s file system relies on a two-step process:

  1. Call getFile to retrieve a file path.
  2. Use the combined URL (baseUrl + file_path) to download the file.
     Verify that your local API server implements the same file-handling endpoints as the official Telegram API. It might be that your local server doesn’t support file downloads via the same mechanism, which would result in a “file couldn’t be found” error.

• Credential configuration:
  Ensure that both the Access Token and the baseUrl in your credentials are correctly set up (as detailed in the documentation for Telegram credentials). An incorrect URL or token might cause the API call to fail in unexpected ways.

If everything in your configuration seems correct and your local server is designed to fully mimic Telegram’s API, then you may want to check whether the local implementation actually returns the correct file path. If it does, then verify that the file retrieval endpoint is functioning as expected.

In summary, the node is not ignoring your custom baseUrl—if you’re experiencing issues with file retrieval using a local API server, it’s most likely due to either a misconfiguration or differences in how the local server implements Telegram’s file endpoints.