missing response in batch from script | FULL mode

[BrPrS]

Hi,

I am using full mode version , but i am getting missing response in batch from scripterror in the app and nothing opens in the browser. here are the things that i've tried:

• I am sure about the AUTH_KEYand TUNNEL_AUTH_KEY , I checked them a couple of times and I am sure that they are correct and fine.
• I am sure about using the CodeFull.gs in my AppScript porject.
• when i use http://my_vps_ip:8080/health , i get ok in response.
• when i use curl with this command that i saw in previous issues curl -X POST 'http://localhost:8080/tunnel' \ -H 'Content-Type: application/json' \ -d '{"k":"TUNNEL_AUTH_KEY","op":"connect","host":"www.google.com","port":443}' \ --max-time 10` , i get {"sid":"285e38d8-5f14-494a-b030-789c51896001","eof":false}

I would really appreciate if someone help me to solve this issue.

[therealaleph]

@BrPrS — missing response in batch from script in full mode means the Apps Script _doTunnel call took longer than 30s (the batch timeout) without responding. Diagnostic ladder:

1. Verify your tunnel-node is reachable from outside your network:

curl -k -i https://your-tunnel-domain:port/

Should return {"v":"...","tn":...} JSON with the tunnel-node version. If it times out / refuses, your VPS firewall is blocking — check iptables / cloud-provider firewall rules.

2. Verify TUNNEL_SERVER_URL in CodeFull.gs matches what you got working in step 1 (including https:// prefix and port if non-443).

3. Verify TUNNEL_AUTH_KEY matches between:

• const TUNNEL_AUTH_KEY in CodeFull.gs
• The TUNNEL_AUTH_KEY env var you started tunnel-node with (docker run -e TUNNEL_AUTH_KEY=...)

4. Check Apps Script's Executions tab at script.google.com → your project → Executions. If the most recent _doTunnel runs are failing, the error message there tells you what's wrong (auth, URL unreachable, etc.).

5. Check tunnel-node logs for incoming requests:

docker logs mhrv-tunnel --tail 100 | grep -i 'tunnel\|auth'

• If you see no requests at all, Apps Script can't reach you (back to step 1)
• If you see auth failures, TUNNEL_AUTH_KEY is wrong (back to step 3)
• If you see successful requests but the client still times out, the tunnel-node's response is being blocked by Apps Script's response size limits or your destination is dead

Most common cause: tunnel-node listening on 127.0.0.1 instead of 0.0.0.0, or the docker port-mapping is wrong (-p 8080:8080 is what you want, not -p 127.0.0.1:8080:8080).

Paste output of steps 1, 4, 5 if still stuck.

---

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

[BrPrS]

curl -k -i https://your-tunnel-domain:port/ ruturns :
curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed
log when i tried to use firefox to open the url :

received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

I tried with :

• using my vps_tunnel_ip in curl
• using my domain_vps in curl

the results were the same

i have another service run on this url with https (port 443) it works just fine.
the problem is just when i try to open https://my_domain:8080/ that docker service of this project is run on it

[therealaleph]

Closing this for now because there has been no activity from the original reporter for more than 7 days.

If this still needs attention on the latest release, please comment here or reopen with the current version, mode, relevant config shape, and fresh logs/details.

---

Answered via LLM, Supervised @therealaleph