rathole::server: Failed to deserialize hello: invalid value: integer `66326`, expected variant index 0 <= i < 2

rapiz1 / rathole

A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok.

Apache License 2.0

9.44k stars 475 forks source link

rathole::server: Failed to deserialize hello: invalid value: integer `66326`, expected variant index 0 <= i < 2 #309

Open passwa11 opened 10 months ago

passwa11 commented 10 months ago

rathole::server: Failed to deserialize hello: invalid value: integer 66326, expected variant index 0 <= i < 2

fernvenue commented 10 months ago

Hi, could you please provide your configuration file?

SakaZhang commented 10 months ago

i got same prob.

fernvenue commented 10 months ago

Could anyone provide configuration? I don't think we can reproduce this issue without any useful information.

fernvenue commented 8 months ago

You guys just keep saying that you all experiencing this, but no one provide any configuration example or useful information, what a joke.

bfshires commented 8 months ago

This message is produced on my server when a port scan is received. If I scan the ports of my server with nmap, this message shows up.

SakaZhang commented 8 months ago

You guys just keep saying that you all experiencing this, but no one provide any configuration example or useful information, what a joke.

sry about that. I turn to use frp and no more pay attention to this issue. Here is some info: os: 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

version: rathole v0.4.8

client config:

[client]
remote_addr = "MY_DOMAIN:28888"

[client.services.outgoing]
token = "isGaDvTQBHYdXPr6"
local_addr = "192.168.50.252:80"

server config is lost, but it looked like the example, then ran and got error.

fernvenue commented 8 months ago

@SakaZhang You may need to reproduce this issue then provide the configuration file.

sunmy2019 commented 7 months ago

You guys just keep saying that you all experiencing this, but no one provide any configuration example or useful information, what a joke.

Don't be so rude. I am able to reproduce issue with the default configuration. Configuration file is the least important thing here.

The cause is simple and clear.

Just as the message itself indicated, someone else is sending invalid bytes into that port. It is an error that should be ignored.

engAmirEng commented 4 months ago

In my case this error happens when I use cloudflare proxied domain

[server]
bind_addr = "0.0.0.0:2053"

[server.services.my_custom]
token = "use_a_secret_that_only_you_know"
bind_addr = "0.0.0.0:443"

[server.transport]
type = "tls"

[server.transport.tls]
pkcs12 = "file.pfx"
pkcs12_password = "passwd"

[client]
remote_addr = "my.domain.com:2053"

[client.transport]
type = "tls"

[client.transport.tls]
trusted_root = "/etc/ssl/certs/ca-certificates.crt"

[client.services.my_custom]
token = "use_a_secret_that_only_you_know"
local_addr = "127.0.0.1:443"

my.domain.com is behind cloudflare proxy