I tried to install nextcloud on ec2 instance and tried to secure it through https but failed.
The procedure which i followed for setting up nextcloud on ec2 instance is
Link : https://medium.com/#nicola88/nextcloud-on-aws-ad244739c586
Error that getting is
enter image description here
Please help me resolving this issue or i want to know how properly install nextcloud on aws and secure it using https
Related
I have a docker image running on EC2 instance that tries to issue an AWS command when I get this error
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "https://ec2.us-east-2.amazonaws.com/"
If I give the EC2 instance Security Group that can access everything it works. But I look for a more limited set of rules. I already tried to give it only ports 443 and 80 (both ingress and outgress) but it doesn't work.
Any other configuration I should try?
Thanks,
I thought of migrating my php application from shared hosting to AWS. however i'm facing some difficult while installing packages, whenever i try to install a package it saying connecting to some xyz server and halts, the installation does not proceed. I followed below steps
1.) I created amazon AWS free tier account
2.) I created a security group policy
3.) I generated a elastic IP from the pool
4.) I created an AWS ec2 instance using Ubuntu x64 v16 (Did all the setup and was fine)
5.) Generated the .pem key and downloaded it, also connected via SSH using the key, i'm able to connect
6.) I then associated the Elastic IP to the instance and restarted the instance
whenever i try to connect to the public IP address it says server took too long to respond or is not accessible. I thought might be i need to install Apache
I'm trying to install Apache, also not only Apache even if i run sudo update && upgrade it just shows a message connecting to server and hangs up!
What my be the problem? Where did i go wrong?
i have setup bitnami wordpress on my ubuntu 64 bit server and now want to add ssl provided by amazon. i have followed following tutorial by bitnami
i am on last step:
/opt/bitnami/apps/APPNAME/conf/httpd-prefix.conf
but when i enter this command in ssh . it says permission denied.
and wen i open my web it says : service temporary unavailable "
but i can visit my web with public ip of instance its working.
You don't enter the file into ssh. You edit the file with a text editor such as "nano" or "vi". Then follow the instructions.
vi opt/bitnami/apps/APPNAME/conf/httpd-prefix.conf
I have created an AWS Ec2 instance using the following documentation:
https://d0.awsstatic.com/Projects/P5505030/aws-project_Jenkins-build-server.pdf
However, when I get to the stage where I connect from my web browser to Jenkins using http://:8080 I get HTTP Error: 503.
I originally taught it was down to my network settings/security group settings on my AWS EC2 instance but I have installed Apache and I can access the Apache test page from port 80. I have allowed traffic from HTTP, SSH and TCP and set the appropriate ports as per the guide.
I have tried curl http://localhost:8080 on the putty instance connected to my EC2 instance and I get the same error. Also, I have checked the /var/lib/jenkins folder and it is empty.
Any help or direction in the right path would be greatly appreciated,
Thank you.
If anyone runs into this problem in the future, the documentation installs the latest version of Jenkins.
I installed an older, stable Jenkins version and this worked perfectly using the "sudo yum install jenkins-2.47-1.1"
The problem is resolved by installing Java 8.
https://issues.jenkins-ci.org/browse/JENKINS-43609
I had successfully used putty to login into Debian-8.1 on AWS by using key file. Once I upgraded debian using the command apt-get upgrade and tried to login through putty, it shows the error which i mentioned below:
putty fatal error: network connection refused
How can i resolve this?
I think Kernal Upgrade , Reboots the system in Linux and if you have not allocated Elastic Ip to the instance , the Ip would have have changed.
Did you Check the Instance IP ? Are you able to Login via Web based Interface from EC2- Console ?