can't access own site from within Linode ssh shell?

What does "apache2ctl -S" report?

For what it's worth, your site is reachable OK via IPv4, but not by IPv6:

rtucker@witte:~$ curl -I -H "Host: ingber.com" http://173.255.212.226
HTTP/1.1 200 OK
Date: Sun, 22 May 2011 18:06:03 GMT
Server: Apache/2.2.17 (Ubuntu)
Last-Modified: Sun, 22 May 2011 14:27:14 GMT
ETag: "1786d1-107e6-4a3de26b05480"
Accept-Ranges: bytes
Content-Length: 67558
Vary: Accept-Encoding
Content-Type: text/html

rtucker@witte:~$ curl -g -I -H "Host: ingber.com" "http://[2600:3c01::f03c:91ff:fe93:e6f3]/"
HTTP/1.1 404 Not Found
Date: Sun, 22 May 2011 18:06:11 GMT
Server: Apache/2.2.17 (Ubuntu)
Vary: Accept-Encoding
Content-Type: text/html; charset=iso-8859-1

So I'm guessing your VirtualHosts aren't paying attention to the IPv6 address…

Hi. My apache report is:

11:55:32am @lin.ingber:~% apache2ctl -S

VirtualHost configuration:

173.255.212.226:80 is a NameVirtualHost

default server lin.ingber.com (/etc/apache2/sites-enabled/000-default:2)

port 80 namevhost lin.ingber.com (/etc/apache2/sites-enabled/000-default:2)

wildcard NameVirtualHosts and default servers:

default:443 hit-nxdomain.opendns.com (/etc/apache2/sites-enabled/default-ssl:2)

Syntax OK

Support insists my site is registered properly under both IPv4 and IPv6. ping6 gives that info OK. All the tests on

http://library.linode.com/networking/ipv6

seem to work just fine. I assume you mean that I must add some other apache-specific into? I could not find any IPv6 info under /etc/apache2/ ?

Lester

Here's a good howto on running a dual stack Apache Virtual Host

http://www.cyberciti.biz/faq/ipv6-apach … -tutorial/">http://www.cyberciti.biz/faq/ipv6-apache-configuration-tutorial/

Thanks for the ipv6 URL. I had seen that and have tried changing

/etc/apache2/ports.config

/etc/apache2/sites-available/default

/etc/apache2/sites-available/default-ssl

(soft links under /etc/apache-enabled/ to these which work fine under IPv4 only)

I created

ports.conf ports.conf.ipv4 ports.conf.ipv6

default default-ssl.ipv4 default.ipv4

default-ssl default-ssl.ipv6 default.ipv6

to quickly copy over ipv4 or ipv6 (dual) and then test with

/etc/init.d/apache2 restart

However, what I have done does not work.

ports.config.ipv6 just has added:

Listen [::]:80

Listen [::]:443

defaults.ipv6 has added an additional section

… (repeat info under )

defaults-ssl.ipv6 has added an additional section

… (repeat info under which is just in default-ssl.ipv6 since

I found that did not work)

With the .ipv6 files I get:

12:49:38pm @lin.ingber:/etc/apache2/sites-available% /etc/init.d/apache2 restart

• Restarting web server apache2

[Sun May 22 12:49:42 2011] [error] (EAI 2)Name or service not known: Failed to resolve server name for 2600:3c01::f03c:91ff:fe93:e6f3 (check DNS) – or specify an explicit ServerName

[Sun May 22 12:49:42 2011] [error] (EAI 2)Name or service not known: Failed to resolve server name for 2600:3c01::f03c:91ff:fe93:e6f3 (check DNS) – or specify an explicit ServerName

… waiting [Sun May 22 12:49:43 2011] [error] (EAI 2)Name or service not known: Failed to resolve server name for 2600:3c01::f03c:91ff:fe93:e6f3 (check DNS) – or specify an explicit ServerName

[Sun May 22 12:49:43 2011] [error] (EAI 2)Name or service not known: Failed to resolve server name for 2600:3c01::f03c:91ff:fe93:e6f3 (check DNS) – or specify an explicit ServerName

(98)Address already in use: make_sock: could not bind to address [::]:80

(98)Address already in use: make_sock: could not bind to address [::]:443

(98)Address already in use: make_sock: could not bind to address 0.0.0.0:443

no listening sockets available, shutting down

Unable to open logs

Action 'start' failed.

The Apache error log may have more information.

…fail!

Lester

While I would like to get ipv6 working with apache2, I do not see how or why this is relevant to the main issue under what I posted: Why can't I reach

http://ingber.com

from within my Linode shell using just my previous ipv4 settings?

Thanks.

Lester

Re ipv6 settings, see

http://ubuntuforums.org/showthread.php?t=935955

where it is claimed that no changes have to be made in Ubuntu servers? As remarked there, my ifconfig returns site info OK (with my old "ipv4" setttings):

1:32:36pm @lin.ingber:~% ifconfig -a

eth0 Link encap:Ethernet HWaddr f2:3c:91:93:e6:f3

inet addr:173.255.212.226 Bcast:173.255.212.255 Mask:255.255.255.0

inet6 addr: 2600:3c01::f03c:91ff:fe93:e6f3/64 Scope:Global

inet6 addr: fe80::f03c:91ff:fe93:e6f3/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:121319 errors:0 dropped:0 overruns:0 frame:0

TX packets:104177 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:26774266 (26.7 MB) TX bytes:50850013 (50.8 MB)

Interrupt:227

Still, I must be missing something if I get no response from

http://[2600:3c01::f03c:91ff:fe93:e6f3]

@ingber:

While I would like to get ipv6 working with apache2, I do not see how or why this is relevant to the main issue under what I posted: Why can't I reach

http://ingber.com

from within my Linode shell using just my previous ipv4 settings?

If both IPv6 and IPv4 are available, IPv6 will be used. Your Linode has IPv6, so it uses IPv6 to reach your site. If you remove the AAAA record on ingber.com until you get this figured out, it will start working OK.

You can probably get Apache to do the right thing by adding, to ports.conf:

NameVirtualHost [2600:3c01::f03c:91ff:fe93:e6f3]:80

And on each of your VirtualHosts, change the directive to:

<virtualhost 173.255.212.226:80="" [2600:3c01::f03c:91ff:fe93:e6f3]:80=""></virtualhost>

It seems the info on

http://ubuntuforums.org/showthread.php?t=935955

is correct.

That is, without any changes in my ipv4 settings,

elinks https:[2600:3c01::f03c:91ff:fe93:e6f3]

works fine (ssl)

I still have the problem with

elinks http:[2600:3c01::f03c:91ff:fe93:e6f3]

which fails because it cannot find

http://www.ingber.com

just like it cannot work with

http://www.ingber.com

but works fine with (ssl)

https://www.ingber.com

Thanks.

Lester

hoopycat:

Yes, I made the simple changes you suggested, and now http://www.ingber.com can be accessed from my Linode shell, for the reasons you stated re trying to first access my ipv6 records.

Everything seems to working OK, e.g., being able to access domain.com as well as ipv4 and ipv6 addresses under both http and https.

I'm glad the "little" problem of not being able to access http://domian.com under my Linode shell came up. It led to a more robust apache2 server.

Thanks.

Lester

Yup, looks good from here via IPv6 as well!

(It wasn't until a little while ago on IRC that I learned could take multiple arguments, so whoever mentioned that gets the credit!)