[Bug] Something doesn't work but don't know

[Tooool-alt]

Problem Summary / خلاصه مشکل

Not sure but it looks I cannot get any data from server stably.

Reproducible Steps / مراحل بازتولید

I don't know how to fill up this part.

Environment Details / مشخصات محیط

OS : for me, Win 10 and on the server Ubunto 22
App version: the last one just downloaded

Expected vs. Actual / انتظار در برابر نتیجه واقعی

To work but doesn't work.

From client:

⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣤⣄⡀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢠⣿⣿⣏⣹⣿⠄⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⣿⠿⠋⢠⣷⣦⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⡇⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⣧⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣿⣿⣿⣆⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣀⣿⣿⣿⣿⡆⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣤⣶⣿⣿⣿⠛⣿⣿⣿⣧⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⣠⣾⣿⣿⣿⣿⣿⣿⡇⢸⣿⣿⣿⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⣠⣴⣿⣿⣿⣿⣿⣿⣿⣿⣿⠇⢸⣿⣿⡿⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⢀⣠⣴⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⠿⠋⣠⣿⣿⣿⠇⠀⠀⠀⠀⠀⠀
⠀⠀⠰⢾⣿⣿⣿⡟⠿⠿⣿⣿⠿⠿⠛⠋⣁⣴⣾⣿⣿⠿⠋⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠉⠛⠻⠷⣶⣤⣤⣤⣤⣶⣾⣿⡿⠿⠛⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣠⢀⣶⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠘⠛⠛⠛⠛⠛⠂⠀⠀⠀⠀
17:03:48  CLIENT  INFO    GooseRelayVPN client starting
17:03:48  CLIENT  INFO    config loaded from client_config.json
17:03:48  CLIENT  INFO    SOCKS5 proxy: socks5://127.0.0.1:1080
17:03:48  CLIENT  INFO    mode: fronting
17:03:48  CLIENT  INFO    fronting via 216.239.38.120:443 (sni hosts: www.google.com, mail.google.com, accounts.google.com — 3 throttle buckets)
17:03:48  CLIENT  INFO    relay endpoints: 1 (AKfycb...V4ckHg)
17:03:48  CARRIER INFO    4 worker(s) across 1 account bucket(s) (1 endpoint(s)), 1 idle slot(s)/bucket
17:03:52  FRONTING INFO    startup probe keep sni=www.google.com err=unexpected probe body "{\"ok\":true,\"date\":\"2026-05-17\",\"count\":180,\"version\":1,\"protocol\":1}"
17:03:52  FRONTING INFO    startup probe keep sni=mail.google.com err=unexpected probe body "{\"ok\":true,\"date\":\"2026-05-17\",\"count\":180,\"version\":1,\"protocol\":1}"
17:03:52  FRONTING INFO    startup probe keep sni=accounts.google.com err=unexpected probe body "{\"ok\":true,\"date\":\"2026-05-17\",\"count\":180,\"version\":1,\"protocol\":1}"
17:03:52  FRONTING INFO    startup probe kept 3/3 sni hosts median_ttfb=0s
17:03:52  CLIENT  INFO    running pre-flight check (Apps Script reachable, VPS reachable, key matches)…
17:03:56  CLIENT  INFO    pre-flight OK: relay healthy, AES key matches end-to-end
17:03:56  CLIENT  INFO    ready: local SOCKS5 is listening on 127.0.0.1:1080
17:04:56  STATS   INFO    active=0 sessions=0/0 frames=0/0 bytes=0B/0B polls=11/0 rst=0 endpoints=1/1
17:04:56  STATS   INFO    endpoints: AKfycb...V4ckHg@acct-a ok=11 fail=0 today=12 script=185
17:04:56  STATS   INFO    accounts=[acct-a today=12 script=185]
17:05:56  STATS   INFO    active=0 sessions=0/0 frames=0/0 bytes=0B/0B polls=23/0 rst=0 endpoints=1/1
17:05:56  STATS   INFO    endpoints: AKfycb...V4ckHg@acct-a ok=23 fail=0 today=24 script=185
17:05:56  STATS   INFO    accounts=[acct-a today=24 script=185]
17:06:56  STATS   INFO    active=3 sessions=3/0 frames=0/0 bytes=0B/0B polls=34/0 rst=0 endpoints=1/1
17:06:56  STATS   INFO    endpoints: AKfycb...V4ckHg@acct-a ok=34 fail=0 today=35 script=185
17:06:56  STATS   INFO    accounts=[acct-a today=35 script=185]
17:07:10  CARRIER INFO    RST from server for session ee0cddd9; closing
17:07:11  CARRIER INFO    RST from server for session 15e6ef2b; closing

For "sudo journalctl -u goose-relay -f" I get this:

May 18 04:48:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:48:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:49:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:49:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:50:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:50:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:51:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:51:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:52:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:52:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:53:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:53:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:54:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:54:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:55:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:55:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:56:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:56:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:57:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:57:26 [stats] goroutines=3 active=0 clients=1 sessions(open=28 close=28) frames(in=281 out=243) bytes(in=188.4KB out=159.2KB) requests=553 dials(ok=28 fail=62) rst_sent=81 decode_fail=0
May 18 04:58:26 vm1960-8458.vpsmarket.org goose-server[108935]: 2026/05/18 05:58:26 [stats] goroutines=8 active=0 clients=1 sessions(open=28 close=28) frames(in=282 out=244) bytes(in=188.5KB out=159.3KB) requests=562 dials(ok=28 fail=62) rst_sent=81 decode_fail=0

And for "curl -I https://google.com" it gave me this:

HTTP/2 301 
location: https://www.google.com/
content-type: text/html; charset=UTF-8
content-security-policy-report-only: object-src 'none';base-uri 'self';script-src 'nonce-Zc5VBludT1Wjoas5iyGqOQ' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp
date: Sun, 17 May 2026 19:24:07 GMT
expires: Tue, 16 Jun 2026 19:24:07 GMT
cache-control: public, max-age=2592000
server: gws
content-length: 220
x-xss-protection: 0
x-frame-options: SAMEORIGIN
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

Logs / Screenshots / لاگ‌ها یا تصاویر

[Kianmhz]

Two separate things in your logs:

1. The unexpected probe body warning is harmless. Your Code.gs is returning the new JSON format ({"ok":true,"date":"…","count":180,…}) but the v1.6.0 client's fronting probe parser only knew the old text format. The log says keep and the next line says kept 3/3 sni hosts, so the hosts stay in rotation regardless. The parser was updated in 280e037 and will be in the next release. Ignore those three lines.

2. The real problem is on the VPS side, not the client. Look at your server stats:

dials(ok=28 fail=62) rst_sent=81

62 dial failures out of 90 (≈69% fail rate) and 81 RSTs sent back to the client. That's the server telling the client "I tried to open these upstream TCP connections to your destinations and they failed" — which is why your browser sees nothing. The two RST from server for session … lines at 17:07:10–11 are exactly those failures landing on the client.

To narrow it down, please share two things:

a) The actual dial error messages. The [stats] lines only show counts — the per-failure reason is logged separately. Run on the VPS:

sudo journalctl -u goose-relay --since "1 hour ago" | grep -E "\[exit\] dial|RST" | tail -40

Each failed dial logs [exit] dial <host:port>: <error>. The error message (i/o timeout vs connection refused vs no such host vs network is unreachable) is what tells us whether it's DNS, firewall, geo-block, or something else.

b) Test outbound from the VPS itself. The curl -I https://google.com you posted was from your Windows machine — that only proves your internet works, not the VPS's. SSH into the VPS and run:

curl -v -m 10 https://www.google.com -o /dev/null
curl -v -m 10 https://www.cloudflare.com -o /dev/null
dig +short www.google.com

If those fail or hang, the VPS itself has no working outbound and the fix isn't in goose-relay. If they succeed, the dial errors from (a) will tell us what's selectively failing.

[masoudbbd]

از دیروز از کار افتاده. خیلی خوب کار میکرد.
12:23:38
CLIENT INFO GooseRelayVPN client starting
12:23:38 CLIENT INFO config loaded from client_config.json
12:23:38 CLIENT INFO SOCKS5 proxy: socks5://127.0.0.1:1080
12:23:38 CLIENT INFO mode: fronting
12:23:38 CLIENT INFO fronting via 216.239.38.120:443 (sni hosts: www.google.com, mail.google.com, accounts.google.com — 3 throttle buckets)
12:23:38 CLIENT INFO relay endpoints: 1 (AKfycb...wZhEIQ)
12:23:38 CARRIER INFO 3 worker(s) across 1 bucket(s) (1 endpoint(s)), 2 idle slot(s)/bucket
12:23:42 FRONTING INFO startup probe keep sni=www.google.com ttfb=1.75s samples=2
12:23:42 FRONTING INFO startup probe keep sni=mail.google.com ttfb=2.152s samples=2
12:23:42 FRONTING INFO startup probe keep sni=accounts.google.com ttfb=2.208s samples=2
12:23:42 FRONTING INFO startup probe kept 3/3 sni hosts median_ttfb=2.152s
12:23:42 CLIENT INFO running pre-flight check (Apps Script reachable, VPS reachable, key matches)…
12:23:45 CLIENT WARN pre-flight FAILED:
12:23:45 CLIENT INFO relay returned a non-batch response.
12:23:45 CLIENT INFO The apps script deployment may be misconfigured or hitting a quota error: <title>خط...
12:23:45 CLIENT INFO continuing anyway — the issue may be transient or recover on its own
12:23:45 CLIENT INFO ready: local SOCKS5 is listening on 127.0.0.1:1080
12:23:46 CARRIER INFO endpoint AKfycb...wZhEIQ blacklisted for 3s (still rotating across 0 others)
12:23:46 CARRIER INFO relay returned non-batch payload via AKfycb...wZhEIQ (likely HTML/JSON error page), dropping response
12:23:46 CARRIER INFO relay returned non-batch payload via AKfycb...wZhEIQ (likely HTML/JSON error page), dropping response
12:23:54 CARRIER INFO relay returned non-batch payload via AKfycb...wZhEIQ (likely HTML/JSON error page), dropping response
12:23:54 CARRIER INFO relay returned non-batch payload via AKfycb...wZhEIQ (likely HTML/JSON error page), dropping response

[TWOC-MODS]

برای منم از امروز از کار افتاد
18:31:05 CLIENT INFO GooseRelayVPN client starting
18:31:05 CLIENT INFO config loaded from client_config.json
18:31:05 CLIENT INFO SOCKS5 proxy: socks5://127.0.0.1:1080
18:31:05 CLIENT INFO mode: fronting
18:31:05 CLIENT INFO fronting via 216.239.38.120:443 (sni=www.google.com)
18:31:05 CLIENT INFO relay endpoints: 1 (AKfycb...LHBWaA)
18:31:05 CARRIER INFO 3 worker(s) across 1 bucket(s) (1 endpoint(s)), 2 idle slot(s)/bucket
18:31:05 CLIENT INFO running pre-flight check (Apps Script reachable, VPS reachable, key matches)…
18:31:10 CLIENT INFO pre-flight OK: relay healthy, AES key matches end-to-end
18:31:10 CLIENT INFO ready: local SOCKS5 is listening on 127.0.0.1:1080
18:31:15 CARRIER INFO RST from server for session 2befe5c3; closing
18:31:32 CARRIER INFO RST from server for session 2ab06f3c; closing
18:31:38 CARRIER INFO RST from server for session bba267b8; closing
18:31:42 CARRIER INFO RST from server for session b19846fa; closing