amazon-lightsail

问题 I have an amazon AWS LightSail instance and have installed Node js downloaded from nodejs.org. Now the setup is complete and I am able to launch my nodejs webpage inside LightSail instance using "http://localhost but when I try to do it using the lightsail public IP from any other laptop, it not getting accessible (getting web error as "This site can’t be reached"). I have set the node js to listen to port 80 which is open by default. A lot of materials shows that bitnami as a way to do it

问题 I have made a silly mistake; So I have a LightSail instance to run my Wordpress Bitnami website. I had recently got the domain working but decided that I wanted to generate an SLL certificate so decided to run the bncert-tool function in the console. I kept getting an error message saying that the 'example.com' and 'www.examples.com' DNS public IP addresses were different. After not being able to fix this issue I ran (rather stupidly) the following command to skip the DNS record check: sudo

问题 I have made a silly mistake; So I have a LightSail instance to run my Wordpress Bitnami website. I had recently got the domain working but decided that I wanted to generate an SLL certificate so decided to run the bncert-tool function in the console. I kept getting an error message saying that the 'example.com' and 'www.examples.com' DNS public IP addresses were different. After not being able to fix this issue I ran (rather stupidly) the following command to skip the DNS record check: sudo

问题 When running the bncert-tool on my LightSail server, I have accidentally modified some of Apache's configuration files which I now need to revert from the backup directories. See previous question and answer here for more info: Modified Bncert command has taken site offline I have looked in both the /opt/bitnami/apache2/conf and /opt/bitnami/apache2/conf/bitnami directories and can see a series of files including httpd.conf.back.202101220056 (/conf) and bitnami.conf.back.202101220056 (

问题 I've reviewed the Lightsail load balancer and unlike ACM, you cannot add wildcard SSL's. For example on ACM, this can done: example.com *.example And then attached to an EC2 Loadbalancer. But for Lightsail, the wild card is not accepted. When we issue only on the apex domain to the load balancer: example.com When we resolve demo.example.com, we get a cert invalid error. As we don't know ahead of time the sub-domains in use, and the limit of 9 is too few, is there a workaround? 回答1: I came up

问题 I've enabled the UFW service without allowing SSH access before then logging off. I am now unable to ssh back to the instance. The steps I have already taken: Made a snapshot and create a new instance from it 回答1: The general point: try to execute a command ( firewall disabling ) while creating a new instance. I was able to do it with the usage of AWS CLI: aws lightsail create-instances-from-snapshot --region eu-central-1 --instance-snapshot-name TEST_SSH_FIX-1591429003 --instance-names TEST

问题 I've enabled the UFW service without allowing SSH access before then logging off. I am now unable to ssh back to the instance. The steps I have already taken: Made a snapshot and create a new instance from it 回答1: The general point: try to execute a command ( firewall disabling ) while creating a new instance. I was able to do it with the usage of AWS CLI: aws lightsail create-instances-from-snapshot --region eu-central-1 --instance-snapshot-name TEST_SSH_FIX-1591429003 --instance-names TEST

问题 I've enabled the UFW service without allowing SSH access before then logging off. I am now unable to ssh back to the instance. The steps I have already taken: Made a snapshot and create a new instance from it 回答1: The general point: try to execute a command ( firewall disabling ) while creating a new instance. I was able to do it with the usage of AWS CLI: aws lightsail create-instances-from-snapshot --region eu-central-1 --instance-snapshot-name TEST_SSH_FIX-1591429003 --instance-names TEST

问题 I've enabled the UFW service without allowing SSH access before then logging off. I am now unable to ssh back to the instance. The steps I have already taken: Made a snapshot and create a new instance from it 回答1: The general point: try to execute a command ( firewall disabling ) while creating a new instance. I was able to do it with the usage of AWS CLI: aws lightsail create-instances-from-snapshot --region eu-central-1 --instance-snapshot-name TEST_SSH_FIX-1591429003 --instance-names TEST

问题 After 2 days of trying multiple tutorials & reading StackOverflow, I'm calling for help! The setting: The development version is running smoothly on the AWS Lightsail server. It's during the production deployment that I'm running in continuous problems with the static files. The application runs on the appointed subdomain but it's missing all the JS/CSS/images/... I have followed the official docs but to no avail. 1/ https://docs.bitnami.com/aws/infrastructure/django/get-started/deploy-django