UFW firewall & DigitalOcean Panel

October 17, 2014 2.2k views
sobwoofer8
By:
sobwoofer8

I have configured ufw

22                         ALLOW       Anywhere
80                         ALLOW       Anywhere
21/tcp                     ALLOW       Anywhere
22/tcp                     LIMIT       Anywhere
8080/tcp                   ALLOW       Anywhere
443                        ALLOW       Anywhere
25/tcp                     ALLOW       Anywhere
993                        ALLOW       Anywhere
22                         ALLOW       Anywhere (v6)
80                         ALLOW       Anywhere (v6)
21/tcp                     ALLOW       Anywhere (v6)
8080/tcp                   ALLOW       Anywhere (v6)
443                        ALLOW       Anywhere (v6)
25/tcp                     ALLOW       Anywhere (v6)
993                        ALLOW       Anywhere (v6)

after configuring i'm last control from DigitalOcean Control Panel (no reboot, no vnc ssh .. etc).. but i'm add gateway ip to rule

22 on eth0 ALLOW 188.226.224.1
80 on eth0 ALLOW 188.226.224.1
8080 on eth0 ALLOW 188.226.224.1
443 on eth0 ALLOW 188.226.224.1

now i have control reboot, poweroff, vnc ssh from Control panel
but online graphs still not workin.. how it fix?

And more, when i'm disable ufw and open page Graphs, it still not works some time, and start works after delay..

i'm sorry in my english.. i'm from Ukraine, and speak english very bad)

2 comments
  • asb MOD October 20, 2014

    Are you able to ping the droplet from you local computer?

    If you are unable to enter the web console, please open a support ticket. The console accesses the droplet directly at the hypervisor level. You should be able to bring down networking completely and still access the droplet via the console. So it's unlikely that your firewall rules would lead to this.

  • sobwoofer8 January 23, 2015

    Thanks, but now everything works. Then, the technical work on our server.

Log In to Comment
1 Answer
asb MOD January 26, 2018

This question was answered by @asb:

Are you able to ping the droplet from you local computer?

If you are unable to enter the web console, please open a support ticket. The console accesses the droplet directly at the hypervisor level. You should be able to bring down networking completely and still access the droplet via the console. So it's unlikely that your firewall rules would lead to this.

View the original comment

Reply
Have another answer? Share your knowledge.