Open jagjordi opened 1 year ago
What's the bridge status reported on the options page? Are you sure the daemon is configured and running properly?
Are there any other logs in browser/extension consoles? I assume that's output from the web console for the YouTube page, but that's just the init logs for the YouTube app.
The bridge status is "found"
I can see now that the bridge connection failed, and it says that the backup is not enabled. I will check why that is happening and report back!
The backup was disabled since I had reinstalled the extension, now I enabled it again and I see some new error messages:
stderr output from native app fx_cast_bridge: *** WARNING *** The program 'fx_cast_bridge' uses the Apple Bonjour compatibility layer of Avahi.
stderr output from native app fx_cast_bridge: *** WARNING *** Please fix your application to use the native API of Avahi!
stderr output from native app fx_cast_bridge: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
stderr output from native app fx_cast_bridge: *** WARNING *** The program 'fx_cast_bridge' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
stderr output from native app fx_cast_bridge: *** WARNING *** Please fix your application to use the native API of Avahi!
stderr output from native app fx_cast_bridge: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
stderr output from native app fx_cast_bridge: *** WARNING *** The program 'fx_cast_bridge' uses the Apple Bonjour compatibility layer of Avahi.
stderr output from native app fx_cast_bridge: *** WARNING *** Please fix your application to use the native API of Avahi!
stderr output from native app fx_cast_bridge: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
stderr output from native app fx_cast_bridge: *** WARNING *** The program 'fx_cast_bridge' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
stderr output from native app fx_cast_bridge: *** WARNING *** Please fix your application to use the native API of Avahi!
stderr output from native app fx_cast_bridge: *** WARNING *** For more information see <http://0pointer.de/blog/projects/avahi-compat.html>
stderr output from native app fx_cast_bridge: node:internal/process/promises:279
stderr output from native app fx_cast_bridge: triggerUncaughtException(err, true /* fromPromise */);
stderr output from native app fx_cast_bridge: ^
stderr output from native app fx_cast_bridge:
stderr output from native app fx_cast_bridge: Error: connect EHOSTUNREACH 192.168.1.104:8009
stderr output from native app fx_cast_bridge: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
stderr output from native app fx_cast_bridge: errno: -113,
stderr output from native app fx_cast_bridge: code: 'EHOSTUNREACH',
stderr output from native app fx_cast_bridge: syscall: 'connect',
stderr output from native app fx_cast_bridge: address: '192.168.1.104',
stderr output from native app fx_cast_bridge: port: 8009
stderr output from native app fx_cast_bridge: }
Any idea on what is the cause?
Looks like some sort of network configuration issue. Is that address (192.168.1.104
) reachable if you ping it?
FWIW I saw the same behavior with this in the logs. However, turning on the backup daemon connection resolved the issue.
fx_cast (Info): init [background.js:1:31810](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Info): checking for bridge... [background.js:1:31810](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Info): ... bridge compatible! [background.js:1:31810](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Info): init (action) [background.js:1:31810](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Info): init (menus) [background.js:1:31810](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Info): init (whitelist) [background.js:1:31810](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast_bridge disconnected: <empty string> [background.js:1:36538](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Error): Bridge connection failed and backup not enabled. [background.js:1:31987](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast_bridge disconnected: <empty string> [background.js:1:36538](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Error): Bridge connection failed and backup not enabled. [background.js:1:31987](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast_bridge disconnected: <empty string> [background.js:1:36538](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
fx_cast (Error): Bridge connection failed and backup not enabled. [background.js:1:31987](moz-extension://ab38c5f5-2368-4f9f-94c8-af964b28f0b2/background/background.js)
I'm also having this issue. What is the "backup daemon" and how do I turn it on?
I'm also having this issue. What is the "backup daemon" and how do I turn it on?
@chandywerks I don't know how it's different but I found the setting in the Add-on preferences.
FWIW, I got this error and resolved it by disconnecting from my VPN while device discovery was running. After my TV was found, it works after reconnecting to the VPN.
I changed to backup, then saved, then un-selected it, and noticed the error message disappeared. So perhaps it just needed a configuration change. (This just mentioned for information, that's all.)
The Refresh Bridge Status
button in the setting page does not test the current settings.
It tests the last saved settings. This means you have to scroll down and click save
before the Refresh Bridge Status
button does anything useful.
This is confusing and just costed me about an hour to find out.
Apart from that, simply enabling the backup daemon connection
without changing any setting did the job for me.
This should really be enabled by default.
OS version: Fedora 37 Browser version: Firefox 108.0 Extension version: 0.3.1 Bridge version: 0.3.0
Description When trying to cast the following message appears
Steps to reproduce
Expected behaviour Casting works and available devices appears
Logs Provide any applicable logs here. Info on where to find them is located here.