Ubuntu default page not redirecting to https

My domain is: dominikruczajewski.pl

I ran this command: http://www.dominikruczajewski.pl

It produced this output: apache2 ubuntu default page

My web server is (include version): Apache/2.4.29 (Ubuntu)

The operating system my web server runs on is (include version): Ubuntu 18.04 LTS bionic

My hosting provider, if applicable, is: nazwa.pl

I can login to a root shell on my machine (yes or no, or I don’t know): yes

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0

Issue description:
Please see detailed case ASK UBUNTU

1 Like

Hi @MrDominikku

checking your domain there is a different result - http over port 443, Grade Q - https://check-your-website.server-daten.de/?q=dominikruczajewski.pl

http + port 80 redirects to https, but https doesn't work, instead, there is a typical error:

SendFailure - The underlying connection was closed: An unexpected error occurred on a send.

So the tool checks http over port 443 - and there is the default Apache page.

Looks like you have a mix of wrong configurations and a wrong port forwarding.

Must be

extern port 80 -> intern port 80, not port 443
extern port 443 -> intern port 443.

If this is checked, share

apachectl -S
1 Like

Hey @JuergenAuer thanks for interest!

Not sure if I am following with external/internal port. Does VirtualHost are wrong configures?

According to /etc/apache2/ports.conf

Listen 80

<IfModule ssl_module>
        Listen 443

<IfModule mod_gnutls.c>
        Listen 443

My firewall status

22/tcp                     ALLOW       Anywhere
80/tcp                     ALLOW       Anywhere
443/tcp                    ALLOW       Anywhere
5432                       ALLOW       Anywhere
5432/tcp                   ALLOW       Anywhere
22/tcp (v6)                ALLOW       Anywhere (v6)
80/tcp (v6)                ALLOW       Anywhere (v6)
443/tcp (v6)               ALLOW       Anywhere (v6)
5432 (v6)                  ALLOW       Anywhere (v6)
5432/tcp (v6)              ALLOW       Anywhere (v6)

and apachectl -S

VirtualHost configuration:
*:443                  dominikruczajewski.pl (/etc/apache2/sites-enabled/django_project-le-ssl.conf:2)
*:80                   is a NameVirtualHost
         default server dominikruczajewski.pl (/etc/apache2/sites-enabled/django_project-le-ssl.conf:59)
         port 80 namevhost dominikruczajewski.pl (/etc/apache2/sites-enabled/django_project-le-ssl.conf:59)
                 alias www.dominikruczajewski.pl
         port 80 namevhost dominikruczajewski.pl (/etc/apache2/sites-enabled/django_project.conf:1)
                 alias www.dominikruczajewski.pl
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex watchdog-callback: using_defaults
Mutex rewrite-map: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
PidFile: "/var/run/apache2/apache2.pid"
User: name="www-data" id=33
Group: name="www-data" id=33

Why there are port 80 vHosts in the le-ssl config file? Remove these.

Every combination of port and domain name must be unique.


looks bad too. May be a duplicated Listen. Remove the second block.


django_project-le-ssl.conf was created from certbot certificate, I thought it’s required. Initial django_project.conf contained only vhost with port 80

Removing vhost resolved issue. Thanks!


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.