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

Connection dies after a while when deploying on fly.io #306

Open
tagener-noisu opened this issue Nov 11, 2023 · 0 comments
Open

Connection dies after a while when deploying on fly.io #306

tagener-noisu opened this issue Nov 11, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@tagener-noisu
Copy link

Describe the bug

I've encountered a weird behavior when I deployed on fly.io. The connection works fine at first, but then the webserver stops responding. If I test the same containers on a local machine everything works fine and there are no error messages in the logs. I feel like fly change the connection somehow, but I don't know how to ask about it on their forums. Can you describe what do those error messages mean?

To Reproduce
Steps to reproduce the behavior:

  1. Create Dockerfile
FROM rapiz1/rathole
COPY ./config.toml /app/config.toml
CMD ["--server", "/app/config.toml"]
  1. Deploy on fly.io

Configuration
Configuration used to reproduce the behavior:

Server:

[server]
bind_addr = "0.0.0.0:7003"

[server.services.webserver]
token = "TOKEN HERE"
bind_addr = "0.0.0.0:8080"

Client:

[client]
remote_addr = "tnoisu.fly.dev:7003"

[client.services.webserver]
token = "TOKEN HERE"
local_addr = "libreddit:8080"

Logs

Client logs:

client_1     | 2023-11-11T00:35:34.432314Z  INFO config_watcher{path="/app/config.toml"}: rathole::config_watcher: Start watching the config
client_1     | 2023-11-11T00:35:34.995333Z  INFO handle{service=webserver}:run: rathole::client: Control channel established
client_1     | 2023-11-11T00:35:35.264566Z  WARN handle{service=webserver}:run: rathole::client: Failed to run the data channel: Failed to read cmd: early eof
client_1     | 2023-11-11T00:35:35.265458Z  WARN handle{service=webserver}:run: rathole::client: Failed to run the data channel: Failed to read cmd: early eof
client_1     | 2023-11-11T00:35:35.265672Z  WARN handle{service=webserver}:run: rathole::client: Failed to run the data channel: Failed to read cmd: early eof

Server logs:

Nov 11 00:35:35.442 WARN connection{addr=172.16.159.90:38538}: rathole::server: Data channel has incorrect nonce
Nov 11 00:35:35.447 WARN connection{addr=172.16.159.90:38544}: rathole::server: Data channel has incorrect nonce
Nov 11 00:35:35.447 WARN connection{addr=172.16.159.90:38546}: rathole::server: Data channel has incorrect nonce 

Environment:

  • OS: latest image from Docker hub. I also tried v0.4.1
  • rathole --version output:
rathole
Build Timestamp:     2023-10-01T10:08:07.162273634Z
Build Version:       0.5.0
Commit SHA:          None
Commit Date:         None
Commit Branch:       None
cargo Target Triple: x86_64-unknown-linux-gnu
cargo Profile:       release
cargo Features:      base64,client,default,futures_core,futures_sink,hot_reload,noise,notify,server,snowstorm,tls,tokio_native_tls,tokio_tungstenite,tokio_util,websocket
  • CPU architecture: x64
@tagener-noisu tagener-noisu added the bug Something isn't working label Nov 11, 2023
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

1 participant