# Aws geïmplementeerde discourse haalt assets op uit database url

**URL:** <https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191>\
**Category:** Product Support\
**Tags:** unsupported-install\
**Created:** [16 september 2020 om 11:41 UTC](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191 "2020-09-16T11:41:05Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Vijay\_Vantipalli](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vijay_vantipalli/32/192329_2.png) [@Vijay\_Vantipalli](https://meta.discourse.org/u/Vijay_Vantipalli)\
**Post date:** [16 september 2020 om 11:41 UTC](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191/1 "2020-09-16T11:41:05Z")

</div>

Hi Team

I am running disource on aws ecs. When I am trying to run the application, the console tab in browser is failing with the below urls. Did I miss any configuration change?

Mixed Content: The page at ‘[https://discuss-stage.tllms.com/finish-installation/register](https://discuss-stage.tllms.com/finish-installation/register)’ was loaded over HTTPS, but requested an insecure favicon ‘[http://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/uploads/default/optimized/1X/\_129430568242d1b7f853bb13ebea28b3f6af4e7\_2\_32x32.png](http://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/uploads/default/optimized/1X/_129430568242d1b7f853bb13ebea28b3f6af4e7_2_32x32.png)’. This request has been blocked; the content must be served over HTTPS.

In the above URL this is my database endpoint [discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com](http://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com).

I have given the above end point in database.yml file.

I deployed discourse in ECS using docker. When I try to access the application the network browser is fetching resources from below URLs instead of [https://discuss-stage.tllms.com/](https://discuss-stage.tllms.com/)

This is our [discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com](http://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/) RDS endpoint which is used in database.yml file.

Mixed Content: The page at ‘[https://discuss-stage.tllms.com/’](https://discuss-stage.tllms.com/%E2%80%99) was loaded over HTTPS, but requested an insecure favicon ‘[http://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/uploads/default/optimized/1X/\_129430568242d1b7f853bb13ebea28b3f6af4e7\_2\_32x32.png’](http://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/uploads/default/optimized/1X/_129430568242d1b7f853bb13ebea28b3f6af4e7_2_32x32.png%E2%80%99). This request has been blocked; the content must be served over HTTPS.

Refused to load the script ‘[https://discuss-stage.tllms.com/assets/browser-detect.js’](https://discuss-stage.tllms.com/assets/browser-detect.js%E2%80%99) because it violates the following Content Security Policy directive: “script-src [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/logs/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/logs/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/sidekiq/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/sidekiq/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/mini-profiler-resources/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/mini-profiler-resources/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/assets/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/assets/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/brotli\_asset/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/brotli_asset/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/extra-locales/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/extra-locales/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/highlight-js/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/highlight-js/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/javascripts/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/javascripts/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/plugins/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/plugins/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/theme-javascripts/](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/theme-javascripts/) [https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/svg-sprite/”](https://discourse-test.c0fbtc1q6bvm.ap-south-1.rds.amazonaws.com/svg-sprite/%E2%80%9D). Note that ‘script-src-elem’ was not explicitly set, so ‘script-src’ is used as a fallback.

---

_[View the full topic](https://meta.discourse.org/t/aws-deployed-discourse-is-fetching-assets-from-database-url/164191)._
