for reference... everyone was sleeping when this happened

Hello,

We are really sorry you had your application go down, we redeployed your workload onto another box because we needed to do maintenance on the host your deployment was previously running on.

I've increased the sort buffer size on your database and triggered a restart of Strapi and it seems to be online now!

For the troubles I've given the team credits that should cover the next couple of months.

Again, we are really sorry about this.

Best,
Brody

App down here. Sometimes i can see login page but cant login and all other times never reach login and gives me 502 ERROR

Thanks @Brody - we're seeing a ton of site errors still. Random pages load instantly (like home) and others crash or never load. Any suggestions?

@loukaseng, That's a completely separate issue, please open your own help thread.

@famviatravel, i'll look into it!

@famviatravel, I saw your HTTP Logs had high request times with 499's meaning likely a client side timeout was reached.

I also noticed that you had Strapi connecting to the database over the public network.

I went to ahead and configured Strapi to connect to the database via the private network for you, that should both decrease service to database latency, and significantly cut down on egress in that regard!

After making that change, your request times looks to be in check, with 200's across the board.

I also see a hand full of 502's when Starpi first starts, this is likely because you are not using a health check and thus Railway doesn't know the appropriate time to start routing traffic to the deploy, I would recommend trying /admin/auth/login as your health check.

amazing, thank you so much Brody

next time you want to head to disney with the fam or take a cruise - let me know, we'll hook it up

That's very kind of you, thank you so much!

Going to mark this as solved, but please feel free to open back up if anything isn't up to your expectations!