# Discourse lost the ability to login for all accounts

**URL:** <https://meta.discourse.org/t/discourse-lost-the-ability-to-login-for-all-accounts/51775>\
**Category:** Product Support\
**Created:** [Outubro 20, 2016, 10:35am UTC](https://meta.discourse.org/t/discourse-lost-the-ability-to-login-for-all-accounts/51775 "2016-10-20T10:35:27Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [Outubro 20, 2016, 2:49pm UTC](https://meta.discourse.org/t/discourse-lost-the-ability-to-login-for-all-accounts/51775/10 "2016-10-20T14:49:33Z")

</div>

Just to add to @fefrei’s explanation, rebuild is unnecessary for this round because you weren’t changing the app.yml, you were invoking Discourse’s internal API which updated the database and thus the next time you attempted to access your Discourse instance, it was able to read force\_https as false.

Every bit of the Discourse application runs off of its own internal UI, so every action you can perform in your browser, there are commands you can run to reproduce those exact actions. In times where you lock yourself out, it is really helpful.

---

_[View the full topic](https://meta.discourse.org/t/discourse-lost-the-ability-to-login-for-all-accounts/51775)._
