apernet / hysteria

Hysteria is a powerful, lightning fast and censorship resistant proxy.
https://v2.hysteria.network/
MIT License
13.98k stars 1.57k forks source link

parse client config failed decoding:\n\n* 'obfs' expected a map #1142

Open H1-N1 opened 2 weeks ago

H1-N1 commented 2 weeks ago

hi. igot this error when running hysteria in client mode failed to parse client config {"error": "1 error(s) decoding:\n\n* 'obfs' expected a map, got 'string'"} config:

{
  "server": "serverip:20000-50000",
  "auth": "asdff==",
  "obfs": "Aqw=",
  "up_mbps": 1,
  "down_mbps": 1,
  "retry": -1,
  "retry_interval": 1,
  "socks5": {
  "listen": "127.0.0.1:10802"
  },
  "http": {
  "listen": "127.0.0.1:1080"
  },
  "insecure": true,
  "ca": "",
  "recv_window_conn": 196608,
  "recv_window": 491520
}

also how can i add tun mode to the config ? thanks

haruue commented 1 week ago

Hello,

It looks like you are running Hysteria 2 with a Hysteria 1 config file.

Please have a look at the Hysteria 2 config guide: https://hysteria.network/docs/getting-started/Client/

H1-N1 commented 1 week ago

Hello,

It looks like you are running Hysteria 2 with a Hysteria 1 config file.

Please have a look at the Hysteria 2 config guide: https://hysteria.network/docs/getting-started/Client/

ok i will check this another proplem is this gonfig work with Version: v1.3.2

but the exposed proxy work only with curl but not global proxy nor any proxy app can you help pls

tobyxdd commented 1 week ago

"does not work" is not a valid description. Be more specific about the problem you are having

H1-N1 commented 1 week ago

"does not work" is not a valid description. Be more specific about the problem you are having

in wnindow log i get 2024-07-06T00:44:13+01:00 [INFO] [src:127.0.0.1:64100] [dst:www.youtube.com:443] [error:connection rejected: host resolution failure] SOCKS5 TCP error

now the message not showing but still no internet when i set the global proxy but when i test with curl with --socks5 argument it return the data (ipinfo)

tobyxdd commented 1 week ago

have you tested www.youtube.com with curl? this looks like a DNS problem