I have an Amazon ec2 instance in which I can login through putty. I want GUI on that instance. Please anyone help me, how can I get GUI on ec2 instance.
Install VNC and connect using VNC. View the video here.
You can also use an X11 server like MobaXTerm: http://mobaxterm.mobatek.net/ ot Xming: http://sourceforge.net/projects/xming/ (assuming you work on a PC running Windows).
login ec2 instance and execute below commands
Sudo apt-get update
Sudo apt-get install lxde
sudo start lxdm
sudo apt-get install xrdp
sudo passwd ubuntu
then open RDC
username -- hostname which you provided in putty
Related
I've installed Centos7 on the Google Cloud Platform, as you know there is just ssh option to connect to the machine.
Now I need to have access to its desktop(GUI) from my laptop (it's win10).
it's appreciated if anyone can help me.
Thanks in advance
you need to ssh login into your CentOS machine either from ssh button in Gcloud, or using the cloud shell:
gcloud compute ssh test-vws
then setup a password for your account:
sudo passwd `whoami`
After that, you will need to install a client that will allow you to navigate the GUI for your server.
again, on your server command line execute:
sudo yum -y update
sudo yum -y groupinstall 'Server with GUI'
once finished, follow this guige to install and setup Teradici Cloud Access Software (Remote Desktop Agent for CentOS).
Installing Teradici Cloud Access Software
On your virtual workstation, install the Teradici repositories:
sudo yum -y install https://downloads.teradici.com/rhel/teradici-repo-latest.noarch.rpm
Install Teradici Standard Agent for Linux:
sudo yum -y update
sudo yum -y install pcoip-agent-standard
Then you will have to register the Agent and create a firewall rule to allow the connection, just follow the guide, and your desktop connection will look like this:
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I have used an instance with ubuntu-server of AWS and would like to use GUI either so I did the following operations referring,
https://aws.amazon.com/premiumsupport/knowledge-center/connect-to-linux-desktop-from-windows/
How To Set Up GUI On Amazon EC2 Ubuntu server
It could be summarized as following.
a) Installed ubuntu-desktop and vnc4server
b) Changed the security settings in AWS console to open the ports 5901, 5902
c) Changed the security settings in my computer to open the ports for outbounding
However, connecting to the ubuntu it works but I could see only the screen full with a gray color.
What should I do further?
Boot up EC2 - Ubuntu 14.04 (LTS)
Once the instance is all boot up, update it:
sudo apt-get update
sudo apt-get upgrade
sudo vim /etc/ssh/sshd_config
Change PasswordAuthentication no to PasswordAuthentication yes
Restart SSH: sudo /etc/init.d/ssh restart OR sudo /etc/init.d/sshd restart
Go into root: sudo -i
Set password for ubuntu: passwd ubuntu
Once you've finished setting your password, go back to ubuntu user: su ubuntu & cd
Install Ubuntu desktop functionality:
export DEBIAN_FRONTEND=noninteractive
sudo -E apt-get update
sudo -E apt-get install -y ubuntu-desktop
Install XRDP and XFCE4:
sudo apt-get install xfce4 xrdp
sudo apt-get install xfce4 xfce4-goodies
Make XFCE4 the default for RDP connections:
echo xfce4-session > ~/.xsession
Copy .xsession to the /etc/skel folder so xfce4 is set as the default window manager for any new user accounts that are created.
sudo cp /home/ubuntu/.xsession /etc/skel
Allow host port to connect to xrdp.ini:
sudo vim /etc/xrdp/xrdp.ini
Change port=-1 to port=ask-1
Restart xrdp:
sudo service xrdp restart
Go back to AWS and make sure your security group includes inbound access to RDP 3389
Go into Microsoft Remote Desktop, type in your IP address with: XX.XX.XXX.XX:3389
Check this link - and this Untested but Solutions to 14.x to 15.x:
Update/upgrade with:
sudo do apt-get update
sudo apt-get dist-upgrade
sudo do-release-upgrade
Make it short and simple:
apt-get update –y
apt-get upgrade –y
apt-get install ubuntu-desktop xfce4 firefox
apt-get install xrdp
echo xfce4-session >~/.xsession
Below lines will solve your problem
THE FIX: edit /etc/xrdp/startwm.sh
make the last two lines look like this;
#. /etc/X11/Xsession
. /usr/bin/startxfce4
NOTE: Don't forget to create new users with password. Extremly necessary.
With this you can simply RDP(Remote Desktop) to the Ubuntu GUI machine.
Donot forget to open ports in Security Groups and Firewall if any implemented.
I need SSHD (SSH server) enabled in order to make Hadoop running in my Travis CI job.
For Linux I just do sudo apt-get install openssh-server and it works. But for OS X the only tips I've found say to enable Remote Login in settings: How to install sshd on Mac?
How can I enable SSHD using just .travis.yml for OS X?
I've finally found the command to enable Remote Login from terminal:
sudo systemsetup -setremotelogin on
I'm trying to write a Powershell script to create a VM in Azure with Docker installed. From everything I've read, I should be able to do the following:
$image = "b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_3-LTS-amd64-server-20150908-en-us-30GB"
azure vm docker create -e 22 -l 'North Europe' --docker-cert-dir dockercert --vm-size Small <myvmname> $image $userName $password
docker --tls -H tcp://<myvmname>.cloudapp.net:4243 info
The vm creation works, however the docker command fails with the following error:
An error occurred trying to connect: Get https://myvmname.cloudapp.net:4243/v1.20/info: dial tcp 40.127.169.184:4243: ConnectEx tcp: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Some articles I've found refer to port 2376 - but that doesn't work either.
Logging onto Azure portal and viewing the created VM - the Docker VM Extension doesn't seem to have been added and there's no endpoints other than the default SSH one. I was expecting these to have been created by the azure vm docker create command. Although I could be wrong with that bit.
A couple of example article I've looked at are here:
https://azure.microsoft.com/en-gb/documentation/articles/virtual-machines-docker-with-xplat-cli/
http://blog.siliconvalve.com/2015/01/07/get-started-with-docker-on-azure/
However, there's plenty of other articles saying the same thing.
Does anyone know what I'm doing wrong?
I know you are doing nothing wrong. My azurecli-dockerhost connection had been working for months and failed recently. I re-created my docker host using "azure vm docker create" but it does not work any more.
I believe it is a bug that the azure-docker team has to fix.
For the time being, my solution is to:
1) Launch a Ubuntu VM WITHOUT using the Azure docker extension
2) SSH into the VM and install docker with these lines:
sudo su; apt-get -y update
apt-get install linux-image-extra-$(uname -r)
modprobe aufs
curl -sSL https://get.docker.com/ | sh
3) Run docker within this VM directly without relying on a "client" and in particular the azure cli.
If you insist on using the docker client approach, my alternative suggestion would be to update your azure-cli and try 'azure vm docker create' again. Let me know how it goes.
sudo su
apt-get update; apt-get -y install nodejs-legacy; apt-get -y install npm; npm install azure-cli --global
To add an additional answer to my question, it turns out you can do the same using the docker create command ...
docker-machine create $vmname --driver azure --azure-publish-settings-file MySubscription.publishsettings
This method works for me.
I am trying to use Cloud9 IDE on a server. I added the SSH key and once I try to SSH into the server the error message
Could not execute node.js on root#xxx.xxx.xxx.xxx
appears.
I have nodejs installed on the server, v0.10.25
You need to install the package "nodejs-legacy".
apt-get install nodejs-legacy
The SSH dialog allows you to set the path to the Node.js binary. That should solve your issue.
I found it is necessary to scroll down and click on the advanced tab. Then I entered /usr/bin/nodejs from my "which nodejs" output in my SSH session. This worked for me even though the documentation states AWS tries to do this by default. That left me in the AWS file work space on the server I ssh'ed into as desired.
nodejs was not installed on my EC2 instance, so I installed using the instructions from the following link, and it work perfectly. Tutorial: Setting Up Node.js on an Amazon EC2 Instance
sudo apt-get install nodejs worked for me