Replies: 1 comment
-
Most likely, this is a bug. The gateway does not need it at all. There are a few mishandled errors on the gateway side that I have plans to address at #21. However, the likelihood of encountering these errors is very low; they may only occur on extremely unstable networks. In any case, I have given the highest priority to addressing such issues. I'm going to check the code more carefully. If you set this environment variable on both the client and gateway sides, you can get more logs that would be very helpful for me. RUST_LOG=narrowlink,narrowlink_gateway,narrowlink_types,narrowlink_network=trace like: export RUST_LOG=narrowlink,narrowlink_gateway,narrowlink_types,narrowlink_network=trace
narrowlink-gateway > logs.txt or RUST_LOG=narrowlink,narrowlink_gateway,narrowlink_types,narrowlink_network=trace ./narrowlink-gateway > logs.txt |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am not sure this is a bug so just bring up in Discussions.
I found I can't connect after 2 days not use, getting this error:
So I restarted the Agent and Client, but still not working.
So I restarted Gateway and Client again, that starts to work.
I am not sure why I need to restart gateway? Any idea? :-)
Beta Was this translation helpful? Give feedback.
All reactions