# Error 503 Service Uanavailable (Docker, Reverse Proxy)

**URL:** <https://forums.rocket.chat/t/error-503-service-uanavailable-docker-reverse-proxy/7536>\
**Category:** Community Support\
**Created:** [July 13, 2020, 12:25pm UTC](https://forums.rocket.chat/t/error-503-service-uanavailable-docker-reverse-proxy/7536 "2020-07-13T12:25:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![colinvv](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/colinvv/32/5247_2.png) [@colinvv](https://forums.rocket.chat/u/colinvv)\
**Post date:** [February 21, 2024, 12:52pm UTC](https://forums.rocket.chat/t/error-503-service-uanavailable-docker-reverse-proxy/7536/3 "2024-02-21T12:52:04Z")

</div>

Scratch that… I had my ingress pointing to the wrong RC container. Duh!  
Anyways, this post worked for me to upgrade M 4.4 to 5.

> [@Docker mongodb 4.4 to 5.0 upgrade...HOW it doesn't work frowning](https://forums.rocket.chat/t/docker-mongodb-4-4-to-5-0-upgrade-how-it-doesnt-work/16640/3):
>
> Thank you for the reply. I figured this out in case someone from the interwebs stumbles on this in the future: Follow the instructions here to create a database dump: docker exec \<database\_name (this is really the docker -ps name)\> sh -c 'mongodump --archive' \> db.dump Now for me it was important to drop the existing rocketchat database that was populated when bringing up the new rocketchat instance before trying to import my database dump. Stop the rocketchat container but leave the datab…

---

_[View the full topic](https://forums.rocket.chat/t/error-503-service-uanavailable-docker-reverse-proxy/7536)._