I just made a deployment of this template and it is built correctly. However, this is the error i am getting when deploying.

```(node:7) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).

For more information, check the migration guide at https://a.co/7PzMCcy

(Use node --trace-warnings ... to show where the warning was created)

LocalStore: store created at

LocalStore: store created at

LocalStore: store created at

/app/bundle/programs/server/npm/nodemodules/meteor/promise/nodemodules/meteor-promise/promise_server.js:218

throw error;

^

Error: /usr/lib/x8664-linux-gnu/libstdc++.so.6: version `GLIBCXX3.4.29' not found (required by /app/bundle/programs/server/npm/nodemodules/isolated-vm/out/isolatedvm.node)

at Object.Module._extensions..node (internal/modules/cjs/loader.js:1173:18)

at Module.load (internal/modules/cjs/loader.js:979:32)

at Module.Mp.load (/app/bundle/programs/server/runtime.js:37:33)

at Function.Module._load (internal/modules/cjs/loader.js:819:12)

at Module.require (internal/modules/cjs/loader.js:1003:19)

at require (internal/modules/cjs/helpers.js:107:18)

at Object. (/app/bundle/programs/server/npm/node_modules/isolated-vm/isolated-vm.js:1:-44)

at Module._compile (internal/modules/cjs/loader.js:1114:14)

at Module.Mp._compile (/app/bundle/programs/server/runtime.js:77:23)

at Object.Module._extensions..js (internal/modules/cjs/loader.js:1143:10)

at Module.load (internal/modules/cjs/loader.js:979:32)

at Module.Mp.load (/app/bundle/programs/server/runtime.js:37:33)

at Function.Module._load (internal/modules/cjs/loader.js:819:12)

at Module.require (internal/modules/cjs/loader.js:1003:19)

at require (internal/modules/cjs/helpers.js:107:18)

at npmRequire (/app/bundle/programs/server/npm-require.js:111:12)

at Module.useNode (packages/modules-runtime.js:751:18)

at module (/app/bundle/programs/server/packages/modules.js:205069:8)

at fileEvaluate (packages/modules-runtime.js:336:7)

at Module.require (packages/modules-runtime.js:238:14)

at Module.moduleLink as link

at module (app/integrations/server/lib/isolated-vm/isolated-vm.ts:2:43)

at fileEvaluate (packages/modules-runtime.js:336:7)

at Module.require (packages/modules-runtime.js:238:14)

at Module.moduleLink as link

at module (app/integrations/server/lib/triggerHandler.js:1:1149)

at fileEvaluate (packages/modules-runtime.js:336:7)

at Module.require (packages/modules-runtime.js:238:14)

at Module.moduleLink as link

at server/services/meteor/service.ts:1:72

at module (server/services/meteor/service.ts:286:2)

at fileEvaluate (packages/modules-runtime.js:336:7)

at Module.require (packages/modules-runtime.js:238:14)

at Module.moduleLink as link {

code: 'ERRDLOPENFAILED'

}
```

Any ideas?

it seems rocket chat broke something with their latest image, at the time of writing this "rocket.chat:6.5.3" is the most up-to-date image that works, replace the services source with that image

I've set the default image to the last working image that Brody mentioned until RocketChat fixes it.

If you require the latest version right now, however, then you can follow these steps as a workaround:

1. Deploy RocketChat Template

2. Go To RocketChat Service Settings

3. Disconnect the source

4. Reconnect the source pointed to [rocket.chat](rocket.chat)

5. Add the following Service Variable: RAILWAY_RUN_UID and set it to 0

6. Paste the following into the custom start command:

/bin/sh -c "echo 'deb http://deb.debian.org/debian testing main' >> /etc/apt/sources.list && \ echo 'deb http://deb.debian.org/debian testing-updates main' >> /etc/apt/sources.list && \ echo 'Installing GLIBC...' && \ apt-get update && \ apt-get install -y libc6 g++-11 && \ echo 'GLIBC succesfully installed! Starting app...' && \ node main.js"

What this will do is install the required packages that are missing before starting RocketChat. This is a temporary workaround but I'd still recommend waiting until RocketChat fixes it officially, but if you need the latest version, then this solution should help you.

Issue seems to have been resolved, set the default RocketChat template version back to latest

As of today, trying to spin up a new Rocket.Chat instance deploys, but doesn't successfully post anything to the deployed URL, and the Rocket Chat module is in a crashloop.

Edit: Tried the workaround above but I don't think they're the same issue!

I just deployed rocket chat and it's working fine for me

My best guess is that it's running out of memory when you deploy it. Rocket chat uses about 600mb memory and Trial Plan has a cap of 500mb memory per service, you might need to upgrade to hobby plan to be able to deploy rocket chat on Railway

Great insight, thank you!

Also leaving this link for others; you can skip the Workspace Registration by setting an env variable:
https://github.com/RocketChat/Rocket.Chat/issues/31163#issuecomment-1847851950

I think there is an issue with this template. When I do a fresh install, setup community (do the env trick as well), after I get through setup, and then add a user, the web socket says it's working, but there is no real-time working at all.I'll open a window on a different computer, login with a different account, and try to message back and forth with no luck. I have to refresh the page every time to update.To notes, I have also redeploys, updated my domain, updated license, etc. So I know everything is refreshed on the build end.

Hey Cory!

I spent 2 hours and multiple fresh deployments trying to figure out what causes that problem and I could not find any misconfiguration on my end, the only misconfiguration could be that the database is not set up as a replica-set but after creating a new deployment that configured the db as a replica-set I still faced the same problem. I'll try and spend more time later trying to uncover why this happens

I have been trying to deploy over the last two days and nothing. WE still don't have a solution and the template deployment is set to 50%.

Hey daynelinx, thanks for flagging! Railway recently changed how database url strings are handled, it used to have a private url specified in a DATABASE_PRIVATE_URL variable, templates usually used that but Railway has since renamed them to DATABASE_URL. This caused the RocketChat template to attempt to connect to the connection string in that variable despite it being empty. I have fixed this problem and RocketChat should work again.

Please note, however, that RocketChat won't work on Trial plans since RocketChat itself uses more than 500mb RAM.

Hi dev,

I figured the 500mb limit but did not know about the database URL. What do you suggest for testing the service out? Would it be good to scale temporarily to the required specs and then the user has the option to proceed after the 24hr deployment window? Or, am i grossly oversimplifying this? Appreciate your prompt response.

Sorry for taking so long to get back to you, I went to bed after my previous response.

The problem with the current situation is that you're on Trial plan from what I can tell, trial plan has a hard-limit of 500mb RAM on services. You wouldn't be able to scale past this point and therefore RocketChat (who runs at about 700mb memory usage) won't be able to start.

The only solution here would be to upgrade to Hobby plan to unlock higher memory caps (in that case you'll have 8gb RAM instead of just 500mb RAM), I noticed your other thread and I'll explain this further there

I also feel it's necessary for me to share that there has been past issues with the RocketChat template, Cory has reported an issue with chat streaming. Meaning to say messages don't appear until you refresh, I've tried a lot of things but couldn't get it working for the life of me. I've recently tried locking RocketChat to the last known version I know for sure it was working at but haven't tested if chat streaming is working again, yet. So if you're only on Railway for this template then I feel this is very important for me to share. You can of course try deploying RocketChat without using this template if the problem still exists, but I just wanted to give you this warning.