Full mode tunnel connect_data error

[cmptrnb]

ERROR tunnel connect_data error for cloud.digitalocean.com:443: missing response in batch from script AKfycbwh

Why is it trying to reach port 443? I specified port 8443 for my tunnel-node.

[therealaleph]

@cmptrnb — cloud.digitalocean.com:443 is the destination port, not the tunnel-node port. The relay log line says: "I, the tunnel-node, tried to open a TCP connection to cloud.digitalocean.com on port 443 (which is what HTTPS uses), and Apps Script never came back with a response."

8443 is the port tunnel-node is listening on for incoming Apps Script requests (the inbound side). It's unrelated to which destinations the tunnel reaches — those are dictated by the URL the browser is loading.

missing response in batch from script AKfycbwh means the Apps Script side didn't return within the 30s batch timeout. Causes:

1. Apps Script daily quota exhausted (~20k UrlFetchApp/day per Google account) — hit the script's Executions tab at script.google.com to see if there's a daily-quota error
2. TUNNEL_AUTH_KEY mismatch between CodeFull.gs and the tunnel-node — Apps Script's _doTunnel rejects the request, returns nothing, batch times out
3. TUNNEL_SERVER_URL wrong / unreachable from Apps Script — verify by hitting https://your-tunnel.com:8443/ in a browser, you should see "tunnel-node v1.x.x"
4. tunnel-node firewall blocking — iptables -L -n | grep 8443 on the VPS, allow the port

Run mhrv-rs test won't help in full mode (see #665). Verify by:

1. Hit your tunnel-node URL directly: curl -k https://your-tunnel.com:8443/ -i — should return JSON
2. Open the Apps Script Executions tab and look for the most recent _doTunnel run + its error if any

If still stuck, paste the most recent _doTunnel error from the Executions tab.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}

[cmptrnb]

Is it supposed to be HTTP or HTTPS?

Command from Windows PC with HTTP:

curl.exe -k http://YOUR_VPS_IP:8443/ -i

Response:

HTTP/1.1 404 Not Found
content-length: 0
date: Sun, 03 May 2026 14:57:16 GMT

Command with HTTPS:

curl.exe -k https://YOUR_VPS_IP:8443/ -i

Response:

curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid

[cmptrnb]

Command with HTTPS from a Linux PC gives a different error than on Windows:

curl -k https://YOUR_VPS_IP:8443/ -i

It says TLS connect error, packet length too long.

[cmptrnb]

Answered elsewhere. It should be HTTP unless you are using some kind of reverse proxy in front of your tunnel-node server.