I am configuring a new site using a cloud server Aruba Business (Nodejs, Docker, Ubuntu 22, Wappler Beta, Mac)
I have a problem with the opening of the ip ports; Only port 22 is open, while despite all attempts made ports 80 and 443 are always closed.
Suggestions?
here’s a chatgpt suggestion:
To open ports 80 and 443 on Ubuntu, you can use the ufw (Uncomplicated Firewall) utility, which is a user-friendly interface for managing iptables. If you haven’t already installed ufw, you can do so by running:
sudo apt update
sudo apt install ufw
Once ufw is installed, you can open ports 80 and 443 with the following commands:
sudo ufw allow 80
sudo ufw allow 443
This will allow incoming traffic on ports 80 and 443. After making these changes, you may need to enable ufw if it’s not already running:
sudo ufw enable
If you want to check the status of ufw and see the list of rules, you can use:
sudo ufw status
Make sure that the application or service you want to access through these ports is properly configured to listen on the specified ports. If you are running a web server, such as Apache or Nginx, they should automatically listen on ports 80 and 443.
Keep in mind that opening ports on a system could expose it to potential security risks. Ensure that you only open the ports you need and that you have appropriate security measures in place.
I followed your indications, but unfortunately the ports 80 and 443 remain closed
Firewall is active and enabled on system startup
those ports are all open in your firewall as shown in your screenshots.
Probably your provider have another firewall Infront, so check with them.
Ok thanks George, I hadn’t thought about this.
I go to check
Ports are closed until a program decides to bind to them. Please show a screenshot proving your desired program is binding to ports 80 and 443. This would be most likely nginx, Traefik or Caddy that would sit in front of NodeJS
Edit: Another way to test is to run curl http://127.0.0.1
I contacted the provider, and he assured me that the server has no filter on ports 80 and 443
Strangely, the doors are now open, perhaps because I updated to the new Beta RC1?
The important thing is that I overcame the problem
Maybe you just did a successful deploy and the services are now running and not before.
Anyway glad it is all working .