# Sidekiq stops after some time **URL:** \ **Category:** Self-hosting\ **Created:** [June 9, 2023, 9:54am UTC](https://meta.discourse.org/t/sidekiq-stops-after-some-time/267777 "2023-06-09T09:54:22Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![trobiyo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trobiyo/32/311872_2.png) [@trobiyo](https://meta.discourse.org/u/trobiyo)\ **Post date:** [June 14, 2023, 1:29pm UTC](https://meta.discourse.org/t/sidekiq-stops-after-some-time/267777/8 "2023-06-14T13:29:53Z")
Hi Denis, This looks to me an issue with sockets/DNS that give timeout? Do you have anything set under the `allowed internal hosts` setting? Looking at the stacktrace, when doing a lookup of the ips it seems this list is empty (see [discourse/lib/final\_destination/ssrf\_detector.rb at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/lib/final_destination/ssrf_detector.rb#L104)), triggered at [discourse/lib/final\_destination/http.rb at tests-passed · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/tests-passed/lib/final_destination/http.rb#L13), hence I’m tempted to say that this could be associated to your installation (that cannot reach the ip of the sidekiq pods?) Or check whether you are using any NetworkPolicy installed in your cluster, this can be another reason. Cheers --- _[View the full topic](https://meta.discourse.org/t/sidekiq-stops-after-some-time/267777)._