error.api.fetch.empty #967

Open
opened 2025-11-09 10:02:54 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @olllayor on GitHub (Nov 4, 2025).

problem description

bug description
I have tried multiple publicly accessible image URLs from instagram and have had the same outcome.

The image get downloaded when tested on the main instance but give the following error on my self hosted instance:

curl -i -s -X POST https://cobalt.ollayor.uz/ -H "Accept: application/json" -H "Content-Type: application/json" -d '{"url":"https://www.instagram.com/reel/DQcSE8SjdkV/?igsh=MW44eWp4OTBuMHo4dA=="}'

Response
{
"status": "error",
"error": {
"code": "error.api.fetch.empty"
}
}

btw, I added a proxy service because you said to use a proxy. The result did not change.

your instance configuration

no changes at all
Originally created by @olllayor on GitHub (Nov 4, 2025). ### problem description bug description I have tried multiple publicly accessible image URLs from instagram and have had the same outcome. The image get downloaded when tested on the main instance but give the following error on my self hosted instance: curl -i -s -X POST https://cobalt.ollayor.uz/ -H "Accept: application/json" -H "Content-Type: application/json" -d '{"url":"https://www.instagram.com/reel/DQcSE8SjdkV/?igsh=MW44eWp4OTBuMHo4dA=="}' Response { "status": "error", "error": { "code": "error.api.fetch.empty" } } btw, I added a proxy service because you said to use a proxy. The result did not change. ### your instance configuration ```shell no changes at all ```
GiteaMirror added the instance hosting help label 2025-11-09 10:02:54 -06:00
Author
Owner

@OrientPlus commented on GitHub (Nov 7, 2025):

Yes, I've also encountered this problem. My local instance is running on a server in the Netherlands, because I live in Russia and YouTube is not directly accessible to me. A similar error pops up periodically, I don't understand what it might be related to.

@OrientPlus commented on GitHub (Nov 7, 2025): Yes, I've also encountered this problem. My local instance is running on a server in the Netherlands, because I live in Russia and YouTube is not directly accessible to me. A similar error pops up periodically, I don't understand what it might be related to.
Sign in to join this conversation.