Can't Configure Chrome Remote Desktop
I'm trying to use Chrome Remote Desktop to access my machine from a Mac. When I try the "enable remote connections" step it tries for a while then times out with error "failed to start remote access service." If I close the window, then my machine shows up and says "(last online 3:49:58 PM)" where the time is the time I attempted to start the service.
I've tried reinstalling chrome and chrome remote desktop and following the instructions in this question. I can connect to my computer through the "remote assistance," and I can connect to my Mac from my linux machine. Any other ideas?
google-chrome remote-desktop
add a comment |
I'm trying to use Chrome Remote Desktop to access my machine from a Mac. When I try the "enable remote connections" step it tries for a while then times out with error "failed to start remote access service." If I close the window, then my machine shows up and says "(last online 3:49:58 PM)" where the time is the time I attempted to start the service.
I've tried reinstalling chrome and chrome remote desktop and following the instructions in this question. I can connect to my computer through the "remote assistance," and I can connect to my Mac from my linux machine. Any other ideas?
google-chrome remote-desktop
What is your Ubuntu release? I tested with Lubuntu 17.04, it seems running fine. I followed instructions here at this page
– Redbob
Oct 5 '17 at 23:47
I'm in 16.04 LTS. I tried following those instructions and got the same error. I think it might be something unique to my machine or google chrome profile. Sometimes when trying to set it up I get the message that the machine is registered to another chrome user, and then I delete the machine and can try again.
– jswien
Oct 6 '17 at 0:03
The profile issue is a valid suggestion. Try to do this: close google-chrome, rename~/.config/google-chrome
folder and restart google-chrome, redo configuration. You will not need to reinstall deb and linux files, I think.
– Redbob
Oct 6 '17 at 0:13
add a comment |
I'm trying to use Chrome Remote Desktop to access my machine from a Mac. When I try the "enable remote connections" step it tries for a while then times out with error "failed to start remote access service." If I close the window, then my machine shows up and says "(last online 3:49:58 PM)" where the time is the time I attempted to start the service.
I've tried reinstalling chrome and chrome remote desktop and following the instructions in this question. I can connect to my computer through the "remote assistance," and I can connect to my Mac from my linux machine. Any other ideas?
google-chrome remote-desktop
I'm trying to use Chrome Remote Desktop to access my machine from a Mac. When I try the "enable remote connections" step it tries for a while then times out with error "failed to start remote access service." If I close the window, then my machine shows up and says "(last online 3:49:58 PM)" where the time is the time I attempted to start the service.
I've tried reinstalling chrome and chrome remote desktop and following the instructions in this question. I can connect to my computer through the "remote assistance," and I can connect to my Mac from my linux machine. Any other ideas?
google-chrome remote-desktop
google-chrome remote-desktop
asked Oct 5 '17 at 23:03
jswienjswien
10115
10115
What is your Ubuntu release? I tested with Lubuntu 17.04, it seems running fine. I followed instructions here at this page
– Redbob
Oct 5 '17 at 23:47
I'm in 16.04 LTS. I tried following those instructions and got the same error. I think it might be something unique to my machine or google chrome profile. Sometimes when trying to set it up I get the message that the machine is registered to another chrome user, and then I delete the machine and can try again.
– jswien
Oct 6 '17 at 0:03
The profile issue is a valid suggestion. Try to do this: close google-chrome, rename~/.config/google-chrome
folder and restart google-chrome, redo configuration. You will not need to reinstall deb and linux files, I think.
– Redbob
Oct 6 '17 at 0:13
add a comment |
What is your Ubuntu release? I tested with Lubuntu 17.04, it seems running fine. I followed instructions here at this page
– Redbob
Oct 5 '17 at 23:47
I'm in 16.04 LTS. I tried following those instructions and got the same error. I think it might be something unique to my machine or google chrome profile. Sometimes when trying to set it up I get the message that the machine is registered to another chrome user, and then I delete the machine and can try again.
– jswien
Oct 6 '17 at 0:03
The profile issue is a valid suggestion. Try to do this: close google-chrome, rename~/.config/google-chrome
folder and restart google-chrome, redo configuration. You will not need to reinstall deb and linux files, I think.
– Redbob
Oct 6 '17 at 0:13
What is your Ubuntu release? I tested with Lubuntu 17.04, it seems running fine. I followed instructions here at this page
– Redbob
Oct 5 '17 at 23:47
What is your Ubuntu release? I tested with Lubuntu 17.04, it seems running fine. I followed instructions here at this page
– Redbob
Oct 5 '17 at 23:47
I'm in 16.04 LTS. I tried following those instructions and got the same error. I think it might be something unique to my machine or google chrome profile. Sometimes when trying to set it up I get the message that the machine is registered to another chrome user, and then I delete the machine and can try again.
– jswien
Oct 6 '17 at 0:03
I'm in 16.04 LTS. I tried following those instructions and got the same error. I think it might be something unique to my machine or google chrome profile. Sometimes when trying to set it up I get the message that the machine is registered to another chrome user, and then I delete the machine and can try again.
– jswien
Oct 6 '17 at 0:03
The profile issue is a valid suggestion. Try to do this: close google-chrome, rename
~/.config/google-chrome
folder and restart google-chrome, redo configuration. You will not need to reinstall deb and linux files, I think.– Redbob
Oct 6 '17 at 0:13
The profile issue is a valid suggestion. Try to do this: close google-chrome, rename
~/.config/google-chrome
folder and restart google-chrome, redo configuration. You will not need to reinstall deb and linux files, I think.– Redbob
Oct 6 '17 at 0:13
add a comment |
2 Answers
2
active
oldest
votes
I think I figured out what was going on. First I deleted my chrome remote desktop installation and all config files associated with google chrome. Then I reinstalled, and followed these edits here so I could remote in to the current session. It worked for about 24 hours, then it failed to connect after that.
So I deleted everything again, and reinstalled without configuring it to connect to the current session. It has been working fine now. In short, you used to be able to edit the code to connect to the current session, but with the recent update this now causes errors.
add a comment |
The Chromium-browser and Chrome are probably different browsers. Probably, Google cannot give some tokens to the Chromium. Because of the reason, you can carry on the following steps for using chrome-remote-desktop on ubuntu.
After this installation, two chrome application is available on your computer. The real one is red-green-yellow colored.
It is tried and worked on my Ubuntu 18.04.1 LTS desktop.
Just install real Chrome from https://www.google.com/chrome/browser/desktop/. Then install it in your computer.Download Chrome Remote Desktop from https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb or from the google official site.Then install it in your computer.
Add Chrome Remote Desktop extension to the Chrome (the real one)
Login to the google by your google account.
- Launch the Chrome Remote Desktop Application from the extension or in the ubuntu application launcher.
Thats All, Enjoy.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f962368%2fcant-configure-chrome-remote-desktop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think I figured out what was going on. First I deleted my chrome remote desktop installation and all config files associated with google chrome. Then I reinstalled, and followed these edits here so I could remote in to the current session. It worked for about 24 hours, then it failed to connect after that.
So I deleted everything again, and reinstalled without configuring it to connect to the current session. It has been working fine now. In short, you used to be able to edit the code to connect to the current session, but with the recent update this now causes errors.
add a comment |
I think I figured out what was going on. First I deleted my chrome remote desktop installation and all config files associated with google chrome. Then I reinstalled, and followed these edits here so I could remote in to the current session. It worked for about 24 hours, then it failed to connect after that.
So I deleted everything again, and reinstalled without configuring it to connect to the current session. It has been working fine now. In short, you used to be able to edit the code to connect to the current session, but with the recent update this now causes errors.
add a comment |
I think I figured out what was going on. First I deleted my chrome remote desktop installation and all config files associated with google chrome. Then I reinstalled, and followed these edits here so I could remote in to the current session. It worked for about 24 hours, then it failed to connect after that.
So I deleted everything again, and reinstalled without configuring it to connect to the current session. It has been working fine now. In short, you used to be able to edit the code to connect to the current session, but with the recent update this now causes errors.
I think I figured out what was going on. First I deleted my chrome remote desktop installation and all config files associated with google chrome. Then I reinstalled, and followed these edits here so I could remote in to the current session. It worked for about 24 hours, then it failed to connect after that.
So I deleted everything again, and reinstalled without configuring it to connect to the current session. It has been working fine now. In short, you used to be able to edit the code to connect to the current session, but with the recent update this now causes errors.
answered Oct 20 '17 at 0:39
jswienjswien
10115
10115
add a comment |
add a comment |
The Chromium-browser and Chrome are probably different browsers. Probably, Google cannot give some tokens to the Chromium. Because of the reason, you can carry on the following steps for using chrome-remote-desktop on ubuntu.
After this installation, two chrome application is available on your computer. The real one is red-green-yellow colored.
It is tried and worked on my Ubuntu 18.04.1 LTS desktop.
Just install real Chrome from https://www.google.com/chrome/browser/desktop/. Then install it in your computer.Download Chrome Remote Desktop from https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb or from the google official site.Then install it in your computer.
Add Chrome Remote Desktop extension to the Chrome (the real one)
Login to the google by your google account.
- Launch the Chrome Remote Desktop Application from the extension or in the ubuntu application launcher.
Thats All, Enjoy.
New contributor
add a comment |
The Chromium-browser and Chrome are probably different browsers. Probably, Google cannot give some tokens to the Chromium. Because of the reason, you can carry on the following steps for using chrome-remote-desktop on ubuntu.
After this installation, two chrome application is available on your computer. The real one is red-green-yellow colored.
It is tried and worked on my Ubuntu 18.04.1 LTS desktop.
Just install real Chrome from https://www.google.com/chrome/browser/desktop/. Then install it in your computer.Download Chrome Remote Desktop from https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb or from the google official site.Then install it in your computer.
Add Chrome Remote Desktop extension to the Chrome (the real one)
Login to the google by your google account.
- Launch the Chrome Remote Desktop Application from the extension or in the ubuntu application launcher.
Thats All, Enjoy.
New contributor
add a comment |
The Chromium-browser and Chrome are probably different browsers. Probably, Google cannot give some tokens to the Chromium. Because of the reason, you can carry on the following steps for using chrome-remote-desktop on ubuntu.
After this installation, two chrome application is available on your computer. The real one is red-green-yellow colored.
It is tried and worked on my Ubuntu 18.04.1 LTS desktop.
Just install real Chrome from https://www.google.com/chrome/browser/desktop/. Then install it in your computer.Download Chrome Remote Desktop from https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb or from the google official site.Then install it in your computer.
Add Chrome Remote Desktop extension to the Chrome (the real one)
Login to the google by your google account.
- Launch the Chrome Remote Desktop Application from the extension or in the ubuntu application launcher.
Thats All, Enjoy.
New contributor
The Chromium-browser and Chrome are probably different browsers. Probably, Google cannot give some tokens to the Chromium. Because of the reason, you can carry on the following steps for using chrome-remote-desktop on ubuntu.
After this installation, two chrome application is available on your computer. The real one is red-green-yellow colored.
It is tried and worked on my Ubuntu 18.04.1 LTS desktop.
Just install real Chrome from https://www.google.com/chrome/browser/desktop/. Then install it in your computer.Download Chrome Remote Desktop from https://dl.google.com/linux/direct/chrome-remote-desktop_current_amd64.deb or from the google official site.Then install it in your computer.
Add Chrome Remote Desktop extension to the Chrome (the real one)
Login to the google by your google account.
- Launch the Chrome Remote Desktop Application from the extension or in the ubuntu application launcher.
Thats All, Enjoy.
New contributor
New contributor
answered Jan 14 at 16:03
nukecorenukecore
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f962368%2fcant-configure-chrome-remote-desktop%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is your Ubuntu release? I tested with Lubuntu 17.04, it seems running fine. I followed instructions here at this page
– Redbob
Oct 5 '17 at 23:47
I'm in 16.04 LTS. I tried following those instructions and got the same error. I think it might be something unique to my machine or google chrome profile. Sometimes when trying to set it up I get the message that the machine is registered to another chrome user, and then I delete the machine and can try again.
– jswien
Oct 6 '17 at 0:03
The profile issue is a valid suggestion. Try to do this: close google-chrome, rename
~/.config/google-chrome
folder and restart google-chrome, redo configuration. You will not need to reinstall deb and linux files, I think.– Redbob
Oct 6 '17 at 0:13