struggling to connect to self-signed backend on same wg network

JavaScript
1

2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info]Sending request to https://api.supercooked.co/api/v1/auth/login/json
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn info Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to ‘0’ makes TLS connections and HTTPS requests insecure by disabling certificate verification.
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info](Use node --trace-warnings ... to show where the warning was created)
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info]API proxy error: TypeError: fetch failed
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at node:internal/deps/undici/undici:13510:13
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at async handleApiProxy (file:///app/build/server/chunks/hooks.server-B57kv747.js:85:27)
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at async respond (file:///app/build/server/chunks/index-Cj_gKmBH.js:4064:22)
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at async Array.ssr (file:///app/build/handler.js:1287:3) {
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] [cause]: Error: connect EACCES fdaa:b:33cf:a7b:35c:0:a:602:443
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16)
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] errno: -13,
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] code: ‘EACCES’,
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] syscall: ‘connect’,
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] address: ‘fdaa:b:33cf:a7b:35c:0:a:602’,
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] port: 443
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info] }
2025-08-07T20:57:35Z app[080ee7ef1d7278] arn [info]}

2

the api in this case is just a dns forward in cloudflare to the ipv6

4

Hm… This looks like it might be a WireGuard peer. Where is the backend running?

5

it is a wireguard peer (I recognise a7b:35c from my own peers in arn).

“connect EACCES” seems like a permissions issue at the linux level, specifically permission denied opening the TCP socket. it’s a really weird error, especially in a Fly Machine :thinking:

1 Like
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.