Question

Apache Setup IPv6 only - Vodafone DS Lite

Posted on April 22, 2025
Apache
Asked by 30ddab6038c044188d489290785dcb

Hi all,

after successfully installing Nextcloud on my Raspberry PI and accessing it locally, I have some issues configuring my Apache2 Webserver to access from externally.

My internet provider is Vodafone and there is only DS-Lite available. So I read that everything must be configured by IPv6. I have registered a public domain via No-IP and entered my IPv6 address. I have also extended the sites-available page:

<VirtualHost [::]:80>
   ServerAdmin xx
   ServerName xx
   ServerAlias xx
   DocumentRoot /var/www/html

<Directory "/var/www/html">
    AllowOverride None
    Require all granted
</Directory>

   ErrorLog ${APACHE_LOG_DIR}/xx.log
   CustomLog ${APACHE_LOG_DIR}/xx.log combined

</VirtualHost>

My Ports.conf looks like this:

Listen [::]:80
Listen [::]:443

<IfModule ssl_module>
        Listen 443
</IfModule>

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

In the FritzBox config I have openend the ports 80 and 443 for the IPv6 address.

Creating a certificate via certbot also fails with connections refuse, .well-know issue What else needs to be configured for only Ipv6 access?

Thanks in advance!

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev

Site Moderator

• April 23, 2025

Hi there,

You need to make sure your domain’s AAAA record points to your current IPv6 address, and double-check that your FritzBox is actually allowing external IPv6 traffic on ports 80 and 443.

Some ISPs, including Vodafone, might block incoming traffic by default even over IPv6, so it’s worth reaching out to them to confirm.

As for the Certbot issue with .well-known, that’s pretty common when HTTP access isn’t fully reachable. You might want to try the DNS challenge method instead, it doesn’t rely on incoming HTTP requests and usually works better in setups like yours.

- Bobby