### Author:  [@AJRT](https://meta.discourse.org/u/AJRT)
#### Post date: [July 23, 2019, 3:27pm UTC](https://meta.discourse.org/t/not-implemented-error-after-upload-any-new-image-with-azure-blob-storage/123743/1 "2019-07-23T15:27:46Z")
Hello,
I am using **v2.4.0.beta2 +66** , with [discourse-azure-blob-storage](https://github.com/discourse/discourse-azure-blob-storage) plugin and since a few weeks I have had some problems with uploaded images (e.g. I cannot zoom in) and in logs, there is an error message.
Steps to reproduce:
1. Create a new topic/post where is upload any image.
2. Try to click on the image in topic/post.
- The image is uploaded and visible in post, but there is no possibility to zoom in/see in a gallery.
- I am expecting behaviour as is on a picture above, on the right site.
- In `/logs`, there is error message (with a lot of **Env** correlated with the same post id):
### Message (27326 copies reported)
`Job exception: Not implemented.`
### Backtrace
```plaintext
/var/www/discourse/lib/file_store/base_store.rb:148:in `not_implemented'
/var/www/discourse/lib/file_store/base_store.rb:42:in `download_url'
/var/www/discourse/lib/cooked_post_processor.rb:386:in `add_lightbox!'
/var/www/discourse/lib/cooked_post_processor.rb:350:in `convert_to_link!'
/var/www/discourse/lib/cooked_post_processor.rb:681:in `block in post_process_images'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/nokogiri-1.10.3/lib/nokogiri/xml/node_set.rb:238:in `block in each'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/nokogiri-1.10.3/lib/nokogiri/xml/node_set.rb:237:in `upto'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/nokogiri-1.10.3/lib/nokogiri/xml/node_set.rb:237:in `each'
/var/www/discourse/lib/cooked_post_processor.rb:678:in `post_process_images'
/var/www/discourse/lib/cooked_post_processor.rb:42:in `block in post_process'
/var/www/discourse/lib/distributed_mutex.rb:42:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:12:in `synchronize'
/var/www/discourse/lib/cooked_post_processor.rb:38:in `post_process'
/var/www/discourse/app/jobs/regular/process_post.rb:26:in `execute'
/var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rails_multisite-2.0.7/lib/rails_multisite/connection_management.rb:63:in `with_connection'
/var/www/discourse/app/jobs/base.rb:221:in `block in perform'
/var/www/discourse/app/jobs/base.rb:217:in `each'
/var/www/discourse/app/jobs/base.rb:217:in `perform'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:192:in `execute_job'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:165:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/middleware/chain.rb:128:in `block in invoke'
/var/www/discourse/lib/sidekiq/pausable.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/middleware/chain.rb:130:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/middleware/chain.rb:133:in `invoke'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:164:in `block in process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:137:in `block (6 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/job_retry.rb:109:in `local'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:136:in `block (5 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq.rb:37:in `block in '
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:132:in `block (4 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:250:in `stats'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:127:in `block (3 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/job_logger.rb:8:in `call'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:126:in `block (2 levels) in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/job_retry.rb:74:in `global'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:125:in `block in dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/logging.rb:48:in `with_context'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/logging.rb:42:in `with_job_hash_context'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:124:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:163:in `process'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:83:in `process_one'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/processor.rb:71:in `run'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/util.rb:16:in `watchdog'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/sidekiq-5.2.7/lib/sidekiq/util.rb:25:in `block in safe_thread'
```
### Env
1/50
| | | | | |
| --- | --- | --- | --- | --- |
| process\_id | 45213 | | | |
| application\_version | 1bb258ab497c25eb502a04112b746e98860968e5 | | | |
| current\_db | default | | | |
| job | Jobs::ProcessPost | | | |
| problem\_db | default | | | |
| | opts | null | | |
| | | post\_id | 181382 | |
| | | bypass\_bump | false | |
| | | new\_post | true | |
| | | current\_site\_id | default | |
| | | image\_sizes | [path\_to\_storage]/uploads/original/3X/0/a/0a6e7769958474f71197bef45f58168b3dbc696f.png | width 500 |
| | | | | height 230 |
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 23, 2019, 3:32pm UTC](https://meta.discourse.org/t/not-implemented-error-after-upload-any-new-image-with-azure-blob-storage/123743/2 "2019-07-23T15:32:31Z")
Yes it seems like this plugin hasn’t been updated for latest discourse versions.
---
### Author:  [@AJRT](https://meta.discourse.org/u/AJRT)
#### Post date: [July 24, 2019, 8:25am UTC](https://meta.discourse.org/t/not-implemented-error-after-upload-any-new-image-with-azure-blob-storage/123743/3 "2019-07-24T08:25:45Z")
Thank you for answer. @j.jaffeux do you think that it could be fixed in next release?
---
### Author:  [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 24, 2019, 8:30am UTC](https://meta.discourse.org/t/not-implemented-error-after-upload-any-new-image-with-azure-blob-storage/123743/4 "2019-07-24T08:30:04Z")
Been talking of it internally, no ETA yet sorry.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [December 7, 2019, 2:52am UTC](https://meta.discourse.org/t/not-implemented-error-after-upload-any-new-image-with-azure-blob-storage/123743/5 "2019-12-07T02:52:46Z")
I believe the Azure plugin is now deprecated until we can find a customer that needs this.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [August 4, 2021, 7:19am UTC](https://meta.discourse.org/t/not-implemented-error-after-upload-any-new-image-with-azure-blob-storage/123743/6 "2021-08-04T07:19:43Z")