a year ago
Something is wrong on my server, I noticed when I'm trying to post data, like sending a form, the request never resolves.
I waited for around 15 min after sending a post request and after that I got a weird error:
"net::ERR_HTTP2_PROTOCOL_ERROR"
I also tried going directly into my postgres client to try and create a record but my db client (DBeaver) freezes, this happens between all my services.
Reads are going as fast as always but the system became unusable like this.
I recently moved to the pro membership and created a schedule to backup my databases, before that everything worked just fine, I don't know it that has something to do with my problem.
3 Replies
a year ago
Hello,
I can access the site just fine, and the Data tab can access the database just fine, this is looking more like an issue with your network.
Best,
Brody
Status changed to Awaiting User Response Railway • 12 months ago
Status changed to Awaiting Railway Response Railway • 12 months ago
brody
Hello,I can access the site just fine, and the Data tab can access the database just fine, this is looking more like an issue with your network.Best,Brody
a year ago
Thank you for your quick response, but this response does not address the issue I'm trying to communicate.
Yes, the connection to the DB works fine, the same goes for reads to the data, that is great.
The issue in on the Writes.
I just tried to delete a row from the user table on that service, if you have access to it, try doing it from data panel too.
The record I'm trying to delete is the one with id 10, it is a dangling record.
If deleting is not suitable, try adding a record.
a year ago
I tried to delete the user with table 10 and got the following error:
update or delete on table "user" violates foreign key constraint "FK_51dc2344d47cea3102674c64963" on table "credential"
Can you try and tell me what happens?
Writing for me (record with ID 99) was instant.
Status changed to Awaiting User Response Railway • 12 months ago
7 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 7 months ago