Regaining access to EC2 instance after it was stopped and restarted

Hi

The EC2 instance running my parse server was recently stopped ((due to unauthorized access on the account).

Now i’ve restarted the instance but can’t connect to the parse server through the dashboard or otherwise.

i checked the instance log on on AWS console and got the log pasted below. Any pointers on how i reconnect?

Thanks in advance :pray:t2:

Copy log
Download
650000+0 records in

650000+0 records out

665600000 bytes (666 MB) copied, 6.94317 s, 95.9 MB/s

Setting up swapspace version 1, size = 649996 KiB

no label, UUID=***

/opt/bitnami/mongodb/scripts/ctl.sh : mongodb started at port 27017

e[33mwarne[39m: --minUptime not set. Defaulting to: 1000ms

e[33mwarne[39m: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms

e[32minfoe[39m: Forever processing file: e[90mserver.jse[39m

/opt/bitnami/apps/parse/scripts/ctl.sh : Parse started

Syntax OK

/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80

curl: (28) Connection timed out after 5001 milliseconds

curl: (7) Failed to connect to myip2.bitnami.org port 80: Connection timed out

curl: (28) Connection timed out after 10000 milliseconds

curl: (7) Failed to connect to myip2.bitnami.org port 80: Connection timed out

curl: (28) Connection timed out after 15001 milliseconds

Starting gonit daemon

  • Stopping System V runlevel compatibilitye[74G[ OK ]

Cloud-init v. 0.7.5 running ‘modules:final’ at Sun, 11 Jun 2023 15:27:29 +0000. Up 177.91 seconds.
Cloud-init v. 0.7.5 finished at Sun, 11 Jun 2023 15:27:29 +0000. Datasource DataSourceEc2. Up 177.98 seconds

Ubuntu 14.04.5 LTS ip-172-31-36-14 ttyS0

ip-172-31-36-14 login:

I’d suggest to SSH into the instance and verify that Parse Server is running locally, This way you can distinguish a local issue vs. infrastructure (ALB, WAF, etc) issue.

Thanks very much for your suggestion Manuel. I get an operation timed out error when trying to connect through SSH.

If you can’t SSH into the instance then maybe check the instance health in the various metrics and logs. Sounds more like an infrastructure / resource issue.