Connor
Connor
Explore posts from servers
CDCloudflare Developers
Created by Connor on 10/21/2023 in #pages-help
Build Error Next.js
I am getting the below error when trying to build my nextjs project using npx @cloudflare/next-on-pages@1 . This makes no sense because export const runtime = 'edge'; is set on my root layout which applies to every page in my entire repo.
⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️
⚡️ The following routes were not configured to run with the Edge Runtime:
⚡️ - /index
⚡️
⚡️ Please make sure that all your non-static routes export the following edge runtime route segment config:
⚡️ export const runtime = 'edge';
⚡️
⚡️ You can read more about the Edge Runtime on the Next.js documentation:
⚡️ https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
⚡️
⚡️ The following routes were not configured to run with the Edge Runtime:
⚡️ - /index
⚡️
⚡️ Please make sure that all your non-static routes export the following edge runtime route segment config:
⚡️ export const runtime = 'edge';
⚡️
⚡️ You can read more about the Edge Runtime on the Next.js documentation:
⚡️ https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
2 replies
CDCloudflare Developers
Created by Connor on 10/17/2023 in #pages-help
Segmentation Fault - Failed Builds
Hello, I was deploying one of my Next.js Pages sites and it all of a suddent started throwing Segmentation fault and failing to deploy. I thought this was strange because not much code had changed, so I redeployed the last working deployment that was working and it throws the same error now. So this is not a problem with my code, but a problem with pages. Anyone have any thoughts? Not Working Deployment: d5b8240e-4109-41e2-bae9-ed17078d05b3 Working Deployment: 15e1d74a-3357-41f3-b94e-63e94247dd95 Account: 4155cbb49d5f64034f319f1ef5182bec Not Working Deployment Logs Attached
7 replies
RRailway
Created by Connor on 6/18/2023 in #✋|help
Fix Postgres DB
Me being dumb ran the following on my Postgres...
ALTER SYSTEM SET shared_preload_libraries = 'timescaledb,pg_stat_statements';
ALTER SYSTEM SET shared_preload_libraries = 'timescaledb,pg_stat_statements';
which has entered the database into an endless cycle of errors
2023-06-18 00:54:39.469 UTC [1] FATAL: could not access file "timescaledb,pg_stat_statements": No such file or directory
2023-06-18 00:54:39.469 UTC [1] LOG: database system is shut down
2023-06-18 00:54:39.469 UTC [1] FATAL: could not access file "timescaledb,pg_stat_statements": No such file or directory
2023-06-18 00:54:39.469 UTC [1] LOG: database system is shut down
but I can't undo what I did because the DB wont start. How can I fix this?
15 replies
RRailway
Created by Connor on 6/13/2023 in #✋|help
Intermittent Network Errors
I am receiving intermittent errors from my service today. There have been no configuration changes to deployment or restarts in the ~2 last weeks. This is just happening today. The service is load balanced with 2 replicas, and there are no errors in the logs for them.
Method: GET
Status: 503

upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: immediate connect error: Cannot assign requested address
Method: GET
Status: 503

upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: immediate connect error: Cannot assign requested address
13 replies
RRailway
Created by Connor on 3/30/2023 in #✋|help
New Service Erroring
Hello, I have added a new service to a project which is an exact copy of another service. It is a node.js app deployed from a github repo. It is the exact same env variables and config options, however, it keeps crashing due to different errors. It is a Directus instance. Any help/guidance why I am getting inconsistent errors between two services that are configured exactly the same would be helpful
7 replies