# Rocket Chat reverse proxy crashed after upgrade 6.1.5 to 7.1.2 **URL:** \ **Category:** Community Support\ **Created:** [June 10, 2025, 8:09am UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225 "2025-06-10T08:09:23Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![marcin7](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@marcin7](https://forums.rocket.chat/u/marcin7)\ **Post date:** [June 10, 2025, 8:09am UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225/1 "2025-06-10T08:09:23Z")
Hello, after Rocket.Chat upgrade from v6.1.5 to v7.1.2 reverse proxy on Apache has stopped working. Before upgrade my Rocket Chat instance url links looked like this: [https://mydomain.com/chat/group/mychannel](https://mydomain.com/chat/group/mychannel). After upgrade the links look like this: [https://mydomain.com/group/mychannel](https://mydomain.com/group/mychannel) The /chat from URL get cut off every time and browser tell me “The requested URL was not found on this server.” Below I paste my Apache configuration: ```auto Order allow,deny Allow from all RewriteEngine On RewriteCond %{HTTP:Upgrade} =websocket [NC] RewriteRule /var/www/(.*) ws://*rocketchat_instance_ip*:3000/$1 [P,L] RewriteCond %{HTTP:Upgrade} !=websocket [NC] RewriteRule /var/www/(.*) http://*rocketchat_instance_ip*:3000/$1 [P,L] ``` From /lib/systemd/system/rocketchat.service: `ROOT_URL=https://*rocketchat_instance_ip*:3000/chat` I am very much asking for your support. Kind regards, Marcin ### Server Setup Information - Version of Rocket.Chat Server: 7.1.2 - Operating System: Debian 11 - Deployment Method: Debian package - Number of Running Instances: 1 - DB Replicaset Oplog: - NodeJS Version: v20.19.2 - MongoDB Version: 5.0.31 / wiredTiger (oplog Enabled) - Proxy: - Firewalls involved: no ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [June 10, 2025, 11:44am UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225/2 "2025-06-10T11:44:19Z")
> [@marcin7](#): > > Debian package There isn’t a “debian package” I am aware of. So how have you deployed it? > [@marcin7](#): > > Rocket.Chat Server: 7.1.2 You have left it a bit late for upgrading. Your version is EOL on the 30th June… > **[Version Durability](https://docs.rocket.chat/docs/version-durability)** > **[Deprecated and phasing out features](https://docs.rocket.chat/docs/deprecated-and-phasing-out-features)** Note there were substantial changes for v7. As a sysadmin you should read all the release notes before upgrading to see what will/won’t affect you, I am not sure they specifically removed this, but the docs have always been pretty clear that Rocket.Chat should be run on it’s own host eg [https://chat.mydomain.com](https://chat.mydomain.com) rather than [https://host.domain.com/chat](https://host.domain.com/chat) ---
**Author:** ![marcin7](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@marcin7](https://forums.rocket.chat/u/marcin7)\ **Post date:** [June 10, 2025, 12:15pm UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225/3 "2025-06-10T12:15:31Z")
Thank You for quick answer 🙂 My Rocket Chat instance was installed according to this doc: > **[Deploy on Debian](https://docs.rocket.chat/docs/deploy-on-debian)** I have plans to upgrade Rocket Chat and MongoDB to a higher version. So currently there is no way to use Rocket Chat as a subdirectory? like [https://mydomain.com/chat](https://mydomain.com/chat). Currently, Rocket Chat must have its own subdomain as in the example you provided? Kind regards, Marcin ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [June 10, 2025, 3:15pm UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225/4 "2025-06-10T15:15:49Z")
> [@marcin7](#): > > So currently there is no way to use Rocket Chat as a subdirectory? like [https://mydomain.com/chat](https://mydomain.com/chat). > Currently, Rocket Chat must have its own subdomain as in the example you provided? I need to check - this was the subject of much debate over the years as they were going to deprecate and then not. A search here will show you. I am not sure what has happened and will try and find out but might take a while. But to be honest you will be much better to use a sub domain as per the docs. SSL certs are free (I prefer dehydrated compared the overweight monster that is certbot!) so why not? ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [June 10, 2025, 5:09pm UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225/5 "2025-06-10T17:09:33Z")
Just noticed you went from 6.1.x Waaaayout of date. That is a huge leap for here. There were a lot of (controversial) changes at 6.5 and more at 7.x So yes, somewhere there sub directories were quietly dropped. Check the changelogs. But no, unlikely to come back. So a host is required. As any version is only supported for 6 months (yup annoying as hell) you really need to be on top of upgrades. I usually track one release behind. So currently 7.6.x + and a test on 7.7.x As I said above, 7.1 is EOL shortly. No rest for admins ☹ ---
**Author:** ![reetp](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/reetp/32/5546_2.png) [@reetp](https://forums.rocket.chat/u/reetp)\ **Post date:** [July 6, 2025, 8:55am UTC](https://forums.rocket.chat/t/rocket-chat-reverse-proxy-crashed-after-upgrade-6-1-5-to-7-1-2/22225/6 "2025-07-06T08:55:26Z")
Found it. Warning was given a long time ago. They had struggled to support it for a long time. It is not going to re-appear, especially with https certs being cheap & easy. > [@Support for installation in subdirectory will be discontinued](https://forums.rocket.chat/t/support-for-installation-in-subdirectory-will-be-discontinued/6371): > > We intend to drop official support for Rocket.Chat installation under subdirectories (with Release 4.0). Over the years there have been many times that we’ve added a new piece of functionality or a contribution merged and it’s ended up with subdirectory support broken. Subdirectory support is complicated in general. But for a large and complex code base like ours we don’t feel maintaining support for it is doing either of us favors. An example of subdirectory in use: [https://www.mydomain.co…](https://www.mydomain.com/chat)