Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
passwa11 opened this issue Nov 20, 2023 · 9 comments
Labels
bug Something isn't working

Comments

@passwa11
Copy link

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

@passwa11 passwa11 added the bug Something isn't working label Nov 20, 2023
@fernvenue
Copy link
Contributor

Hi, could you please provide your configuration file?

@SakaZhang
Copy link

i got same prob.

@fernvenue
Copy link
Contributor

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

@fernvenue
Copy link
Contributor

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

@bfshires
Copy link

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
Copy link

SakaZhang commented Jan 18, 2024

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
Copy link
Contributor

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

@sunmy2019
Copy link
Contributor

sunmy2019 commented Feb 15, 2024

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants