Pepijn Comments - Answer Overflow

Topics

Pepijn

Explore posts from servers

CDCloudflare Developers RRailway

•Created by Pepijn on 11/6/2024 in #✋｜help

Build runner # CPU and amount of memory

N/A

5 replies

•Created by Pepijn on 11/1/2024 in #✋｜help

Snapshot phase taking very long

Started eventually after 12 minutes

4 replies

•Created by Pepijn on 11/1/2024 in #✋｜help

Snapshot phase taking very long

a0f3572b-295e-4a43-b776-ce352a4d0980

4 replies

•Created by Pepijn on 10/3/2024 in #✋｜help

Services down

Pretty much anything so not going to post al service IDS

13 replies

•Created by Pepijn on 10/3/2024 in #✋｜help

Services down

And c6f6b68a-8b76-42d7-bd0a-65e794ac8fef

13 replies

•Created by Pepijn on 10/3/2024 in #✋｜help

Services down

a0f3572b-295e-4a43-b776-ce352a4d0980

13 replies

•Created by Josh Larson on 2/5/2024 in #✋｜help

Sending Laravel logs to Railway's logger

Thanks for your reply. I eventually fixed got it to work by doing some config changes to the php-fpm conf I add in the docker image.

10 replies

•Created by Josh Larson on 2/5/2024 in #✋｜help

Sending Laravel logs to Railway's logger

@Josh Larson you got this working in the end? We run into the same issue where no Laravel logs appear.

10 replies

•Created by Pepijn on 8/16/2024 in #✋｜help

Services not loading in Railway dashboard

For example

8 replies

•Created by Pepijn on 8/16/2024 in #✋｜help

Services not loading in Railway dashboard

a0f3572b-295e-4a43-b776-ce352a4d0980

8 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

So not really sure if it was maybe related to any of the issues from this incident https://discord.com/channels/713503345364697088/846875565357006878/1270411636527726674

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

I just created a new node v20 instance, not the fetches seem to work again

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

In staging I downgraded the NextJs Node version to v18 and from that point on the fetches worked again.

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

Hi Brody, thanks for your replies. This is maybe a better view: https://railway.app/project/fc130f30-4c71-4ab5-99b3-dbff85ca4dea/logs?filter=%40level%3Aerror&start=1722463200000&end=1722852000000 You can see the errors in the production environment

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

Seems weird that this issue showed up on the new Edge Proxy, but maybe the new proxy has some requirements on which HTTP version it supports.

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

I have downgraded the Node version on the NextJs project to v18 (was v20) and now the fetches seem to work

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

Adding some verbose logging gives these fetch error: SocketError: other side closed / UND_ERR_SOCKET

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

I have added a reproduction staging environment for this project: https://railway.app/project/fc130f30-4c71-4ab5-99b3-dbff85ca4dea Building the NextJs Frontend when having the new Edge Proxy enabled on the Strapi CMS will result in build failures where fetches to the CMS fails. Switching on Legacy proxy results in succsfull builds.

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

You can see for example these production error logs where since 1 aug many errors occur: - https://railway.app/project/fc130f30-4c71-4ab5-99b3-dbff85ca4dea/logs?filter=%40level%3Aerror&start=1721117351871 - https://railway.app/project/3160979a-66a1-4ab0-b77f-1ef3fe72acf4/logs?filter=%40level%3Aerror&start=1721117642017

16 replies

•Created by Pepijn on 8/6/2024 in #✋｜help

New Edge Proxy 5xx errors

fc130f30-4c71-4ab5-99b3-dbff85ca4dea

16 replies