Scheduled maintenance: Thursday, September 24, between 11:30am and 13:30pm UTC. This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn’t solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter

搜尋 Mozilla 技術支援網站

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

https://remotedesktop.google.com/access doesn't work with FF68

  • 14 回覆
  • 1 有這個問題
  • 3282 次檢視
  • 最近回覆由 McCoy

more options

Chrome Remote Desktop (https://remotedesktop.google.com/access) doesn't work with FF68 on MacOS. It's been working lovely thus far. Lot's of users are having the same issue: https://www.reddit.com/r/firefox/comments/ceg19l/google_remote_desktop_error/

What's up?

被選擇的解決方法

Suddenly after a week of rest this issue has disappeared! The Chrome Remote Desktop service is working with FF. Hard to guess what's changed, but probably Google changed something since I'm using the same FF version.

從原來的回覆中察看解決方案 👍 0

所有回覆 (14)

more options

Please explain the problem in detail. What happens? What are the exact error message(s) ?

more options

It shows the remote desktop for 1 second, then kills the connection with the error message: "The remote computer is not responding to connection requests. Please verify that it is online and try again."

In the Reddit thread there are others experiencing in the exact same way, and with no improvements after removing/reinstalling Chrome Remote Desktop. It works flawlessly through Google Chrome – so there might be a conspiracy theory that Google has somehow managed to block non-Google browsers...

more options

I had no problem using the link.

Make sure you are not blocking content.

Start Firefox in Safe Mode {web link}

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?


One issue that seems more common lately is Firefox's Content Blocking. When it is blocking content in a page, a shield icon will appear at the left end of the address bar next to the padlock icon. This article has more info on managing this feature:

https://support.mozilla.org/en-US/kb/content-blocking

more options

Hi Miko, could you test in the Developer Edition? It can install side-by-side with the standard release and contains the changes already approved for Firefox 69. If this problem was accidentally fixed in the course of fixing something else, that would save a lot of time trying to track down which of the hundreds of changes in Firefox 68 caused the issue.

https://www.mozilla.org/firefox/developer/all/

more options

Hello Miko,

Just in case none of the above should do the trick; would you please check this :

Type in the address bar about:config and press Enter (promise to be careful, if asked)

Type in the search bar and look for the preference :

media.peerconnection.enabled

and make sure its value is set to true

If you had to change the value, then close and restart Firefox.


Maybe the last post in that Reddit thread might be worth considering though ......

more options

The link works but the service of connecting to a remote desktop (through the Chrome Remote Desktop service) doesn't. It's not a problem of link not working, but rather a question of the remote desktop streaming being erroneously shut down.

Unfortunately Safe Mode didn't change anything.

FredMcD said

I had no problem using the link. Start Firefox in Safe Mode {web link}
more options

I tried installing the Firefox Developer Edition, and unfortunately the issue persists.

jscher2000 said

Hi Miko, could you test in the Developer Edition?
more options

The preference was set to "true" and unfortunately switching on/off doesn't change anything.

McCoy said

Type in the search bar and look for the preference : media.peerconnection.enabled and make sure its value is set to true
more options

Miko said

The preference was set to "true" and unfortunately switching on/off doesn't change anything.

Bummer - but thank you for trying, though.

This won't help, but here it's the other way around :

https://support.google.com/chrome/thread/9440790?hl=en


If everything else fails, would this be an option for you (?) :

https://www.connectwise.com/software/control

(see the last post in that Reddit thread)

more options

Miko said

I tried installing the Firefox Developer Edition, and unfortunately the issue persists.

Thank you for testing that.

The next step is the difficult one: finding the specific code check-in that caused the changed behavior. This often takes a good deal of time because you have to login in and test over and over and over with different builds. I'm not sure how to do it on Mac (there isn't a compiled GUI version of https://mozilla.github.io/mozregression/ for Mac).

If you file a bug, maybe someone can help with that.

more options

The website states that it WebRTC, so maybe check for issues with WebRTC.

Did you already check the Web Console?

more options

cor-el said

The website states that it WebRTC, so maybe check for issues with WebRTC.

https://webrtc.org/troubleshooting/

more options

選擇的解決方法

Suddenly after a week of rest this issue has disappeared! The Chrome Remote Desktop service is working with FF. Hard to guess what's changed, but probably Google changed something since I'm using the same FF version.

more options

Miko said

Suddenly after a week of rest this issue has disappeared! The Chrome Remote Desktop service is working with FF. Hard to guess what's changed, but probably Google changed something since I'm using the same FF version.

That's good news - thank you for letting us know.

Would you please mark your own last post as Chosen Solution  ? ("Solved the problem" button to the right of that post)