Created a droplet on digitalocean but when I searched that IP address then error came that domain.com refused to connect.
I go to droplet's networking section and also turned ON the firewall and also allowed http::80, https, but still the error is there.
What mistake have I made?
Related
I have setup an Nginx reverse proxy on my Raspberry Pi running Fedora Server and nothing will load locally or publicly. Whenever I connect to the ip address of the Raspberry Pi with port 80 I get a message saying the connection was reset. I have looked at other questions here, but none of them have been able to solve my problem. Note: Nginx is running with the default configuration.
I have my domain on namecheap and My ubuntu server on upcloud. My react app is installed on ubuntu server. It's ip is xx.xx.xx.xx:3000 I tried pointing it through namecheap but when I go to the url it shows the content from xx.xx.xx.xx (not from xx.xx.xx.xx:3000) How to solve this issue?
I have 3 websites running on my server, all of them on different ports. One is on port 80 and it works fine, the other one is on port 88 and it also works fine. Today I deployed a third one on port 8080, opened the port in Firewall.
I can access it with http://localhost:8080/, with 127.0.0.1:8080 and with it's internal IP address. I can't access it using the external IP address for some reason. I tried accessing it locally using the external IP address and I tried from another computer.
It is worth noting that the website on port 8080 is almost identical to the one on port 80.
Initially I thought it was a firewall issue but I disabled the firewall and tried again and I get the same result (The website took too long to respond).
I am using Windows 10 on the server.
Any ideas as to why this is happening?
I figured out the answer. I am using an EC2 instance from Amazon Web Services for a server. I forgot to go into the console in AWS and open the port there too. I did that and now it's working as it should.
There could be couple of reasons.
Cloud Provider(AWS) Specific
Check your subnet's ACL rules. Both ingress and egress
Check the security group attached to the instance. It should allow ingress
on that port/protocol
Windows Server Firewall: All windows servers and desktops have firewall running which blocks any non-standard traffic. Make sure to add a custom rule to allow the traffic that you want to allow. I found this https://computingforgeeks.com/how-to-open-a-port-in-windows-server-firewall/ link helpful
Recently I've had this problem with a Tomcat server and it was saying that it couldn't resolve the host address. It turned out to be that it required my internal IP to be assigned to localhost, i.e. 192.168.A.B but why was it not already resolved as localhost? And there's no good adding that IP to my hosts file because as soon as I change network it'll become something else.
I try to host my website for learning, on a CentOS free VPS (no support).
I’m allowed to access Apache service via IPv4 by adding a custom port.
Using the format below, I can access the server with my browser.
e.g. 12345 is my custom port that I created for default port 80:
http://xxx.xxx.xxx.xxx:12345
But I cannot access my hosted website http://mywebsite.com (‘the webpage is not available’).
I’ve created the proper DNS record on my DNS provider, and pointed the domain name to the free VPS server IPv6 address (through CloudFlare).
Note: My ISP doesn't provide IPv6 connection and the IP is not ICMP pingable (I can’t create IPv6 tunnel).
Here is my telnet test communication result (not my real IPv6 address):
[root#myserver ~]# telnet mywebsite.com 80
Trying 1a12:1234:1:1::1:1a23...
Connected to mywebsite.com.
Escape character is '^]'.
Connection closed by foreign host.
[root#myserver ~]#
Why I can’t access my website: http://mywebsite.com ?
Okay.., what fixed it was adding on Cloudflare a 'CNAME' record in addition to the existing 'AAAA' record.
Hope this help someone.