Installing Flarum on AWS

MikeJones

0E800 What am I looking for there?

0E800

MikeJones

Your looking to change the server name to your Ip

MikeJones

0E800 so change root /var/www/seekadventure.net; to root /var/www/myIP ?

0E800

MikeJones

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

may you provide the ip so I can see?

MikeJones

0E800 13.58.215.35

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

0E800 yes

MikeJones

Tried to post an image but it didnt work, must have used the wrong syntax:

0E800

what is the output of:

cat /var/log/nginx/error.log

MikeJones

0E800 typed that into putty and got nothing back

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

MikeJones

0E800 Looking for how to tie the security group to the instance. I assumed if I crated the security group that I was creating it in that instance but now it looks like probably not.

0E800 You are using lemp stack?

Yes

0E800

You are using lemp stack?

0E800

Review https://serverfault.com/questions/237557/how-to-change-an-ec2-instances-security-group

MikeJones

0E800

Now I have issues with the easy part:

Something went wrong: SQLSTATE[HY000] [1045] Access denied for user 'seekAdventureAdmin'@'localhost' (using password: YES)

Assuming I couldn't just make my own database name up right there, it was asking what the script used?

0E800

Since the nginx error log is empty, makes me believe traffic is not be allowed through.

MikeJones

Hell yeah, that worked thanks! I can now see my FLARUM set up!

« Previous Page Next Page »