MikeJones To get back on topic: Assuming I can spin up a Apache LAMP instance on AWS and go from there? New to AWS and want to learn it to, so I think I am going to start here: https://aws.amazon.com/getting-started/projects/launch-lamp-web-app/
0E800 MikeJones Lemp All I had to do was create a 1gb ubunti instance and run below script. https://github.com/webeindustry/flarumvpsinstallscript/blob/patch-1/script
MikeJones 0E800 so I may hav emessed up. I ran the script and i put seekadventure.net instead of the ip address. I ran the entire script with no problem but now I do not know how to view my forum..... I tried taking the IPV4 Public IP from my AWS console and putting it into chrome but it looks like it times out
MikeJones Alright so I just followed this to change my host name: https://aws.amazon.com/premiumsupport/knowledge-center/linux-static-hostname/ Its been awhile since I have dove into something like this. Do I then need to go to google domains and change something there too for my domain name to work? I am trying to prep everything before I run the FLARUM install script
0E800 MikeJones That's okay. Try: sudo nano /etc/nginx/sites-enabled/whateveryoursitenameiscalled Change server_name to your IP CTRL-X , Y to save. sudo systemctl restart nginx If you want, you can hit me on https://gitter.im/0e800
0E800 MikeJones No Edit the file and where it says Server name seekadventure.net Change seek adventure.net to your Ip address. sudo nano /etc/nginx/sites-enabled/seek adventure.net
MikeJones 0E800 changed and re-booted server. Still cant access site by typing in the public IPv4 ip ec2 gives me
0E800 MikeJones Did you allow for port 80 http in the AWS Instance security group rules? https://aws.amazon.com/premiumsupport/knowledge-center/connect-http-https-ec2/
MikeJones I get the to long to respond error if I use the hostname that I use to connect with putty too
MikeJones I did create a new security group, was I supposed to add the rules to one of the existing security groups? The directions on AWS did not specify.
0E800 MikeJones Make sure your instance is using the security group that contains the rules that include allowing port 80
