gazhay
We need serious help to continue using railway. Server is halting often and we are not sure why.
I think this may be completely unrelated, but I have found that sometimes, without error, the internal routing between app and DB has failed at some point and does not re-establish so the front end goes down.
Then when I restart/redeploy either everything is ok, or I do then get an internal routing error.
I have just switched to "v2" setting of "deploy">"runtime" in the service settings as a possible solution to this and the need to wait a number of seconds before connecting to the db at boot time (also routing errors), but its too soon to say if this has been the solution.
We only use one connection to the DB though which is why I think it may be unrelated to your problem.
141 replies
Internal routing errors
It has been ongoing for some time over multiple posts, and I can also see from other posts on the help forum I am not the only one who has felt this way.
That said, in general terms I have always been happy with Railway, the service and staff, despite some issues (notably billing which was resolved over quite a long period) and have always treated railway employees with great respect and received respect in return. I was simply eliciting that my experience on this discord has jarred with that, and ultimately above when called out I have been threatened with receiving no further support on here or the help station.
Whilst I would prefer just to move on, I think that illustrates the point I was making, that it is one way or the highway in terms of the front line support on here.
In the interests of moving on though, I would be happy to retract my statement above and apologise to Brody. If I have misinterpreted our interactions then I am sorry I took offence where I hope none was intended. I hope you have a good day and that in future our interactions will be more cordial and respectful.
18 replies
Internal routing errors
Well, we went from working code -> migration of mysql -> still working -> overnight one night failed every single time with internal routing errors -> 10s delay -> everything works now as routing seems to take time to come up when the service is started -> working for a good while -> suddenly randomly routing fails until a restart or redeploy.
I'm not really sure why you feel the need to feel superior and belittle others at every opportunity Brody.
If you aren't living chronically online on the railway discord it is easy to miss new announcements (like this mysterious v2 runtime) In fact, having gone through the MySQL migration period and the issue is to do with MySQL routing, it was fair to assume that you were talking about that as "v2".
Your attitude here really detracts from the great experience at Railway and demeans you greatly.
18 replies
Intermittent network (DNS?) errors
I've been getting internal dns errors to local MySQL the last 2 days, they disappear as quickly as they appear (usually overnight uk tine)
Sometimes error is silent - loss of front end but nothing in logs until a restart then the errors appear but resolve after minutes.
64 replies
Whats going on with billing?
We used to get billed on 3rd of the month - but in January we were billed twice (3rd, 28th) and I think we just got billed again today (19th) = 22 days from last bill.
We had a ticket escalated about why the billing period changed last month, but heard nothing since - so I think its just the billing thing again, but its kinda worrying that its gone from monthly to 25 days and then 22, are we going to get billed again in 19?
15 replies