How To Open Port 80

[Quinton Hebenstreit]

Thisis a free utility for remotely verifying if a port is open or closed. It is useful to users who wish to verify port forwarding and check to see if a server is running or a firewall or ISP is blocking certain ports.

Port forwarding or port mapping allows remote computers to connect to a specific computer or service on a private network. This allows you to run a web server, game server or a service of your choosing from behind a router.

In a typical network the router has the public IP address and computers/servers obtain a private IP address from the router that is not addressable from outside the network. When you forward a specific port on your router, you are telling your router where to direct traffic for that port. This utility can verify the success of that process.

LEGAL DISCLAIMER

THE INFORMATION ON THIS PAGE IS STRICTLY FOR INFORMATIONAL PURPOSES ONLY. IT IS YOUR RESPONSIBILITY TO OBEY ALL APPLICABLE LOCAL, STATE AND FEDERAL LAWS. WE ASSUME NO LIABILITY AND ARE NOT RESPONSIBLE FOR ANY MISUSE OR DAMAGE CAUSED BY THE USE OF THE INFORMATION ON THIS PAGE.

After some trial and error I could get it to work.

Changed COM ports as suggested by @yvesdelbrassine, open the serial Monitor and make sure, it opens for the configured COM Port (why does platformio sometimes open the monitor for the wrong port!??)

When you managed to open the correct monitor, PRESS AND HOLD THE RST button on your esp device and THEN CLICK UPLOAD .

Once the terminal tells you it tries to connect,

release the rst button.

Port Checker is a simple and free online tool for checking open ports on your computer/device, often useful in testing port forwarding settings on a router. For instance, if you're facing connection issues with a program (email, IM client etc) then it may be possible that the port required by the application is getting blocked by your router's firewall or your ISP. In such cases, this tool might help you in diagnosing any problem with firewall setup. You could also find this useful for security purpose, in case you're not sure whether a particular port is open or closed. If you host and play games like Minecraft, use this checker to make sure the server port(25565) is configured properly for port forwarding, then only your friends will be able to connect to your server.

If you're looking for a full list of port numbers check out this wikipedia page. I've listed all the common ports above, feel free to enter any custom port number to check. By default, this site is taking your device's IP address as target ip address (the device through which you're visiting this web page), but you can change the IP input field to check for other IP addresses - remote clients and servers as well. But, please don't misuse this option otherwise, I would have to restrict the IP address to source again (as I had done earlier). Please keep in mind that if you're using a VPN or proxy server then it may not be able to get your device's IP correctly.

Port forwarding or port mapping involves translating the address (or port number to a new destination), accepting the packets and forwarding it (using routing table). It's typically used in connecting remote computers to specific programs running on computer (in a private LAN (Local Area Network)). For example : running a public server (HTTP, port 80) on a computer in a private LAN or granting SSH access to a specific computer in a private LAN etc. Read More on Wikipedia.

I had a similar problem. As far as I could tell, nothing was attached to the COM port. Earlier before I had uploaded the ESP32 (M5StickC+) filesystem image successfully, but then when I went to upload the code, this came up. Tried restarting PI, disconnecting and reconnecting the M5, powering off and on the M5, closing all terminal sessions, starting a monitor session and then closing, no luck.

What seemed to work was disabling and re-enabling the COM port in Device Manager.

The error means that your application did not listen on a port. If your deployment is not a website but rather a bot or something else that runs in the background, you will need to deploy it as a Background Worker within a Reserved VM deployment. Those options are available via the Deployments pane in the UI.

However, there is nothing actually listening in behind the port. To curl the port, there should be an application that will send a reply. This is typically called a server. As @Florian points out, you can use Python's SimpleHTTPServer to test it.

you can use sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT this accepts the port when it configures with the port to prevent from losing this terminal line of code you can use sudo apt-get install iptables-persistent The reason for sudo in the beggining of a command is to let it run as superuser the persistant uses it as a persistant connection to the port that is supplied. You can also use you can use Python's SimpleHTTPServer to test it! This was a great question! Thank You!

Here is an image side by side.

i am running the AIO installation on an ubuntu 20.04 server in plain vanilla/updated state, no firewall / router forwading ports 80/443 to the server (10.0.0.11) (i did a test installing apache and i am able to access it from a remote location via the domain name).

I am using a subdomain cloud.mydomain.com which has been pointed to the IP more than 48 hours ago and is resolving perfectly fine to the IP of this installation.

I am able to flick the switch on the firewall router, on and off for ports 443/80 and they take immediate effect. And finally, the test suggested by the nextcloud installer on portchecker.co CONFIRMS, port 443 is open.

I am typing the domain perfectly fine in the input box of the AIO setup page in the screenshot attached.

The ubuntu server is a VM under TrueNAS.

Any ideas where else i could check?

I run the installation TWICE, restoring the server to the initial fresh ubuntu setup.

/etc/hostname and /etc/hosts already setup with the complete subdomain i am using for this server.

Finally, as the last obvious test confirmation, if i shut down the ubuntu server VM where i am running the AIO setup, portchecker.co shows me port 443 is CLOSED. Confirming there was no issue whatsoever to reach the AIO install.

here is another screenshot.

Thank you for the ideas.

I have tried now re-checking that there was not an IP change, and tested using the domain instead of the IP on portchecker.co.

My terminal resolves the subdomain to the right IP, i am copying and pasting, there are no mistakes.

About the other settings.

I am following the installation instrucctions in the nextcloud github page here: GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All In One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.

I have installed another server using the same procedure at another location and the whole thing is just running one single command on a fresh installed server, there is no need to configure ip6, individual docker containers or anything, it is all automatic. That other installation went perfectly fine, so i am puzzled here why is till not finding the port, but everything else does,

Thank you szaimen.

I have a TrueNAS server as the host running this VM.

And also, another Proxmox server on a different physical computer on the same network.

The issue is happening on both of them, i do not think is an issue with the VE. And as i mentioned, if i was able to get a cert and open a padlocked apache page on the same VM i am using for AIO, then there should not be issues with AIO.

I will test the extra switch you suggested, and report back

Thank you

The much easier option: pick a port range (10100 to 10110 as an example) and open that in the firewall from your configuration.nix with a nice comment explaining why. When you are working on a project that requires external access, have it listen on one (or more) of the ports in the range. There is no harm leaving a port open in the firewall if there is nothing listening.

I have a question that is stumping me I have opened ports on firewall on XG115 for my security cameras and they work, however after some time the ports become disabled and am not able to view my cameras from outside of my network.

Finally after many calls to the internet provider, a tech from there who also knew the Arlo product was able to do the right testing of all connections and isolated the issue to our modem. Full reset of the modem online and then manually and YAY the modem is now seeing the Arlo base and we are up and running again. Nothing at all to do with port 80 & 443 too. Thanks for the help

An internet search will tell you that port 80 and 443 are used for HTTP and HTTPS (this is secure HTTP). What this means if you can open websites that use either of these protocols, then you likely do not need to do anything. What you do NOT want to do is go into your router and mess with port forwarding because it creates a huge security risk. Don't mess with port forwarding unless you really know what you are doing.

3a8082e126