Calcom logs that I don't know how to fix

[pdmarf]

Hi all, I'm hosting calcom on proxmox vm. Locally it works fine. I'm using a self hosted pangolin tunnel (https://github.com/fosrl/pangolin) to access the local instance from the web. I'm finding when accessing it via a public url that it doesn't always work, and mostly is very slow. I'm getting this docker log but don't know if the error is related or how to fix it - just a newbie. Thanks for the help.

om/web:start: [PERF]: getEventTypesFromGroup(1) took 103.23184299468994ms
@calcom/web:start: [PERF]: getEventTypesFromGroup(1) took 102.88365200161934ms
@calcom/web:start: [next-auth][error][CLIENT_FETCH_ERROR]
@calcom/web:start: https://next-auth.js.org/errors#client_fetch_error fetch failed {
@calcom/web:start: error: {
@calcom/web:start: message: 'fetch failed',
@calcom/web:start: stack: 'TypeError: fetch failed\n at node:internal/deps/undici/undici:12637:11',
@calcom/web:start: name: 'TypeError'
@calcom/web:start: },
@calcom/web:start: url: 'https://meet.myurl.co.uk/api/auth/csrf',
@calcom/web:start: message: 'fetch failed'
@calcom/web:start: }
@calcom/web:start: [next-auth][error][CLIENT_FETCH_ERROR]
@calcom/web:start: https://next-auth.js.org/errors#client_fetch_error fetch failed {
@calcom/web:start: error: {
@calcom/web:start: message: 'fetch failed',
@calcom/web:start: stack: 'TypeError: fetch failed\n at node:internal/deps/undici/undici:12637:11',
@calcom/web:start: name: 'TypeError'
@calcom/web:start: },
@calcom/web:start: url: 'https://meet.myurl.co.uk/api/auth/csrf',
@calcom/web:start: message: 'fetch failed'
@calcom/web:start: }
@calcom/web:start: [next-auth][error][CLIENT_FETCH_ERROR]
@calcom/web:start: https://next-auth.js.org/errors#client_fetch_error fetch failed {
@calcom/web:start: error: {
@calcom/web:start: message: 'fetch failed',
@calcom/web:start: stack: 'TypeError: fetch failed\n at node:internal/deps/undici/undici:12637:11',
@calcom/web:start: name: 'TypeError'
@calcom/web:start: },

[dosubot[bot]]

Hello @pdmarf! I'm Dosu, a bot here to help you resolve bugs, answer questions, and guide you in becoming a contributor. I'm ready to assist you while we wait for a human maintainer. How can I help you today?

The "CLIENT_FETCH_ERROR" in NextAuth.js typically indicates a failed fetch request, which can be caused by several factors. Here are some steps to help resolve the issue:

1. Configuration Issues: Ensure that the NEXTAUTH_URL is correctly configured. It should match the public URL you are using to access the service. Verify that all OAuth providers are correctly set up.

2. Cookies Configuration: Check the cookies settings to ensure they are not being blocked or restricted by the browser. Proper cookie configuration is crucial for authentication and session management. Make sure secure cookies are enabled if using HTTPS, and verify the sameSite attribute settings ^[1].

3. Network Issues: Since you're using a tunnel, network latency or connectivity issues might be affecting performance. Ensure that the Pangolin tunnel is correctly set up and that your domain is properly configured to point to your VPS. You might want to test the tunnel with a service like ngrok to see if it improves connectivity ^[2].

4. Error Logging: Look for additional error details in the logs, such as the request body or specific error messages, to help diagnose the issue further.

By addressing these areas, you should be able to improve the performance and resolve the fetch errors you're encountering.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}