# 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:** 2

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [February 3, 2019, 10:23pm UTC](https://meta.discourse.org/t/http-logo-urls-after-enabling-letsencrypt/108261/2 "2019-02-03T22:23:37Z")

</div>

Was this server built using the [standard install guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md), or some other third-party package?

Is :80 specified in your app.yml at the end of the domain name? Check `DISCOURSE_HOSTNAME` - it shouldn’t include the port, but likely does based on what you’re reporting above. Remove the :80 from that line if so and rebuild. The only place :80 should appear in the YML file is the `expose:` section.

`Force_HTTPS` is required when Let’s Encrypt is enabled, the mixed content error is the result of an install without it enabled.

---

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