unable to connect site to different port
Posted
by
JohnMerlino
on Server Fault
See other posts from Server Fault
or by JohnMerlino
Published on 2012-12-10T20:32:18Z
Indexed on
2012/12/10
23:06 UTC
Read the original article
Hit count: 153
I have a domain was registered at godaddy named http://mysite.com/. I logged into godaddy and I went to All Products > Domains > Domain Management. I clicked on the appropriate domain and it took me to the Domain Details page. I clicked Launch under DNS Manager and it took me to the Zone File Editor. I noticed that notify.mysite.com was pointing to an IP address pointing to a dead server, so I switched it to an operating server. Then I pinged the domain to see where it was pointing to and it was correctly pointing to the working server. So I copied the default configuration under sites-available: sudo cp default notify.mysite.com. And then I made some edits to it to have it point to a different document root to serve files at a different port:
Listen 1740
Listen 64.135.xx.xxx:1740 #I also tried this as well: NameVirtualHost 64.135.xx.xxx:1740
<VirtualHost 64.135.xx.xxx:1740>
ServerAdmin [email protected]
ServerName notify.mysite.com
DocumentRoot /var/www/test/public
<Directory /var/www/test/public>
Order allow,deny
allow from all
</Directory>
ErrorLog ${APACHE_LOG_DIR}/error.log
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>
Then I enabled the virtual host. Then I went to the document root and added an index.html file with some text in it. Then I restarted apache. The restart gave no errors.
Then I type the correct domain in URL:
http://notify.mysite.com:1740/
and I get:
Oops! Google Chrome could not connect to notify.mysite.com:1740
Somehow it took out all my other sites. Now even the ones that were responding on port 80 are no longe responding, even though I did not touch the virtual hosts for them.
I get this message now:
Oops! Google Chrome could not connect to mysite.com
However, ping responds:
ping mysite.com PING mysite.com (64.135.12.134): 56 data bytes 64 bytes from 64.135.12.134: icmp_seq=0 ttl=49 time=20.839 ms 64 bytes from 64.135.12.134: icmp_seq=1 ttl=49 time=20.489 ms
The result of telnet:
$ telnet guarddoggps.com 80 Trying 64.135.12.134... telnet: connect to address 64.135.12.134: Connection refused telnet: Unable to connect to remote host
© Server Fault or respective owner