I installed tigervnc on AWS Lightsail CentOS7. When I try to connect to the server with vnc client it shows a black screen. Then I tried to run startx, it gives an error. "xauth: file /root/.serverauth.6301 does not exist".
Is it possible that GUI is not working on AWS Lightsail?
I was using AWS Lightsail Server with low configuration. The problem was gone after I moved to another AWS Lightsail server with high configuration. I think the problem was in low memory.
Related
I have a nodejs app running on an EC2 instance. I installed the webapp using Ubuntu server 18.04 and node version v16.x using this link:
Node installation guide v16.x
To run the project I used the following tutorial: Tutorial link
The problem I am facing is that when I run the starting command npm start my app launches on the server using port 3000. But whenever I open the link provided from AWS which in my case is : https://ec2-3-72-79-132.eu-central-1.compute.amazonaws.com it doesn't respond. I saw some similar questions and most common answers were to edit the inbound security groups which I did.
But it still doesn't work. I also tried to access the link with http only like this:
http://ec2-3-72-79-132.eu-central-1.compute.amazonaws.com:3000 but it still doesn't work. Any help will be highly appreciated, because I spent 2 days struggling with this issue and I see that I don't make any progress.
Sorry maybe it is a dump question but I could not go further.
I got a website which already built with ReactJS and working on AWS Ec2
When I run on localhost
First; in terminal which in file directory run node server.js
yarn start
then I can see the localhost:3000 then when I make any changing just send with SSH and run server with PM2 which pm2 restart server
My question is I want to create a second AWS EC2 instance and run the code there as well when I change config.json which domain is store there I can see a NETWORK ERROR
I created a ec2 instance copied all my files there and I installed NodeJS npm and pm2 but I could not managed see my website on localhost:3000()
What Do I have to do?
You need to use the EC2 public address/IP not localhost
I have Ubuntu 16.04 on VMware workstation 12 player and my desktop is Windows 10. I have created a simple Flask web api and using nginx and uwsgi. Same application is working on my Azure Ubuntu 16.04 VM without any problem.
I have not made any changes in code I brought all the files from Azure VM via scp from my local VMware VM. But still app is not working. I have followed steps given in following URLs:
I have executed all the step accept last step, instead of creating uWSGI Emperor I created systemd service
https://vladikk.com/2013/09/12/serving-flask-with-nginx-on-ubuntu/
https://www.digitalocean.com/community/questions/convert-run-at-startup-script-from-upstart-to-systemd-for-ubuntu-16
https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-server-blocks-virtual-hosts-on-ubuntu-16-04
Web api is working when i am running it from terminal using "python3 MLService.py &" command. which means flask along with my code has no issue. it is some thing with uwsgi and nginx.
I have configured wordpress in a lamp setup in centos 6.9 server.
It's an aws ec2 instance. When i stop the vm and start it again database connectivity of wordpress is lost.How do i resolve this?
I tested by rebooting from inside vm. At that time everything is working fine. But not when i stop and start from aws dashbord.. any solution?
I think the issue might be with your mysql service , after rebooting if you have not specified that it should run at start of server it would not run.
Also Make sure you have connection string as localhost and Elastic (Static) IP assigned to it.
If that is the case you can resolve it by adding the service to run every time instance start by this command:
sudo chkconfig mysqld on
I did the following steps:
1) Use an existing AMI with Ubuntu 16.0.
2) Create Instance from this AMI and Launch it.
3) Do nothing, just stop the instance.
4) Create AMI from this stopped instance.
The new AMI becomes (Platform) "Other Linux" and I cannot login into SSH into anymore......:
When using Putty, I can see on terminal output 'instance XXX connected',
but do not have access the terminal Bash.
(just read only screen).
It happens anytime when I used another AMI than Amazon AMI (Ubuntu).
Is it related to Free tier account ?
How to get support on this ?
Thanks vm.
Similar issues:
https://forums.aws.amazon.com/message.jspa?messageID=758595#758595
Solved (using AWS Support...):
Pb was due to AWS Mindterm Java SSH Browser which cannot connect to this instance.
But using Putty works well, "Other Linux" does not have influence.
1.) Other Linux means No vanilla Ubuntu (default Ubuntu changed).
2.) Can be connect to EC VM using Putty
putty -ssh loginName#Ipadress
Dont forget to convert PEM file to PPK using PuttyGen 1st.
login depends on the original AMI instance,
here ubuntu/root can be used since this is Ubuntu Amazon.
Compare to google Cloud, AWS does not have robust Web Browser SSH, so 3rd party SSH is needed.