# Unable to upgrade past v5.33.5

**URL:** <https://forum.mattermost.com/t/unable-to-upgrade-past-v5-33-5/12136>\
**Category:** Troubleshooting\
**Created:** [August 31, 2021, 2:05pm UTC](https://forum.mattermost.com/t/unable-to-upgrade-past-v5-33-5/12136 "2021-08-31T14:05:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![battlemedialab](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/battlemedialab/32/5029_2.png) [@battlemedialab](https://forum.mattermost.com/u/battlemedialab)\
**Post date:** [August 31, 2021, 2:05pm UTC](https://forum.mattermost.com/t/unable-to-upgrade-past-v5-33-5/12136/1 "2021-08-31T14:05:13Z")

</div>

I manage a private Mattermost instance for our team, and due to other tasks taking priority the updating of Mattermost had been sidelined until recently.

I was able to upgrade to **5.33.5** , but upon attempting to upgrade to **5.36.2** I’m unable to restart the Mattermost service post-upgrade. `journalctl -xe` doesn’t appear to show anything of relevance to bring light to the issue (in upgrading to **5.32.1** that did reveal the need to upgrade to PostgreSQL 10.x).

I didn’t see any notable _important upgrade notes_ for the v5.36.x releases, so I’m not sure why the service fails to start post-upgrade. So I’m a bit confused as to what could be the issue at fault here.