# Http logo urls after enabling LetsEncrypt

**URL:** <https://meta.discourse.org/t/http-logo-urls-after-enabling-letsencrypt/108261>\
**Category:** Self-hosting\
**Created:** [February 3, 2019, 8:12pm UTC](https://meta.discourse.org/t/http-logo-urls-after-enabling-letsencrypt/108261 "2019-02-03T20:12:54Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![dovydasm](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dovydasm/32/141073_2.png) [@dovydasm](https://meta.discourse.org/u/dovydasm)\
**Post date:** [February 3, 2019, 8:12pm UTC](https://meta.discourse.org/t/http-logo-urls-after-enabling-letsencrypt/108261/1 "2019-02-03T20:12:54Z")

</div>

I recently enabled letsencrypt for my instance by following [this tutorial.](https://meta.discourse.org/t/setting-up-https-support-with-lets-encrypt/40709)

Now all the images uploaded via settings panel (logo, small logo, favicon) have **http** links in the design, resulting in mixed content error (although user avatars and uploads have correct https links). Reuploading them doesn’t change anything.

`http://community.mysite.com/uploads/default/original/2X/8/818b69671732c4416713308be3b79cf837ea56c9.png`

When I enable “force HTTPS” setting, the links end up looking like this (note how it’s forcing port 80):

`https://community.mysite.com:80/uploads/default/original/2X/8/818b69671732c4416713308be3b79cf837ea56c9.png`

I’m using v2.2.0.beta10 +21.

`./launcher rebuild app` didn’t help.

How do I fix this?

---

_[View the full topic](https://meta.discourse.org/t/http-logo-urls-after-enabling-letsencrypt/108261)._