2 Answers
- Newest
- Most votes
- Most comments
0
netstat -tulpn
shows that sshd is listening on port 22, which is why you're able to connect using SSH.
There doesn't appear to be a webserver running, which would be expected to be listening on port 80 and/or 443.
Could you try starting your webserver, you will know better than me what this is but could be something like httpd (Apache) or nginx.
0
Thanks for your quick reply Steve.
How am I to proceed with starting my webserver? It is Apache that I am using.
I have restarted the webserver (or I think I did):
If I am checking in the wrong place, could you provide me resources where I could go check how to troubleshoot the issue more in depth?
answered a year ago
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 4 months ago
Thanks for your quick reply Steve.
How am I to proceed with starting my webserver? It is Apache that I am using.
I have restarted the webserver (or I think I did):
bitnami@ip-172-26-2-541:~$ sudo /opt/bitnami/ctlscript.sh restart apache Restarted apache
If I am checking in the wrong place, could you provide me resources where I could go check how to troubleshoot the issue more in depth?
Yes that looks like the correct command https://docs.bitnami.com/aws/faq/administration/control-services/
Now does
netstat -tulpn
show anything listening on 80 and 443 ? Similar to:Apache log files are usually found in
/var/log/httpd/
, though you may have to become root in order to view them.