I fairly new to this. I've setup a Ubuntu server using the Perfect setup docs and I installed ISPConfig. I can get to the admin screen if I go through https://my.static.WAN.IP.address:81, but I can't if I try https://www.my.domain:81. I've checked my host file and everything appears to be setup correctly there. I made sure the router has access to that port. Any other ideas?
firewall? Can you check to see that port 81 is not blocked by a firewall? Also, www.my.domain.com seems unusual to me. http://my.domain.com seems more like what I am used to seeing.
Port 81 isn't blocked by a firewall. If it wasn't it wouldn't let me resolve using the WAN IP address. As far as the domain name, it was more for illustrative purposes. The WAN IP resolves, but the domain name gives me a "problem loading page" error message.
Does my.static.WAN.IP.address and www.my.domain point to the same IP address? ISPConfig listens on all IP addresses on your server, so it is not domain specific as long as both domains point to your server IP.
I'm not sure I understand the question or more to the point how would I be able to tell? Here is how I'm setup. I have the Ubuntu server set behind a router on my network. I currently have all web traffic pointed to the server via the NAT in the router. I registered a domain with GoDaddy and have it forwarded to the static IP address that is provided by my cable company. If I open a browser window and type the static IP address specifying port 81 it pulls up ISPConfig. If I type in the domain name I registered I get an error message. Just in case here are the results when I ran netstat -tap Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:mysql *:* LISTEN 8184/mysqld tcp 0 0 *:81 *:* LISTEN 6532/ispconfig_http tcp 0 0 www.bandbtech.ne:domain *:* LISTEN 6768/named tcp 0 0 localhost:domain *:* LISTEN 6768/named tcp 0 0 *:smtp *:* LISTEN 28373/master tcp 0 0 localhost:953 *:* LISTEN 6768/named tcp6 0 0 *:imaps *:* LISTEN 7849/couriertcpd tcp6 0 0 *op3s *:* LISTEN 7752/couriertcpd tcp6 0 0 *op3 *:* LISTEN 7689/couriertcpd tcp6 0 0 *:imap2 *:* LISTEN 7794/couriertcpd tcp6 0 0 *:www *:* LISTEN 22520/apache2 tcp6 0 0 *:ftp *:* LISTEN 27035/proftpd: (acc tcp6 0 0 *:ssh *:* LISTEN 4352/sshd tcp6 0 0 *:smtp *:* LISTEN 28373/master tcp6 0 0 ip6-localhost:953 *:* LISTEN 6768/named tcp6 0 0 *:https *:* LISTEN 22520/apache2 tcp6 0 52 www.bandbtech.net:ssh www.bandbtech.net:3934 ESTABLISHED591/sshd: mdbrie01 root@www:/home/mdbrie01# Active Internet connections (servers and established)
Can you do a : telnet www.yourdomain.com 81 Does it connect? the resolve thing is outside your control, if the dns is well configurated then it will resolve the name, even when the server is down..
