My weekend was calm, and my next issue is with my blog’s Telegram integration
I wanted to share my next problem with my Telegram integration on my blog. But first, I want to say a few words about today, because it was sunny and surprisingly warm, around +9 degrees. The past few days were also sunny and comfortable, but I didn’t describe them. So I couldn’t stay at home, and I didn’t try to resolve my Telegram API issues, because it felt too boring to spend time on that during such a nice day. Instead, I went for a walk and spent about an hour outside in the sun. Also, it was different from previous days because our neighborhood was crowded with adults and their kids.
Now I want to share a few moments from my Telegram API experience that happened two days ago on my blog. The main problem in this situation was Telegram blocking, which appeared unexpectedly but didn’t completely stop my blog from working. I noticed this issue when I tried to share my post to my Telegram channel and got a “504 Gateway Timeout” error. At first, I thought it was just a temporary network issue or a server-side problem. Honestly, it was something new for me—I had never encountered this kind of behavior before, and I didn’t even think that the API could be blocked.
So I started to investigate possible reasons and tried to understand what exactly was going wrong. In my opinion, I only had a few options in this situation: rent a new server abroad or use a VPN on my current production server. I think using a server abroad is the best solution, but it’s a bit expensive. I don’t want to use a VPN because it can be unstable, and governments can block it too.
My weekend was calm, and my issue is with my blog’s Telegram integration
In this post I wanted to share about my next problem with my Telegram integration on my blog. But first I need to say some words about this day, because it was sunny and extremely warm, around +9 degrees. Of course my last days were also sunny and comfortable, but I didn't describe them. So I couldn't stay at home, and I didn't try to resolve my Telegram API issues. Because it's boring and not interesting enough to spend time at home on such a sunny day. Instead, I went for a walk and spent around an hour under the sun. Also, it wasn't like my previous days that I spent previously because our neighborhood was crowded with adults and their kids.
Now I need to share a few moments from my Telegram API experience that happened two days ago on my blog. In this situation the main problem is about the Telegram blocking, which appeared unexpectedly but didn't paralyze my blog working. I noticed this issue when I wanted to share my post to my Telegram channel. I got the message "504 Gateway Timeout" and at first I thought it might be just a temporary network issue or a server-side problem. Honestly, it was something new for me; I had never encountered behavior like this, and I also couldn't think that the API would be blocked.
So I started to investigate possible reasons and tried to understand what exactly was going wrong. In my opinion, in this situation I had only a few options, rent a new VDS server from abroad or just use a VPN for my current production server. I think using a broad server can be the best solution but a bit expensive. I don't want to use a VPN because it can be unstable, governments can block it too.