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
Whenever the SQL table countries in the server is changed, our Dart script shall receive an update, but because of the bug, it doesn't. There is no WebSocket connection between our client app and the .onion server providing Supabase.
Version (please complete the following information):
On Linux/macOS
According to Tor Project: FAQ | Tor onion services: How do I access onion services?, the client shan't lookup .onion address. Please note that the top-level domain is .onion. It will doom to fail to lookup .onion address, because .onion is only recognizable by Tor Network. The client shall simply pass the .onion address to Tor proxy without looking up the .onion address in advance.
When running the above code example that reproduces the bug, it will throw this exception:
SocketException (SocketException: Failed host lookup: 'your_onion_address.onion' (OS Error: Name or service not known, errno = -2))
The callstack of the DNS lookup that causes the exception is as follows:
There is no way to pass a HttpClient to WebSocketChannel like what we can do to SupabaseClient, but defining HttpOverrides.createHttpClient and running all Supabase code in a HttpOverrides.runZoned is a workaround.
Describe the bug
Unable to create a WebSocket connection to access Realtime on an .onion server.
To Reproduce
Expected behavior
Whenever the SQL table
countries
in the server is changed, our Dart script shall receive an update, but because of the bug, it doesn't. There is no WebSocket connection between our client app and the .onion server providing Supabase.Version (please complete the following information):
On Linux/macOS
Additional context
According to Tor Project: FAQ | Tor onion services: How do I access onion services?, the client shan't lookup .onion address. Please note that the top-level domain is
.onion
. It will doom to fail to lookup .onion address, because .onion is only recognizable by Tor Network. The client shall simply pass the .onion address to Tor proxy without looking up the .onion address in advance.When running the above code example that reproduces the bug, it will throw this exception:
The callstack of the DNS lookup that causes the exception is as follows:
The text was updated successfully, but these errors were encountered: