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

[Bug]: EOF in nekobepass #42

Open
radiumatic opened this issue Sep 25, 2023 · 2 comments
Open

[Bug]: EOF in nekobepass #42

radiumatic opened this issue Sep 25, 2023 · 2 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@radiumatic
Copy link

Any connection simply gets closed, yielding no errors or warnings.

Using the default configuration or a custom DoH server does not seem to have any effects.

Based on the (rather) short conversation that you had on twitter, It seems like bepass does not check for the "use worker" value, tries to validate a nonexistent worker address, and fails.

This also shows that logs need to be a bit more expressive. 🤔

@uoosef uoosef added bug Something isn't working enhancement New feature or request labels Sep 27, 2023
@uoosef
Copy link
Contributor

uoosef commented Sep 27, 2023

It maybe because your worker address is wrong please double check it that you followed this specific format:
https://<worker_name>.<user_name>.workers.dev/dns-query
many of issues are becuase ppl forget to add https or 's' in workers.dev or adding '/dns-query' trailing...
i will make it more simpler and provide some autofixes in v2 to improve ux and simpilicity

@radiumatic
Copy link
Author

It maybe because your worker address is wrong please double check it that you followed this specific format:
https://<worker_name>.<user_name>.workers.dev/dns-query
many of issues are becuase ppl forget to add https or 's' in workers.dev or adding '/dns-query' trailing...
i will make it more simpler and provide some autofixes in v2 to improve ux and simpilicity

I'm not using a worker. (The config value is empty) As I have already said, my guess is that bepass tries to validate/use the worker even if use-worker option is set to false.

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

No branches or pull requests

2 participants