debian host setup

expectationlost

are these instructions right been trying for 3 weeks to just get the basic setup https://help.blacknight.com/entries/22972193-Setting-up-Apache-in-Debian

mneylon

Which part of it is causing you issues?

expectationlost

im not sure

when i stop apace and start i get

Starting web server: apache2(99)Cannot assign requested address: make_sock: could not bind to address [2001:db8::1]:80
no listening sockets available, shutting down
Unable to open logs
Action 'start' failed.
The Apache error log may have more information.

mneylon

What do you have in your VirtualHost config?

Bear in mind that the IP addresses given in that article are examples only and should not be used in production

expectationlost

# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default
# This is also true if you have upgraded from before 2.2.9-3 (i.e. from
# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
# README.Debian.gz

#NameVirtualHost *:80
#Listen 80

# Virtual Hosting IP
Listen 46.22.130.226:80
Listen [2001:DB8::1]:80

# ssl.example.com
Listen 46.22.130.226:80
Listen [2001:DB8::2]:80

# Parking Page
Listen 46.22.130.226:80
Listen [2001:DB8::1]:80

#<IfModule mod_ssl.c>
    # If you add NameVirtualHost *:443 here, you will also have to change
    # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
    # to <VirtualHost *:443>
    # Server Name Indication for SSL named virtual hosts is currently not
    # supported by MSIE on Windows XP.
   # Listen 443
#</IfModule>

<IfModule mod_gnutls.c>
    Listen 443
</IfModule>


# Set the virtual hosting ip to act on the Host: header
# This should only be done on ips where you plan on having
# multiple different sites.
NameVirtualHost 46.22.130.226:80
NameVirtualHost [2001:DB8::1]:80
<IfModule mod_ssl.c>
    # If the mod_ssl library is loaded, get apache to listen on port 443 for the SSL site.
    Listen 46.22.130.226:443
    Listen [2001:DB8::2]:443
</IfModule>

mneylon

Remove the IPv6 bit from that and it should work

expectationlost

so the instructions were wrong and misleading!

mneylon

expectationlost wrote: »

so the instructions were wrong and misleading!

No they weren't but I'll get someone to clarify them

expectationlost

Blacknight wrote: »

No they weren't but I'll get someone to clarify them

doesn't really clarifiy it be better to say don't use the [2001:DB8::1]:80 bit unless IPV6 something something

gerryk

expectationlost wrote: »

doesn't really clarifiy it be better to say don't use the [2001:DB8::1]:80 bit unless IPV6 something something

I would have thought that it is self evident that you don't configure an IPv6 listener if you don't have IPv6 configured.

expectationlost

gerryk wrote: »

I would have thought that it is self evident that you don't configure an IPv6 listener if you don't have IPv6 configured.

do you ever use something 
like

[font=Arial, Helvetica, sans-serif]Listen 192.0.2.2:80 (and)[/font]
[font=Arial, Helvetica, sans-serif]Listen [2001:DB8::2]:80[/font]

gerryk

Yes... that's how you configure Apache dual-stack listener. I have done testing of this functionality, but not on the open internet, as few hosting providers have IPv6.

To clarify, dual stack is where your server has both IPv4 and IPv6 configured at the same time. There are few scenarios where you would have IPv6 only.

The likelihood is that you're only going to need the first line (or something like it) in your case.

expectationlost

gerryk wrote: »

Yes... that's how you configure Apache dual-stack listener. I have done testing of this functionality, but not on the open internet, as few hosting providers have IPv6.

To clarify, dual stack is where your server has both IPv4 and IPv6 configured at the same time. There are few scenarios where you would have IPv6 only.

The likelihood is that you're only going to need the first line (or something like it) in your case.

so why didn't they make that clear, the instruction at the top of the page don't make that clear at all.

mneylon

expectationlost wrote: »

so why didn't they make that clear, the instruction at the top of the page don't make that clear at all.

Our network has both IPv4 and IPv6 so both our own sites and those of clients with dedicated servers or colocation can and do use dual stack setups.

expectationlost

im telling you its still not clear maybe you might like to listen to your customer