Jump to content
satimis

Fail to visit homepage

Recommended Posts

Hi folks,

 

Ubuntu-6.06.1-LAMP-server-amd64

Apache2

Domain: satimis.homelinux.com

(registered with dynsdn.com)

 

Apache is running on this server which is for test purpose.

 

On browser

http://satimis.homelinux.com

https://satimis.homelinux.com

satimis.homelinux.com

http://satimis.homelinux.com:443

https://satimis.homelinux.com:443

satimis.homelinux.com:443

http://satimis.homelinux.com:8080

https://satimis.homelinux.com:8080

satimis.homelinux.com:8080

 

all of them failed to visit the homepage on /var/www/. They only hung there until time out.

 

Both ports 443 and 8080 are open and not stealth. I have them checked on;

http://www.grc.com/

SheildsUp

 

# cat /etc/hosts

127.0.0.1	   localhost.localdomain   localhost
192.168.0.100   sever1.example.com   server1
ubuntu

# The following lines are desirable for IPv6 capable hosts
::1	 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

 

However

//localhost

//localhost:443

//localhost:8080

 

all displayed the homepage.

 

There is no hardware firewall between server and Internet. The server is connected with a CAT5 cable to an ADSL modem. Another end of the ADSL modem is connected to telephone wall socket with a telephone line. The ADSL modem is supplied by ISP and does not require setup.

 

Please help. TIA

 

B.R.

satimis

Share this post


Link to post
Share on other sites

are you absolutely SURE that iptables/firewall is not blocking those ports ?

 

and is apache really listening on those ports ?

 

netstat -an |grep tcp

 

should show you what is listening

Share this post


Link to post
Share on other sites

Hi anyweb,

 

are you absolutely SURE that iptables/firewall is not blocking those ports ?
Whether you meant 80, 443 and 8080?

 

and is apache really listening on those ports ?

 

netstat -an |grep tcp

 

should show you what is listening

$ netstat -an | grep tcp

tcp		0	  0 0.0.0.0:2049			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:932			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:45350		 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:3306		  0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:747			 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:56877		   0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:111		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:6000			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:753			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:46292		 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN
tcp		0	  0 58.152.169.2:53		 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:53			0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:631		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:8888			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:25			  0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:953		   0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:45350		 127.0.0.1:43988		 ESTABLISHED
tcp		0	  0 127.0.0.1:43988		 127.0.0.1:45350		 ESTABLISHED
tcp		0	  0 58.152.169.2:52172	  72.14.253.147:80		ESTABLISHED
tcp		0	  0 58.152.169.2:54508	  72.14.255.147:80		ESTABLISHED
tcp6	   0	  0 :::993				  :::*					LISTEN
tcp6	   0	  0 :::995				  :::*					LISTEN
tcp6	   0	  0 :::2222				 :::*					LISTEN
tcp6	   0	  0 :::110				  :::*					LISTEN
tcp6	   0	  0 :::143				  :::*					LISTEN
tcp6	   0	  0 :::6000				 :::*					LISTEN
tcp6	   0	  0 :::80				   :::*					LISTEN
tcp6	   0	  0 :::8080				 :::*					LISTEN
tcp6	   0	  0 :::25				   :::*					LISTEN
tcp6	   0	  0 ::1:953				 :::*					LISTEN
tcp6	   0	  0 :::443				  :::*					LISTEN

ports 80, 443, 8080 are listened by tcp6.

 

Tks.

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites

yep, meaning that it's listening for ipv6 connections and not 'normal' internet traffic

 

i dont know how you've configured it to do that but it's certaintly not listening on regular port 80

 

checkout my webserver listen properties

 

tcp 0 0 192.168.0.128:80 0.0.0.0:* LISTEN

 

so, are you using ipv6 at all ? if not re-configure your network settings and/or httpd.conf to listen on your IP and not your IPV6

 

cheers

anyweb

Share this post


Link to post
Share on other sites

Hi anyweb,

 

yep, meaning that it's listening for ipv6 connections and not 'normal' internet traffic

 

i dont know how you've configured it to do that but it's certaintly not listening on regular port 80

I haven't configured the network after installing Ubuntu-6.06.1-LAMP-server-amd6.

 

I followed;

http://www.howtoforge.com/perfect_setup_ubuntu_6.06

 

to build this server for test and absorbing knowhow as well. Neither I configured listening ipv6. I even don't fully understand its application.

 

so, are you using ipv6 at all ? if not re-configure your network settings and/or httpd.conf to listen on your IP and not your IPV6

Please advise which file shall I edit;

 

$ cat /etc/hosts

127.0.0.1	   localhost.localdomain   localhost
192.168.0.100   sever1.example.com   server1
ubuntu

# The following lines are desirable for IPv6 capable hosts
::1	 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

 

$ cat /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
 address 127.0.0.1
 netmask 255.0.0.0

auth eth0
iface eth0 inet dhcp

auto dsl-provider
iface dsl-provider inet ppp
provider dsl-provider

# added by pppoeconf
auto eth0
#pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf

 

$ cat /etc/apache2/httpd.conf

# This is here for backwards compatability reasons and to support
#  installing 3rd party modules directly via apxs2, rather than
#  through the /etc/apache2/mods-{available,enabled} mechanism.
#
#LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so

ServerName "localhost"

# httpd.conf listen directive, change "80" to some other value
#Listen 80

No entry on this file.

 

and how to make such a change. TIA

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites

Hi anyweb,

 

Tks for your URL

 

Performed following test;

 

on /etc/modprobe.d/aliases

 

added follows;

alias net-pf-10 ipv6 off

alias net-pf-10 off

alias ipv6 off

#alias net-pf-10 ipv6

 

# network protocols ##########################################################
alias net-pf-1  unix
alias net-pf-2  ipv4
alias net-pf-3  ax25
alias net-pf-4  ipx
alias net-pf-5  appletalk
alias net-pf-6  netrom
alias net-pf-7  bridge
alias net-pf-8  atm
alias net-pf-9  x25
alias net-pf-10 ipv6 off
alias net-pf-10 off
alias ipv6 off
#alias net-pf-10 ipv6
alias net-pf-11 rose
alias net-pf-12 decnet
# 13 NETBEUI
alias net-pf-15 af_key
alias net-pf-16 af_netlink
alias net-pf-17 af_packet
# 18 ASH
alias net-pf-19 af_econet
alias net-pf-20 atm
# 22 SNA
alias net-pf-23 irda
alias net-pf-24 pppoe
alias net-pf-25 wanrouter
alias net-pf-26 llc
alias net-pf-31 bluetooth
....

 

Rebooted PC

 

On browser;

satimis.homelinux.com (still failed displaying webpage)

219.79.147.166 (displayed webpage. IP address on connection)

 

$ sudo ping -c 3 satimis.homelinux.com

Password:
PING satimis.homelinux.com (58.152.181.13) 56(84) bytes of data.

--- satimis.homelinux.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2002ms

 

$ sudo netstat -an |grep tcp

tcp		0	  0 0.0.0.0:2049			0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:3306		  0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:43211		 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:716			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:111		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:6000			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:913			 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:722			 0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:36242		 0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:21			  0.0.0.0:*			   LISTEN
tcp		0	  0 219.79.147.166:53	   0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:53			0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:631		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:8888			0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:25			  0.0.0.0:*			   LISTEN
tcp		0	  0 127.0.0.1:953		   0.0.0.0:*			   LISTEN
tcp		0	  0 0.0.0.0:57499		   0.0.0.0:*			   LISTEN
tcp		0	  0 219.79.147.166:42524	72.14.255.104:80		ESTABLISHED
tcp		0	  0 219.79.147.166:42608	72.14.255.104:80		ESTABLISHED
tcp		0	  0 127.0.0.1:54789		 127.0.0.1:36242		 ESTABLISHED
tcp		0	  0 127.0.0.1:36242		 127.0.0.1:54789		 ESTABLISHED
tcp6	   0	  0 :::993				  :::*					LISTEN
tcp6	   0	  0 :::995				  :::*					LISTEN
tcp6	   0	  0 :::2222				 :::*					LISTEN
tcp6	   0	  0 :::110				  :::*					LISTEN
tcp6	   0	  0 :::143				  :::*					LISTEN
tcp6	   0	  0 :::6000				 :::*					LISTEN
tcp6	   0	  0 :::80				   :::*					LISTEN
tcp6	   0	  0 :::8080				 :::*					LISTEN
tcp6	   0	  0 :::25				   :::*					LISTEN
tcp6	   0	  0 ::1:953				 :::*					LISTEN
tcp6	   0	  0 :::443				  :::*					LISTEN

 

Tks.

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites

This is a firewall issue, attempting to scan that system shows:

 

Host n058152181013.netvigator.com (58.152.181.13) appears to be up ... good.
Interesting ports on n058152181013.netvigator.com (58.152.181.13):
PORT	 STATE	SERVICE
80/tcp   filtered http
443/tcp  filtered https
8080/tcp filtered http-proxy

 

Obviously there is no IPv6 address, so I can't scan those ports, so all ports are filtered.

 

Look into your firewall setup.

Share this post


Link to post
Share on other sites

znx,

 

Obviously there is no IPv6 address, so I can't scan those ports, so all ports are filtered.

 

Look into your firewall setup.

$ sudo iptables -L

Password:
Chain INPUT (policy ACCEPT)
target	 prot opt source			   destination

Chain FORWARD (policy ACCEPT)
target	 prot opt source			   destination
TCPMSS	 tcp  --  anywhere			 anywhere			tcp flags:SYN,RST/S YN tcpmss match 1400:1536 TCPMSS clamp to PMTU

Chain OUTPUT (policy ACCEPT)
target	 prot opt source			   destination

 

$ sudo iptables -L -n -v

Chain INPUT (policy ACCEPT 10142 packets, 9083K bytes)
pkts bytes target	 prot opt in	 out	 source			   destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target	 prot opt in	 out	 source			   destination
0	 0 TCPMSS	 tcp  --  *	  ppp0	0.0.0.0/0			0.0.0.0/0		   tcp flags:0x06/0x02 tcpmss match 1400:1536 TCPMSS clamp to PMTU

Chain OUTPUT (policy ACCEPT 9482 packets, 1410K bytes)
pkts bytes target	 prot opt in	 out	 source			   destination

It is quite strange to me. I can ping 219.79.144.63 which is the IP address on connection. But failed to ping "satimis.homelinux.com"

 

On browser 219.79.144.63 can browse the webpage and "satimis.homelinux.com" failed.

 

I login DYNDNS.COM and found the IP there has been updated 219.79.144.63. It seems DYNDNS.COM has not redirected satimis.homelinux.com to 219.79.144.63

 

My server is off if I'm not working on it.

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites
On browser;

satimis.homelinux.com (still failed displaying webpage)

219.79.147.166 (displayed webpage. IP address on connection)

 

$ sudo ping -c 3 satimis.homelinux.com

CODE

 

Password:

PING satimis.homelinux.com (58.152.181.13) 56(84) bytes of data.

 

--- satimis.homelinux.com ping statistics ---

3 packets transmitted, 0 received, 100% packet loss, time 2002ms

 

something about that ^ doesnt look right

 

which ip should you be, the 58 one or the 219 one ?

 

sort that out first then see if you can fix this issue

 

cheers

 

anyweb

Share this post


Link to post
Share on other sites

Hi anyweb,

 

something about that ^ doesnt look right

 

which ip should you be, the 58 one or the 219 one ?

 

sort that out first then see if you can fix this issue

58.152.181.13 is the IP address of satimis.homelinux.com on DYNDNS.COM/ORG

 

219.79.147.166 was the IP address of the server on connection. This address was asigned by ISP.

 

Now the IP address of the server is 58.152.160.184 because I just started the server.

 

I logon DYNDNS.COM/ORG website and found the IP address of the server on their website has been updated to 58.152.160.184. It is the exact IP address of the server.

 

Throughout struggling on these few days I suspect DYNDNS.COM/ORG has not redirected all requests on 58.152.181.13 to the running IP address of the server. Otherwise why it was always hanging and pointing at 58.152.181.13 without response.

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites

ok well look at this

 

Pinging satimis.homelinux.com [58.152.181.13] with 32 bytes of data:

 

which is the wrong ip...

 

so login manually to dyndns.org and update the ip to the correct one, manually

 

then i will test it again.,.,,.,

 

cheers

anyweb

Share this post


Link to post
Share on other sites

Hi anyweb,

 

Sorry I just rebooted the server.

 

The current IP address is "218.250.34.249", same on DYNDNS.COM/ORG

 

& sudo ping -c 3 218.250.34.249

Password:
PING 218.250.34.249 (218.250.34.249) 56(84) bytes of data.
64 bytes from 218.250.34.249: icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from 218.250.34.249: icmp_seq=2 ttl=64 time=0.033 ms
64 bytes from 218.250.34.249: icmp_seq=3 ttl=64 time=0.034 ms

--- 218.250.34.249 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.033/0.036/0.043/0.008 ms

 

$ sudo ping -c 3 58.152.181.13

PING 58.152.181.13 (58.152.181.13) 56(84) bytes of data.

--- 58.152.181.13 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2013ms

Always failed.

 

I'll keep the server running. If there is a change on IP address. I'll post.

 

Tks.

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites

Hi anyweb,

 

I discovered the trick.

 

$ sudo ping -c 3 www.satimis.homelinux.com

PING satimis.homelinux.com (58.152.183.105) 56(84) bytes of data.
64 bytes from n058152183105.netvigator.com (58.152.183.105): icmp_seq=1 ttl=27 time=35.9 ms
64 bytes from n058152183105.netvigator.com (58.152.183.105): icmp_seq=2 ttl=27 time=36.3 ms
64 bytes from n058152183105.netvigator.com (58.152.183.105): icmp_seq=3 ttl=27 time=35.0 ms

--- satimis.homelinux.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2401ms
rtt min/avg/max/mdev = 35.045/35.761/36.313/0.573 ms

 

Then it worked. It needs www as prefix.

 

Please advise what other tests I have to continue. TIA

 

 

B.R.

satimis

Share this post


Link to post
Share on other sites

Hi anyweb,

 

"satimis.homelinux.com" may have problem.

 

On browser running "satimis.homelinux.com"/"www.satimis.homelinux.com" can't display the homepage.

 

 

I have registered another free domain "satimis.freeddns.com"

 

$ sudo ping -c 3 satimis.freeddns.com

Password:
PING satimis.freeddns.com (220.246.238.244) 56(84) bytes of data.
64 bytes from n220246238244.netvigator.com (220.246.238.244): icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from n220246238244.netvigator.com (220.246.238.244): icmp_seq=2 ttl=64 time=0.033 ms
64 bytes from n220246238244.netvigator.com (220.246.238.244): icmp_seq=3 ttl=64 time=0.034 ms

--- satimis.freeddns.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2015ms
rtt min/avg/max/mdev = 0.033/0.033/0.034/0.004 ms

 

On browser running "satimis.freeddns.com" displayed the homepage.

 

B.R.

satimis

Share this post


Link to post
Share on other sites

hi

 

can you please join us on IRC to resolve this

 

EFNET server, join #linux-noob

 

cheers

anyweb

Share this post


Link to post
Share on other sites

Hi anyweb,

 

can you please join us on IRC to resolve this
Yes, please advise how to proceed. I'm ready.

 

Besides my server is not up round the clock. It is only up on testing.

 

Please advise if any change made on my server so that I can learn. Tks

 

EFNET server, join #linux-noob

What is it? TKs.

 

My server can be visited on browser by running;

 

satimis.freeddns.com:8080

 

ISP blocks port 80.

 

It worked on my friend's WinXP box. Tks

 

B.R.

satimis

Share this post


Link to post
Share on other sites
ISP blocks port 80.

 

uh, why didn't you point out this vital information at the START of this thread....

 

if port 80 is blocked by your ISP then you'll NEVER be able to browse http://yoursite.yourip.com on port 80...

 

 

 

ok,

 

if you want further help then please get an IRC client, in windows try http://www.mirc.com

 

in linux use xchat

 

then join the EFNET server and join our channel for live support #linux-noob

 

cheers

anyweb

Share this post


Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...