Pablo's questions

I accidentically removed grant from the user_accounts tab (privileges) for root account

I have this extra account backend_dev_team

Now edit privileges clickable link is missing can I undo it?

UPDATE

GRANT ALL PRIVILEGES ON * . * TO 'root'@'localhost'; but gave me error access denied, I entered this using backend_dev_team and root account

My last activity was I accidentically edited permission on my ec2 instace

I was trying to add permission 775 on my project's directory called storage

command like this

sudo chmod -R 775 storage

But instead doing this on /var/www/html/ I did this on directory like this ~ means the root directory.

and I exit the terminal and tried to access the server using ssh but it gaves me an error

Connection time out port 22

The following steps I tried to fix but didn't work on my end

1. Adding Public IP to Security Group using SSH Port 22
2. Adding rule to Network ACL ( for both inbound and outbound rules )
3. Checking Route table
4. Tried to Snapshot the Instance and launch new ec2 instance using same AMI

all the above steps are what I tried, but still I cannot connect. Is there missing step that I need to do?

As of now I can visit the wordpress installer on the browser

But the problem is I having an error 504 Gateway Time out

As I open the log file shown in the frontend this gaves multiple error like this

POST-EXTACT-CHECKS
--------------------------------------
PERMISSION UPDATES:
   -DIRS:  '755'
    -FILES: '644'
[PHP ERR][WARN] MSG:chmod(): Operation not permitted [CODE:2|FILE:/var/www/html/etha/dup-
installer/lib/snaplib/class.snaplib.u.io.php|LINE:479]

I've already made sudo chmod -R 777 /var/www/html/projectwp but seems nothing works

UPDATE

As of now the propagation is done already

How did I checked it?

1. ping <public-ip-of-instance>

2. I tried to check my domain using HTTP Request and it works fine. The site loading fine on port 80

Things I've checked

1. Security Group - As of now my load balancer uses the security group of my instance.

these are the following:

80, 443, 22

2. And pointed my ELB to <domain.com> & <www.domain.com> you can check it on the lower part of the image and upper part.

3. As you can notice there's a lot of A Record thsoe are the subdomains and emails. that needs to be kept with their IP Addresses.

Subdomain are working fine right now. But the domain doesn't work on port 443 and I don't know why.

PS: in my dns provider I changed the nameserver given from the created zone and @ A Record pointed to my instance public ip.

Is there anything I missed?

UPDATE

  `ns-xxx.awsdns-47.co.uk. awsdns-hostmaster.amazon.com. 1 7xxx0 900 1xxxxx00 8xxxx0`

So I have these 2 different endpoints

1. blog.subdomain.com - The wordpress files of this located on my hosting (HostMonster)
2. domain.com - This was a parked domain, but recently tried to use AWS to upload my files and point this domain.com A Record & Nameserver to AWS.

blog.subdomain.com was working fine before, but not until when I tried to point my domain.com to my AWS Ec2 Instance. The changes I made was changing the a record of my domain.com pointed to aws public ipand changed the nameserver into aws

I'm using Loadbalancer & Route53 on my domain.com.

Now I wonder how can I keep the blog.domain.com files uploaded to my hosting at the same time the domain.com files are uploaded to aws ec2 instance? The showing on my blog.subdomain.com is DNS_PROBE_FINISHED_NXDOMAIN

Just want to know some possible ways to fix this, without transferring the files again and again.

UPDATE

Currently I have working fine ec2 instance

and the DNS A Record is pointed to my elastic ip

Is it risky to point it on elastic ip? or should I point my DNS A record to my load balancer link?

So my boss, said "I don't know, what company you were working for before. But DNS settings doesn't take 24 hours to take effect since when I started this company. "

I'm having a doubt with myself if I'm doing this AWS thing right but

Here's my key words

1. EC2 Instance
2. Elastic IP
3. Load Balancer
4. Request Certificate to Domain Provider using CNAME Verification
5. Route 53
6. DNS A Record
7. DNS Nameserver

As of now, I tried all of these key words. Since changing nameserver may take few hours to take effect, mostly 24 hours.

and

DNS A record takes 4-8hours before it take effect.

Now I waited almost 1 day just to finish this and it works fine.

I know that changing nameserver may take some time but is there another way on how to implement SSL on my ec2 instance without waiting this too much? Just curious with the aws. Probably some of you will down vote this question. Since I've already done it.. But just wanted to know more deeply if there's possible way of applying ssl on Elastic IP of the instance without using Route 53 or should I say without waiting too much.

Hello I just wanna ask

Currently I have created a load balancer and route 53

In my route 53 I have these records

Now I have these name servers registered on my BlueHost (Mydomain provider)

Yesterday I just changed the name servers on bluehost based on the requirement of AWS after creating a record set (route53)

Now I can search this http://www.adthrone.com/

but not this

http://adthrone.com

Where this should working after changing the name server it just suddenly happened.

UPDATE

I created another record set

does this mean, adthrone.com should be working now?

Currently I'm trying to put SSL on my EC2 Instance using Load balancer & Route 53 for my BlueHost Domain

As of now I have working Load balancer

https://adthrone-loadbalancer-1188159040.us-west-2.elb.amazonaws.com

and also I did some Route53 like this

Is there something I need to reconfigure on my BlueHost account just to map my adthrone.com domain to my ELB?

UPDATE

Is this the name server that I need to add on my bluehost?

AWS UI

BlueHost UI

After placing the name servers and saves.

Im using AWS Linux 2 AMI Currently I have AWS EC2

Recently the mysql doesn't work anymore but it worked before.

when I tried to do this

sudo service mysql start

or

sudo service mysqld start

It says service mysql unit not found

I tried also to sudo service httpd start and start the mysql but still doesn't work

I tried also to check the disk usage of my ec2

using this commnad : df

This gives me an output like this

Filesystem     1K-blocks    Used Available Use% Mounted on
devtmpfs         2000788       0   2000788   0% /dev
tmpfs            2018800       0   2018800   0% /dev/shm
tmpfs            2018800     480   2018320   1% /run
tmpfs            2018800       0   2018800   0% /sys/fs/cgroup
/dev/xvda1       8376300 5880760   2495540  71% /
tmpfs             403764       0    403764   0% /run/user/1000

Where here /dev/xvdal has 71% of used storage

Is this even related why mysql doesn't want to start?

Currently exploring the relation between Plesk and AWS

As of now my AWS account showing the Memory Disk SSD Usage of 30GB of my account

Where it says 40%+ of memory are being used out of 30GB

and Relational Database System of AWS showing no current data

and my AWS Account doesn't run a single instance of ec2

My question is, how does the Plesk uses AWS when it comes to storage?

Because as of now My plesk contains the files of my wordpress site and database of site using phpmyadmin (mysql)

Currently I have setup

docker with linux ubuntu 18.04

In my container reverent_ptolemy

contains the project of my api.

On my container

HTTP vhosts configuration is listening to 3021

HTTPS vhosts configuration is listening to 1250

and on my Host

port 3021 is mapped to port 80

port 1250 is mapped to port 443

In my host docker

I can access my api through HTTPS Curl

like this

curl https://<sub-domain>/api/login

But when I tried to access this from the browser

this gives me an error like this

PS:

Only http://<subdomain>/api/login is accessible from the outside world not the https

What could be the reason why HTTPS is only accessible on the host and container but not accessible from the outside world?

Currently I have laravel project on my docker instance.

But the problem is,

SSL accessible only for that container and I can check it using this command

curl --insecure https://127.0.0.1:4021/api/login

And this gives me my api response like this

Which is correct and working fine only if I try to curl it inside the container.

Now I'm trying to check if that curl is accessible to my docker host

using this command

curl -k -v https://MY-HOST-DOCKER-IP:4021/api/login

but this gives me an error like this

What could be the reason why this error keeps showing?

UPDATE

Currently I'm trying to setup my ssl in docker instance. I'm trying to check if these ports are allowed in my firewall

Port: 443 and 4021

I've searched that allowing specific port for firewall using this terminal command

sudo ufw allow 4021

But how can I check and see all the ports allowed in my firewall?

I update my AWS instance from ubuntu 16 to 18.04.

Currently I have the xampp installer with this name

xampp-linux-x64-7.2.2-0-installer.run

located at user@ip:~$

I tried to run this command sudo chmod +x xampp-linux-x64-7.2.2-0-installer.run

But the problem is when I tried to run this command

sudo ./xampp-linux-x64-7.2.2-0-installer.run

Terminal says

sudo: ./xampp-linux-x64-7.2.2-0-installer.run: command not found

Is there anything I need to do first?

I have this configuration setting on my /opt/lampp/etc/httpd.conf

<VirtualHost *:902>
    DocumentRoot "/opt/lampp/htdocs/e-wallet-frontend/public"
    ServerName localhost
</VirtualHost>
Listen 902

and my Laravel Project placed in my /opt/lampp/htdocs/e-wallet-frontend

I already installed my composer and laravel on the server all the dependencies are downloaded already.

If I try to navigate the project manually without using port something like this

http://mypublicip/e-wallet-frontend/public/index.php the project appears but of course lot of errors.

But whenever I try to navigate the project something like this

http://mypublicip:902/login since laravel performs the route.

The browser always gives this response, too long to respond

This configuration is working on my local. But when I try to use it on AWS It doesn't work anymore. Is there anything I need to configure to solve this problem?

UPDATE using sudo curl -vv http://mypublicip:902/login

enter image description here

Ubuntu 18.04