You get a separate clean session.įrom this, you can launch chrome and log into the Web interface of your NAS just as you would from any PC on your LAN or from MyQNAPCloud. Note that the XWindows session launched is not the same as the one your using when you log into the Web GUI of Ubuntu. Once everything runs as it should, its time to test it from a remote PC using Chrome with the CRD client installed. ![]() If you get the "Failed to start remote access service" you must go back into command line and try to stop and start the CRD server again. This is where you configure the access code and pin code. Then you go back to Chrome, and into App Store to download the CRD client. Cleaning, rebuilding, updating, upgrading and fetching dependencies turned out to be the the solution for me, before I finally made it run succesfully. I had a lot of trouble with it refusing to run becuase it was unable to build a working config file. It is important that you make sure it does start and run properly. Pay close attention to the console output. Then it is important to clean up and get rid of unused libraries and services Where is the name of the deb file you just downloaded.Īgain, it will be likely to complain about dependencies not present, so you probably have to run again:Īnd then install CRD one more time like you just did above. Then, as soon as that is set and done, search for the Linux Debian package of Chrome Remote Desktop and download it. ![]() (If you do not have a Google account, now is a good time to create one). It is important that you log in to Google using your Google account. You should find it from your "start" button in Ubuntu, but if it's not there, you'll find it under: Now that you have chrome installed, it is a good time to launch and test it. Then it is time to install Chrome Remote Desktop server (CRD). You solve this by typing:įollowed by another re-install of the chrome package again (just as you did above). Where is the name of the file you just downloaded from Google.ĭuring installation, it will most likely throw a lot of missing dependencies at you. Once downloaded, install it from command line using: Then launch Firefox from Ubuntu and goto where you search for Chrome download. If everything is ok then the first thing to do is to update and upgrade So it is important to test this as soon as the container is up and running the first time. You will have to delete the whole container and start all over again. If your forget it now, or do it wrong, then I know of no way to change this later. If you only need to have an easy transport of data in/out of the contianer, then a path to your Public folder is enough, but if you want to have full root folder access, then now is the time to set it up. This also must be done in the Advanced Setting -> Shared Folder during first time set up. You do this under Advanced Setting -> Network during first time setup.Īlso, it is important to map a path to your QTS so that Ubuntu can easily stretch an arm and a leg out of the container and reach your QTS folder structure. ![]() If you choose NAT, the container gets a new port each time you boot, and it becomes difficult to connect. I chose the docker-ubuntu-vnc-desktop image named "Ubuntu desktop with noVNC" in the CS repository.ĭuring installation, it is important to choose host networking instead of NAT in order to let the container have access to your LAN subnet directly. ![]() However, my next idea was to install Ubuntu in Container station and then attempt to make CRD run from there. (If you have any idea, let the community know) I talked to a couple of the chromium developers, but they could not help me. Eventually, I traced the problem down to PAM Authentication failure, see this link: I tried for some time to install and run CRD under Linux Station, but it failed persistantly when I tried to connect from a remote client with an "Invalid Key" error. Perhaps the easies way is to configure a Windows PC on the same LAN and use it as a front end, but that in turn requires yet another computer to run 24/7 probably also with UPS to be on the safe side.Īs far as I know, there is no way to install and run CRD in QTS either as a QPKG or from Entware as OPKG. In theory, it should be easy to set up and configure, but in practice it can be quite challenging. If you want full access to your NAS without the need to open any ports in your WAN router, while still maintaining encryption and security, Chrome Remote Desktop is a wonderful tool. However, the cloudlink service only gets you into QTS without any SSH or FTP or much of anything, and is not offered with a 24/7 guarantee. It requires no firewall opening or port forward, and can easily be secured using private or public sertifactes (SSL) Access NAS using Chrome Remote Desktop (CRD)Īn easy (and secure) way to remotely access a QNAP NAS is to use MyQNAPCloud Cloudlink service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |