Question

Issue with 443 in my droplet

Hi all!

I want to to a simple web server which will accept JIRA webhooks on 443. That’s why i need to open it. I did “ufw allow 443/tcp” and it seems to be opened, but nothing works. From my other machine i nmaped it and… nothing, only 22/ssh. If i will change it to 8443 everything works perfectly (and nmap can “see” the 8443 port) except JIRA webhooks are only 80/443 :) Is there any limitation from DigitalOcean on 443 port or i missed something? Thanks!!!


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello, @j1nka

There is no limitation on using port 443. I believe that this is happening because at the moment there is no service listening on this port. You can confirm this by running a netstat command from your droplet:

netstat -plunta | grep 443

If there is no output then the issue is that there is no service binded to this port and this is what you’ll need to sort out. You can check the configuration of your web server (Apache, Nginx, Tomcat).

If you get output and you can see that there is a service listening on this port then the issue is most likely with the Firewall configuration.

Let me know how it goes.

Regards, Alex

Thanks for your replies, @alexdo , @bobbyiliev !!!

Changed to 0.0.0.0, netstat -plunta | grep 443

tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      4967/python3.6  
tcp        0      0 206.189.7.216:60214     149.154.167.220:443     ESTABLISHED 4967/python3.6 

nmap output (nmap -Pn):

PORT   STATE SERVICE
22/tcp open  ssh

My UFW status:

Status: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere                  
1194/udp                   ALLOW       Anywhere                  
5000/tcp                   ALLOW       Anywhere                  
443/tcp                    ALLOW       Anywhere                  
80/tcp                     ALLOW       Anywhere                  
8443/tcp                   ALLOW       Anywhere                  
OpenSSH (v6)               ALLOW       Anywhere (v6)             
1194/udp (v6)              ALLOW       Anywhere (v6)             
5000/tcp (v6)              ALLOW       Anywhere (v6)             
443/tcp (v6)               ALLOW       Anywhere (v6)             
80/tcp (v6)                ALLOW       Anywhere (v6)             
8443/tcp (v6)              ALLOW       Anywhere (v6)  

And if i will change to 8443:

netstat -plunta | grep 443

tcp        0      0 0.0.0.0:8443            0.0.0.0:*               LISTEN      5031/python3.6 

nmap output (nmap -Pn):

PORT     STATE SERVICE
22/tcp   open  ssh
8443/tcp open  https-alt

The same problem is with 80 port. Don’t have any ideas why is it hapenning.

Hello, @j1nka

As per Bobby’s suggestion it is considered best practice to bind the port (443) on 0.0.0.0:443 as it will give you access to the service from other IP addresses as well.

Let us know how it goes.

Regards, Alex