Score:0

log.io monitoring tool hosted in AWS EC2, cannot reach server after starting log.io-server

za flag

Installed log.io in my Ubuntu 20.04 EC2 instance as given in the below documentation.

https://github.com/NarrativeScience/log.io

After npm install started server with log.io-server, terminal outputs

TCP message server listening on port 6689
HTTP server listening on port 6688

I tried to access the log.io http server in browser using EC2 Public IPv4 address on port 6688 Expected result expected logio server

The result is 'IPv4':6688 site can't be reached

In security group of EC2 instance 6688 , 6689 ports are open as custom TCP to 0.0.0.0

in flag
Have you confirmed that `ufw` is not blocking access? `sudo ufw status` will show you what ports are open, whether the service is running, or whether the tool is installed at all
Shanmugavel avatar
za flag
executed `sudo ufw allow 6688` to allow that port. still same issues
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.