You're on the trial plan and are limited to 500GB Volumes, MongoDB can not happily run with only 500MB, you will need to upgrade to the Hobby plan for access to 5GB volumes, after the upgrade go into the volume's settings to grow it to 5GB.

ok, it was working fine for 10 days or so

yep, you ran out of storage

well, there were 2 records in one collection (really small ones, a few text/int fields) and another 40 records with mostly text. the server was not accessed for a few days so it's a bit weird that it started crashing. i deleted now all the 40 short text records and the server keeps crashing - are we sure this is the problem? there were no issues until yesterday, it never crashed. now it's empty and keeps crashing.
how can i be certain that your infra is reliable when i go to prod?…

I am absolutely certain, this happens all the time for trial users, 500MB is not enough to run MongoDB happily, nothing to do with the Railway platform itself

and i would just like to clarify something since you said "your infra"..
I don't work for railway

well, just upgraded to hobby plan. keeps crashing. why is that?

have you grown the volume?

not sure how

i tried redploying now

it gives some error messages but not crashing now. but it seems it cannot create DB connection

i can't find nowhere where to increase volume size

as previously mentioned, go into the volumes settings and grow it to 5gb

and no db connection

where is volume settings

click on the volume

where is the volume

no volume in settings

the volume is attached to the service

click on the volume, it is on the project canvas

ok, found it

I didn't know it needed finding <:kekw:788259314607325204>

well, someone should do UX here

i think it's working, thanks

btw, the other service cannot connect to the DB now, anything that needs to be "rewired" somehow?

please provide specific errors

2024-07-04 19:12:16,499 (async_telebot.py:565 MainThread) ERROR - TeleBot: "mongodb.railway.internal:27017: [Errno -2] Name or service not known (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: ]>"

are the two services in the same project

i am trying to redploy

yes, same project

it was working before mongodb started crashing

do you have the V2 runtime enabled

it was on legacy - was it changed somehow or it was in legacy when i started the project?

it was legacy when you started the project, switch to v2

ok, but i think i still have the same error

have you switched to the v2 runtime

yep

both are V2

deploy logs please -

Starting Container

Started server process [2]

Waiting for application startup.

Application startup complete.

Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit)

2024-07-04 19:20:53,215 (async_telebot.py:565 MainThread) ERROR - TeleBot: "mongodb.railway.internal:27017: timed out (configured timeouts: socketTimeoutMS: 20000.0ms, connectTimeoutMS: 20000.0ms), Timeout: 30s, Topology Description: ]>"

this is the app

use the bookmarklet please

well, the tool is not "brave" browser friendly

1258505531698712576

logs of the app please

1258505667367534622

can you connect to the database locally

yep

any idea?

something is messed up in internal networking?

there?

Should i create a ticket somewhere else?

hobby users are only eligible for support from the community, so please be patient