# Can’t log in to panel after upgrade due to unencrypted passwords

**URL:** <https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240>\
**Category:** Questions\
**Tags:** v3\
**Created:** [May 15, 2020, 11:05am UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240 "2020-05-15T11:05:52Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![romano](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@romano](https://forum.getkirby.com/u/romano)\
**Post date:** [May 15, 2020, 11:05am UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/1 "2020-05-15T11:05:52Z")

</div>

Hi everybody! After upgrading Kirby from 2.x to 3.2.5, and moving all user accounts to the new installation, we face a strange situation: Users that existed before the upgrade can still log in. But newly created users - or users who now change their passwords - cannot. Checking their .htpasswd file shows the (probable) reason: The new passwords are not encrypted, whereas passwords of the older users are hashed. And if a user with formerly hashed password changes his password, Kirby now stores it as clear text. My question is: Why? How can I make .htpasswd files hashed again?

---

<div class="post-metadata">

**Author:** ![pixelijn](https://avatars.discourse-cdn.com/v4/letter/p/7ab992/32.png) [@pixelijn](https://forum.getkirby.com/u/pixelijn)\
**Post date:** [May 15, 2020, 11:11am UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/2 "2020-05-15T11:11:42Z")

</div>

You are using an outdated Kirby version, probably in conjunction with PHP 7.4. Please update to 3.3.6.

---

<div class="post-metadata">

**Author:** ![anon77445132](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@anon77445132](https://forum.getkirby.com/u/anon77445132)\
**Post date:** [May 15, 2020, 11:16am UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/3 "2020-05-15T11:16:02Z")

</div>

@romano:  
Did you follow the whole [Kirby-Docs: How to migrate users](https://getkirby.com/docs/cookbook/setup/migrate-users) with PHP version 7.2 or 7.3?

---

<div class="post-metadata">

**Author:** ![romano](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@romano](https://forum.getkirby.com/u/romano)\
**Post date:** [May 15, 2020, 11:20am UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/4 "2020-05-15T11:20:44Z")

</div>

@anon77445132: Thanks for the hint. Yes, we followed the docs. And its not a problem with the migrated users. The problem is that the new installation does not encrypt password files of new users, but stores them as plain text in .htpasswd!

---

<div class="post-metadata">

**Author:** ![pixelijn](https://avatars.discourse-cdn.com/v4/letter/p/7ab992/32.png) [@pixelijn](https://forum.getkirby.com/u/pixelijn)\
**Post date:** [May 15, 2020, 11:34am UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/5 "2020-05-15T11:34:52Z")

</div>

As I already wrote above, if you are on PHP 7.4, you have to update (which you should do anyway). This is then an issue with versions before 3.3.2 not being compatible with PHP 7.4 resulting in plain text passwords being stored.

---

<div class="post-metadata">

**Author:** ![romano](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@romano](https://forum.getkirby.com/u/romano)\
**Post date:** [May 15, 2020, 12:21pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/6 "2020-05-15T12:21:14Z")

</div>

@pixelijn: Thanks very much for the explanation, this sounds plausible… Too bad that we can’t fix this without updating Kirby again! ☹ Is there maybe a shortcut from 3.2.5 to 3.3.6?

---

<div class="post-metadata">

**Author:** ![pixelijn](https://avatars.discourse-cdn.com/v4/letter/p/7ab992/32.png) [@pixelijn](https://forum.getkirby.com/u/pixelijn)\
**Post date:** [May 15, 2020, 12:23pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/7 "2020-05-15T12:23:18Z")

</div>

> [@romano](#):
>
> Too bad that we can’t fix this without upgrading Kirby again!

For security reasons you should always keep your Kirby version up to date.

Why don’t you want to update?

---

<div class="post-metadata">

**Author:** ![pixelijn](https://avatars.discourse-cdn.com/v4/letter/p/7ab992/32.png) [@pixelijn](https://forum.getkirby.com/u/pixelijn)\
**Post date:** [May 15, 2020, 12:51pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/8 "2020-05-15T12:51:06Z")

</div>

> [@romano](#):
>
> s there maybe a shortcut from 3.2.5 to 3.3.6?

What do you mean with a shortcut?

---

<div class="post-metadata">

**Author:** ![romano](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@romano](https://forum.getkirby.com/u/romano)\
**Post date:** [May 15, 2020, 12:56pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/9 "2020-05-15T12:56:05Z")

</div>

A short way… but ok, it’s fine, I’ll update.

---

<div class="post-metadata">

**Author:** ![anon77445132](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@anon77445132](https://forum.getkirby.com/u/anon77445132)\
**Post date:** [May 15, 2020, 1:02pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/10 "2020-05-15T13:02:03Z")

</div>

Look at [https://getkirby.com/docs/guide/quickstart#updates](https://getkirby.com/docs/guide/quickstart#updates) for details. But don’t update a live system without testing on your development system in front!

---

<div class="post-metadata">

**Author:** ![romano](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@romano](https://forum.getkirby.com/u/romano)\
**Post date:** [May 15, 2020, 1:06pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/11 "2020-05-15T13:06:35Z")

</div>

Thanks again! That helps! Just replacing the Kirby folder seems manageable! 🙂

---

<div class="post-metadata">

**Author:** ![pixelijn](https://avatars.discourse-cdn.com/v4/letter/p/7ab992/32.png) [@pixelijn](https://forum.getkirby.com/u/pixelijn)\
**Post date:** [May 15, 2020, 1:11pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/12 "2020-05-15T13:11:00Z")

</div>

There were only very few breaking changes between 3.2 and 3.3 and they shouldn’t affect you, see [https://github.com/getkirby/kirby/releases/tag/3.3.0](https://github.com/getkirby/kirby/releases/tag/3.3.0).

You might want to update deprecated methods though, to be prepared for the future…

---

<div class="post-metadata">

**Author:** ![romano](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@romano](https://forum.getkirby.com/u/romano)\
**Post date:** [May 15, 2020, 2:07pm UTC](https://forum.getkirby.com/t/can-t-log-in-to-panel-after-upgrade-due-to-unencrypted-passwords/18240/13 "2020-05-15T14:07:31Z")

</div>

@pixelijn: Great, thanks for your help!
