As I can see, is not wrong, because is very clear how the IP is the PRIVATE IP of the server. AWS informs me that in several screens.
But anyway, I used that IP and the one informed me as BROADCAST in the /sbin/ifconfig command ... nothing.
Amazing
In a matter of fact yes, I did.
IP's are linked as described (LAN IP not belonging to user; only Apache added) and the directadmin.conf with lan_ip=*.*.*.* correctly added and information is correct.
Only this I see weird is subnet mask of the public IP accessed through the Control Panel that...
Yes I think so, is Amazon's AWS.
The control panel at port 222 works really fine. Cant understand what's wrong in there, why sites are not routing to the domain directory or handling web resources.
Everything really looks fine.
Howdy
ports 80 and 443 are back on the list. Yet, no way I can browse the site.
Really hard to deal with this DirectAdmin server. So poor instructions on the console...
Hi smtalk, I saw several posts from you regarding this "APACHE IS FUNCTIONING NORMALLY" problem.
I checked virtual hosts and everything is fine@ httpd.conf
Checked IP's and all Ip's are fine
But running:
netstat -punta | grep LISTEN
I dont see port 80 or 443 on the list.
Any idea on this...