You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. 🤔
The text was updated successfully, but these errors were encountered:
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
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.
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. 🤔
The text was updated successfully, but these errors were encountered: