Tag Info

New answers tagged

0

Almost every access list is by default ended with deny all all. When you enable ufw width any rules to allow some traffic all is in deny state. Status: active To Action From -- ------ ---- 69 ALLOW Anywhere 53 ALLOW Anywhere 22 ...


0

There is a /usr/share/ufw/check-requirements script that checks for everything needed for ufw to work. You'll get hints about what's missing. ufw is not meant to work without the full iptables/netfilter build in the kernel or loaded by modules. If you can't build a new kernel, you're in for some trouble. The post you linked tries to go around these ...


0

Well, I do believe that Adobe stuff (like photoshop) has a bad reputation of working with Wine. The same thing happens with iTunes. The latest compatible version of iTunes that works with Wine is version 8. 8! THE LATEST RELEASE IS LIKE, 12.1.1!!!!! I would suggest trying an earlier version of Master Collection, and if that doesn't work, try looking around ...


0

+1 for Simon's answer above. I was looking for that piece of information hard. I want to highlight the answer to make it easier to notice: sudo ufw show added


1

Solution By MadHatter, http://serverfault.com/questions/666696/ubuntu-apache2-cannot-open-port-443/666713?noredirect=1#comment814308_666713 don't know much about ufw, but in this case I think it will be completely ineffective on INPUT traffic, because the rules that implement it come after a blanket DROP (the fifth rule in the INPUT chain). You can see ...


1

Remove the IP Address from NameVirtualHost 92.243.16.14:443 (you practically have binded all VirtualHosts on that IP Address) in order to listen on port 443 on all network interfaces (IPs): NameVirtualHost *:443 Then you can differentiate domain by binding the VirtualHost on a specific IP address like so: VirtualHost 1.2.3.4:443 VirtualHost 1.2.3.5:443 ...


0

Apache is running and port 443 is also open, here you need to check for the IP 92.243.16.14 is configured or not using ifconfig command. because 443 is running on default interface.


0

I ended up figuring this out. It wasn't directly a firewall issue. I have two NICs, one for the LAN and another for the DMZ, to which the WAN IP is NAT'ed. The default route was over the LAN. When receiving packets from the internet, the server tried to respond via the default route on the LAN. Disconnecting from the LAN enabled the services to communicate ...


0

I had a problem that I can not access a server on my hosting machine (Ubuntu 14.04 64 Bit) from a guest windows machine by VMWare Player. I had been around for like a two days searching for a network solution while the problem was all about firewall. I decided that it is all about firewall and I tried to see how to stop the firewall, I tried this solution ...


0

You can use gufw, which is an gui frontend for ufw. To install it, run sudo apt-get install gufw


1

From what I can tell dnsmasq uses port 53 tcp/udp, as well as port 67/udp dhclient by default uses port 68/udp So a generic way to get this setup would be sudo ufw allow to any port 53 sudo ufw allow to any port 67 proto udp sudo ufw allow to any port 68 proto udp Or if you want to just open these ports for a particular IP address (not sure if you ...



Top 50 recent answers are included