-
Notifications
You must be signed in to change notification settings - Fork 316
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
No longer works in Firefox Nightly #622
Comments
OK, the admin interface is returning 403 Forbidden. The difference between Chrome and Firefox is that Firefox appends a |
Thank you for reporting! Interesting. This is basically Firefox version of #615 (which we fixed in #616). In short, Chrome was adding Seems that Firefox Nightly started setting |
Heads up: I’d expect this behavior to change in Firefox. The internal UUID they send is unique and persistent per installation. It would allow for user tracking. Edit: upstream issue. |
Correction: it’s been like this for a year according to bugz#1405971. I’m not sure why this issue only started affecting IPFS now. |
@da2x shipped a fix in v2.6.1.12130 (Beta), give it a try! :) |
Works for me. |
The IPFS Companion stopped working one–three weeks ago in Firefox Nightly.
It can’t connect to IPFS Desktop anymore. IPFS is listening on the expected ports, however. IPFS Companion still works in Chromium.
I’ve tried reinstalling IPFS Companion and have tested with older versions all the way back to 2.4.0.
Confirmed issue on Firefox Nightly on macOS 10.14 and Windows 10.1809.
The text was updated successfully, but these errors were encountered: