# Jobs::DownloadAvatarFromUrl time-out

**URL:** <https://meta.discourse.org/t/jobs-downloadavatarfromurl-times-out/191905>\
**Category:** Product Support\
**Created:** [28 mei 2021 om 09:47 UTC](https://meta.discourse.org/t/jobs-downloadavatarfromurl-times-out/191905 "2021-05-28T09:47:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![bytegoose](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@bytegoose](https://meta.discourse.org/u/bytegoose)\
**Post date:** [5 juni 2021 om 01:41 UTC](https://meta.discourse.org/t/jobs-downloadavatarfromurl-times-out/191905/2 "2021-06-05T01:41:10Z")

</div>

Sorry for the late update.

I just got around testing with 1024MB and 2048MB of memory allocated but the result is still the same. Any more suggestions would be highly appreciated!

**Edit:** So after going through the logs again and again, I checked the code for the job and saw that this is not intented to be retried. Naturally, this is exactly what I did. I edited the file and found in Sidekiq that my issue is actually related to network related things.  
The retry job gives me

> Jobs::HandledExceptionWrapper: Wrapped Net::OpenTimeout: execution expired

as an error I can actually work with.

The takeaway for anyone in the future is: If `URI.open(your url).read` in the rails console does not work, it’s likely a ruby-network issue instead of an Discourse issue. I had the idea from [stackoverflow](https://stackoverflow.com/questions/42036133/ruby-netopentimeout-execution-expired/42043142)

---

_[View the full topic](https://meta.discourse.org/t/jobs-downloadavatarfromurl-times-out/191905)._
