Closed abracadabra1111 closed 2 years ago
Have you tried restarting the container? It is a connection issue between your container and the Telegram API.
Have you tried restarting the container? It is a connection issue between your container and the Telegram API.
I did, but same error. It's currently tunneled through a VPN, so I'll try running it as a standalone.
Have you tried restarting the container? It is a connection issue between your container and the Telegram API.
I did, but same error. It's currently tunneled through a VPN, so I'll try running it as a standalone.
Makes no difference whether I'm running it through VPN container or as a bridge network in docker. Same error persists. I have about 30 other docker containers and no other connectivity problems elsewhere. Not sure if there's some other problem related to api.telegram.org.
Have you tried running it in host
network mode? Or running from source to rule out docker? It's working fine for many people, so I don't think there's a searcharr problem here.
Have you tried running it in
host
network mode? Or running from source to rule out docker? It's working fine for many people, so I don't think there's a searcharr problem here.
Looks like some network issue I need to sort out. Container working fine in a separate User bridge network.
Good luck!
I've been running searcharr for around 10 months or so and it's been great. Recently realized that the telegram bot stopped responding to inquiries. Searcharr container log shows the following recurring error. Any ideas what's causing the problem?