Can't upload files > 20MB on Self Host about telegram-bot-api HOT 11 CLOSED

Using both HTTP and HTTPS

This wouldn't work, because in local mode you can "Upload files up to 2000 MB". Sending a file using its HTTP URL is not a file uploading. Such files are downloaded by the Telegram servers from the specified URL and there is no way --local flag can change limits on their size.

URI Scheme: file://path/to/file.jpg with both absolute and relative path, hitting {"ok":false,"error_code":400,"description":"Bad Request: realpath failed for <path to file>"}

The provided path is wrong as the error message suggest. The error message includes the wrong path, so you should clearly see the error. You can find examples of valid file URI in https://en.wikipedia.org/wiki/File_URI_scheme#Examples.

from telegram-bot-api.

Solved. I added "/" to the real file path, making it file:///<absolute path to file.jpg>, in my case file:///var/www/....

from telegram-bot-api.

I stand corrected. A new error arises: {"ok":false,"error_code":400,"description":"Bad Request: stat for file \"<path to file>" failed"}

from telegram-bot-api.

The file is still not accessible. Check access rights of the file.

from telegram-bot-api.

Does it work with files smaller than 20MB?

from telegram-bot-api.

@mrbesen The error isn't related in any way to size of the file. The file doesn't exist or there are no enough rights to access it.

from telegram-bot-api.

@Nickelza Was your problem solved?

from telegram-bot-api.

The file is still not accessible. Check access rights of the file.

I'm afraid you're right, still trying to figure it out

from telegram-bot-api.

Does it work with files smaller than 20MB?

No

from telegram-bot-api.

@Nickelza Was your problem solved?

Not yet, but I think I've more or less understood what to fix, just not how to fix it. The user that is used to access the script (www-data) isn't able to view upper level folders, so a realpath is more or less meaningless to it (I confirmed this by verifying the PHP realpath function returns false). So now I just have to figure out how to give www-data executable permission for upper folders without changing their ownership or making them 777

from telegram-bot-api.

All solved. As @levlam initially stated, it was a problem with permissions. The permission of the last folder inside of which the file to send was had executable permission set only for the owner, I set it for all (711). This definitely fixed the issue. Thanks for the help @levlam and @mrbesen for chipping in too.

from telegram-bot-api.