Reputation
2,146
Top tag
Next privilege 2,500 Rep.
Create tag synonyms
Badges
9 48 81
Impact
~472k people reached

Apr
12
accepted fwbuilder/iptables manually scripted + autogenerated rules at startup?
Apr
8
asked Master/Slave DNS setup vs. rsync'ed DNS servers
Apr
5
accepted Firewalls: What is the difference between Policy, NAT and Routes?
Apr
5
asked PhpLdapAdmin - How to disable a user/uid?
Apr
5
asked fwbuilder/iptables manually scripted + autogenerated rules at startup?
Apr
5
comment Firewalls: What is the difference between Policy, NAT and Routes?
Let me get this straight: If I wanted someone on the outside to access SSH or http on a specific internal machine, I would use NAT? If our network had two ISP connections both connected to the Firewall, and I wanted certain internal computers to connect to the internet via ISP A and others to use ISP B, I would use Routes? And if I wanted to just control whether certain services that pass through the router are accepted or denied, I use Policy?
Apr
5
awarded  Critic
Apr
5
asked Firewalls: What is the difference between Policy, NAT and Routes?
Apr
4
accepted Cannot delete old NFS directory: Device or resource busy
Apr
4
accepted ls returns nothing only in certain directories
Apr
4
accepted rdiff-backup is taking longer and longer every time it runs
Apr
4
accepted SVN/Trac - OPTIONS reponse did not include requested activity collection set
Apr
4
accepted ssh auto-forward?
Apr
4
asked Bacula alternative?
Apr
4
comment Basic Apache setup is not seeing my site
The only process is shows that is using port 80 is the very httpd process that I'm starting and stopping. My next try is to just disable or move all the .conf's out of /etc/httpd/conf.d/ and add them back in one at a time to see which one is screwing this up.
Apr
1
comment Basic Apache setup is not seeing my site
/etc/hosts is system default. No issues there. iptables doesn't show anything about blocking port 80. I added Listen <ip address of mysite.ourdomain.com but when restarting apache I get (98)Address already in use: make_sock: could not bind to address x.x.x.x:80 no listening sockets available, shutting down
Apr
1
comment Basic Apache setup is not seeing my site
Yup, the include is already there. It's obviously working because the CRM that is also running on this server is declared in a .conf and it's getting picked up just fine.
Apr
1
comment Basic Apache setup is not seeing my site
Ya I moved it in there w/o any luck. In httpd.conf I changed NameVirtualHost *:80 to NameVirtualHost mysite.ourdomain.com:80 and then the directive at the bottom of httpd.conf is <VirtualHost mysite.ourdomain.com:80>
Apr
1
comment Basic Apache setup is not seeing my site
I see Include /etc/httpd/conf.d/*.conf in httpd.conf and it is not commented out. And what do you mean regarding the NameVirtualHost? In httpd.conf near the bottom I see NameVirtualHost *:80. Is that supposed to say NameVirtualHost mysite.mydomain.com:80 ?
Apr
1
comment Basic Apache setup is not seeing my site
That didn't make a difference. Any other ideas?