# Impossible de se connecter à Discourse soudainement

**URL:** <https://meta.discourse.org/t/unable-to-login-into-discourse-suddenly/115708>\
**Category:** Product Support\
**Created:** [Avril 23, 2019, 11:45 UTC](https://meta.discourse.org/t/unable-to-login-into-discourse-suddenly/115708 "2019-04-23T11:45:39Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [Avril 23, 2019, 1:59 UTC](https://meta.discourse.org/t/unable-to-login-into-discourse-suddenly/115708/9 "2019-04-23T13:59:58Z")

</div>

> [@Tarek\_Khalil](#):
>
> The migration started, reached a particular step, executed that step but then some fault caused a hault. At this point, the migration `version number` wouldn’t be written to the DB but the migration step would be executed.

That would explain it! So I guess the best solution is to manually drop the `ignored_users` table (after taking a backup). Then the migration should be able to run successfully.

@Shashikant_Sharma are you using a standard installation from our [install guide](https://github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md)? If so, please try running

```plaintext
cd /var/discourse
./launcher enter app
su -c 'psql discourse' postgres

```

Then run

```plaintext
SELECT version, name, created_at from schema_migration_details ORDER BY created_at DESC LIMIT 10;

```

---

_[View the full topic](https://meta.discourse.org/t/unable-to-login-into-discourse-suddenly/115708)._