B
Bemz
Guest
Bemz Asks: ConnectionRefusedError: [WinError 10061] No connection made because the target machine actively refused it
I am running an eth node on an ec2 which is running well. The api is accessible through port 3500. However, the data seems to be only accessible internally through 0.0.0.0:3500, whenever I am trying to access the api publically through the ec2 upv4 address (e.g http://3.10.45.65:3500/eth/v1alpha1/beacon/chainhead <-dummy link) i ran into the error
I made sure to keep the ec2 instance inbound security group open to all traffic.
Just so I was not making any mistakes, I even hosted a dummy page publically using python http server through port 3500 which was functioning well.
I am a lil confused to what else could be blocking the server from handling the request.
Any input would be appreciated.
I am running an eth node on an ec2 which is running well. The api is accessible through port 3500. However, the data seems to be only accessible internally through 0.0.0.0:3500, whenever I am trying to access the api publically through the ec2 upv4 address (e.g http://3.10.45.65:3500/eth/v1alpha1/beacon/chainhead <-dummy link) i ran into the error
ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it
.I made sure to keep the ec2 instance inbound security group open to all traffic.
Just so I was not making any mistakes, I even hosted a dummy page publically using python http server through port 3500 which was functioning well.
I am a lil confused to what else could be blocking the server from handling the request.
Any input would be appreciated.