# Upload assets to S3 after in-browser upgrade

**URL:** https://meta.discourse.org/t/upload-assets-to-s3-after-in-browser-upgrade/153519
**Category:** Support
**Created:** [2 juni 2020 om 04:11 UTC](https://meta.discourse.org/t/upload-assets-to-s3-after-in-browser-upgrade/153519 "2020-06-02T04:11:03Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![taher1](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/taher1/32/182563_2.png) [@taher1](https://meta.discourse.org/u/taher1)
#### Post date: [2 juni 2020 om 05:23 UTC](https://meta.discourse.org/t/upload-assets-to-s3-after-in-browser-upgrade/153519/7 "2020-06-02T05:23:49Z")

</div>

It started happening after I configured s3 settings following this [Configure an S3 compatible object storage provider for uploads](https://meta.discourse.org/t/using-object-storage-for-uploads-s3-clones/148916?page=2#backblaze-b-cloud-storage)

> [@itsbhanusharma](#):
>
> JS is regenerated upon rebuild

That’s why they added the `after_assets_precompile ` hook to upload the updated assets on s3.

How do I fix this. It 404s if I try to access any asset through local server. It have to be through s3. Or I would’ve put an edge routing rule on my cdn pulling asset requests through local domain.

---

_[View the full topic](https://meta.discourse.org/t/upload-assets-to-s3-after-in-browser-upgrade/153519)._