Certificates not showing up and No secure connection

Help
1

My domain is: igw.news
There are 9 others with certificates on the same server. IP: 5.101.140.50

I ran this command:
Browsed on Chrome to igw.news

It produced this output:

This site can’t provide a secure connection

igw.news sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

My web server is (include version):
Server version: Apache/2.4.41 (Ubuntu)
Server built: 2021-10-14T16:24:43

The operating system my web server runs on is (include version):
Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-90-generic x86_64)

My hosting provider, if applicable, is:
Dedicated Server on UKServers

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

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 c or certbot-auto --version if you're using Certbot):
certbot 1.21.0

Hi,
Firstly, thanks for providing this great resource!

I believe that I have set up the Letsencrypt certificates using certbot for the following domains:
1: bot10x.com
2: www.bot10x.com
3: cybxpert.com
4: www.cybxpert.com
5: expressresponse.net
6: www.expressresponse.net
7: gldn.page
8: www.gldn.page
9: igw.news
10: www.igw.news
11: pdg.reviews
12: www.pdg.reviews
13: reviewed.page
14: www.reviewed.page
15: smartbiz.pro
16: www.smartbiz.pro
17: ukncsa.com
18: www.ukncsa.com
19: yel.page
20: www.yel.page

But maybe I've made some errors !

It may best to focus on one domain first and I'll apply any corrections to the others.

Looking at igw.news

Browsing the topics on this forum, I found and used some utilities like:
transparencyreport.google.com and
check-your-website.server-daten.de
(which raised more questions)

First, may I just check that I have set up the apache server correctly.

In my /etc/apache2/sites-available I have these files:

-rw-r--r-- 1 root root 435 Nov 16 11:18 bot10x.com.conf
-rw-r--r-- 1 root root 475 Nov 15 18:56 bot10x.com-le-ssl.conf
-rw-r--r-- 1 root root 472 Nov 16 08:45 chitchatmedia.net.conf
-rw-r--r-- 1 root root 517 Nov 15 19:12 chitchatmedia.net-le-ssl.conf
-rw-r--r-- 1 root root 447 Nov 16 11:19 cybxpert.com.conf
-rw-r--r-- 1 root root 487 Nov 15 18:58 cybxpert.com-le-ssl.conf
-rw-r--r-- 1 root root 6338 Apr 13 2020 default-ssl.conf
-rw-r--r-- 1 root root 489 Nov 16 11:19 expressresponse.net.conf
-rw-r--r-- 1 root root 529 Nov 15 18:59 expressresponse.net-le-ssl.conf
-rw-r--r-- 1 root root 430 Nov 16 11:19 gldn.page.conf
-rw-r--r-- 1 root root 470 Nov 15 08:26 gldn.page-le-ssl.conf
-rw-r--r-- 1 root root 423 Nov 16 11:20 igw.news.conf
-rw-r--r-- 1 root root 463 Nov 15 13:25 igw.news-le-ssl.conf
-rw-r--r-- 1 root root 442 Nov 16 11:20 pdg.reviews.conf
-rw-r--r-- 1 root root 482 Nov 15 19:00 pdg.reviews-le-ssl.conf
-rw-r--r-- 1 root root 454 Nov 16 11:20 reviewed.page.conf
-rw-r--r-- 1 root root 494 Nov 15 18:55 reviewed.page-le-ssl.conf
-rw-r--r-- 1 root root 267 Nov 16 11:21 smartbiz.pro.conf
-rw-r--r-- 1 root root 435 Nov 16 11:22 ukncsa.com.conf
-rw-r--r-- 1 root root 475 Nov 15 19:12 ukncsa.com-le-ssl.conf
-rw-r--r-- 1 root root 423 Nov 16 11:22 yel.page.conf
-rw-r--r-- 1 root root 463 Nov 15 19:02 yel.page-le-ssl.conf

and the igw.news.conf looks like:

<VirtualHost *:80>
ServerAdmin admin@igw.news
ServerName igw.news
ServerAlias www.igw.news
DocumentRoot /var/www/igw.news/html
ErrorLog ${APACHE_LOG_DIR}/eror.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
RewriteEngine on
RewriteCond %{SERVER_NAME} =www.igw.news [OR]
RewriteCond %{SERVER_NAME} =igw.news
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

My first question is: I only have created a *:80 entry - should I not have *:443 for the https ?
I didn't see any instructions for creating *:443 anywhere.

In my /var/www/igw.news/html/ I created a basic index.html file:

<html>
<head>
     <title>Welcome</title>
  </head>
   <body>
     <h1>THIS IS IGW.NEWS!</h1>
   </body>
 </html>

I have run a2ensite igw.news.conf ( and all the others)

and apache2ctl configtest ( result Syntax OK )

and systemctl restart apache2

systemctl status apache2

  • apache2.service - The Apache HTTP Server
    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
    Active: active (running) since Tue 2021-11-16 11:26:54 GMT; 23h ago
    Docs: Apache HTTP Server Version 2.4 Documentation - Apache HTTP Server Version 2.4
    Process: 38023 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS)
    Main PID: 32240 (apache2)
    Tasks: 11 (limit: 19071)
    Memory: 21.5M
    CGroup: /system.slice/apache2.service
    |-32240 /usr/sbin/apache2 -k start
    |-38036 /usr/sbin/apache2 -k start
    |-38116 /usr/sbin/apache2 -k start
    |-41701 /usr/sbin/apache2 -k start
    |-41721 /usr/sbin/apache2 -k start
    |-41725 /usr/sbin/apache2 -k start
    |-41732 /usr/sbin/apache2 -k start
    |-41739 /usr/sbin/apache2 -k start
    |-41740 /usr/sbin/apache2 -k start
    |-41749 /usr/sbin/apache2 -k start
    `-41750 /usr/sbin/apache2 -k start

Nov 16 11:26:54 Ubuntu20 systemd[1]: Starting The Apache HTTP Server...
Nov 16 11:26:54 Ubuntu20 systemd[1]: Started The Apache HTTP Server.
Nov 17 00:00:03 Ubuntu20 systemd[1]: Reloading The Apache HTTP Server.
Nov 17 00:00:04 Ubuntu20 systemd[1]: Reloaded The Apache HTTP Server.

Hopefully this is all correct ?

When I use: https://check-your-website.server-daten.de/?q=5.101.140.50

It reports that all these ports are open !!!!

21 FTP
22 SSH
25 SMTP
53 DNS
110 POP3
143 IMAP
465 SMTP (encrypted)
587 SMTP (encrypted, submission)
993 IMAP (encrypted)
995 POP3 (encrypted)
1433 MS SQL
2082 cPanel (http)
2083 cPanel (https)
2086 WHM (http)
2087 WHM (https)
2089 cPanel Licensing
2095 cPanel Webmail (http)
2096 cPanel Webmail (https)
2222 DirectAdmin (http)
2222 DirectAdmin (https)
3306 mySql
5224 Plesk Licensing
5432 PostgreSQL
8080 Ookla Speedtest (http)
8080 Ookla Speedtest (https)
8083 VestaCP http
8083 VestaCP https
8443 Plesk Administration (https)
8447 Plesk Installer + Updates
8880 Plesk Administration (http)
10000 Webmin (http)
10000 Webmin (https)

This is all very concerning as I am NOT running Plesk, Webmin, Vesta, cPanel, or WHM !!

As far as I know all I need open is 22 for SSH and 80 and 443 at the moment and I will open
up the SMPT when I start to use it.

Maybe these ports come open by default with Ubuntu 20.04.3 LTS ?

I am running UTW.
ufw status
Status: active

To Action From

3389/tcp ALLOW Anywhere
22/tcp ALLOW Anywhere
22 ALLOW Anywhere
2222 ALLOW Anywhere
Apache ALLOW Anywhere
Postfix ALLOW Anywhere
3306/tcp ALLOW Anywhere
Apache Full ALLOW Anywhere
3389/tcp (v6) ALLOW Anywhere (v6)
22/tcp (v6) ALLOW Anywhere (v6)
22 (v6) ALLOW Anywhere (v6)
2222 (v6) ALLOW Anywhere (v6)
Apache (v6) ALLOW Anywhere (v6)
Postfix (v6) ALLOW Anywhere (v6)
3306/tcp (v6) ALLOW Anywhere (v6)
Apache Full (v6) ALLOW Anywhere (v6)

Very strange as it doesn't show half the ports that "check-your-website" says are open.
Especially concerning is the unsecure ftp on 21.

That site also seems to be unable to locate any certificates.

Would much appreciate some guidance to get this properly set up.

I have some other questions concerning the certificates shown on transparencyreport.google.com
... seems to be showing several certificates .... not sure what that means,
any way, I better stop here.

I would like to fully understand this, as well as get it working !
Many thanks.
David.

1 Like
2

@Dave.Sintra Welcome to the forum!

Yes, let's focus on just the one domain. Let's start with these:

Please show the output of:
sudo apachectl -t -D DUMP_VHOSTS

Also, show the contents of the file:
/etc/apache2/sites-available/igw.news-le-ssl.conf

Please use the preformatted-text option in the format menu (or Ctrl-E) around each of these separately. Thanks

2 Likes
3

Thanks ...

root@Ubuntu20:~# apachectl -t -D DUMP_VHOSTS

VirtualHost configuration:
*:80                   is a NameVirtualHost
         default server bot10x.com (/etc/apache2/sites-enabled/bot10x.com.conf:1)
         port 80 namevhost bot10x.com (/etc/apache2/sites-enabled/bot10x.com.conf:1)
                 alias www.bot10x.com
         port 80 namevhost cybxpert.com (/etc/apache2/sites-enabled/cybxpert.com.conf:1)
                 alias www.cybxpert.com
         port 80 namevhost expressresponse.net (/etc/apache2/sites-enabled/expressresponse.net.conf:1)
                 alias www.expressresponse.net
         port 80 namevhost gldn.page (/etc/apache2/sites-enabled/gldn.page.conf:1)
                 alias www.gldn.page
         port 80 namevhost igw.news (/etc/apache2/sites-enabled/igw.news.conf:1)
                 alias www.igw.news
         port 80 namevhost pdg.reviews (/etc/apache2/sites-enabled/pdg.reviews.conf:1)
                 alias www.pdg.reviews
         port 80 namevhost reviewed.page (/etc/apache2/sites-enabled/reviewed.page.conf:1)
                 alias www.reviewed.page
         port 80 namevhost smartbiz.pro (/etc/apache2/sites-enabled/smartbiz.pro.conf:1)
                 alias www.smartbiz.pro
         port 80 namevhost ukncsa.com (/etc/apache2/sites-enabled/ukncsa.com.conf:1)
                 alias www.ukncsa.com
         port 80 namevhost yel.page (/etc/apache2/sites-enabled/yel.page.conf:1)
                 alias www.yel.page
root@Ubuntu20:~#

and ...

root@Ubuntu20:~# cat /etc/apache2/sites-available/igw.news-le-ssl.conf

<IfModule mod_ssl.c>
<VirtualHost *:443>
    ServerAdmin admin@igw.news
    ServerName igw.news
    ServerAlias www.igw.news
    DocumentRoot /var/www/igw.news/web
    ErrorLog ${APACHE_LOG_DIR}/eror.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined


Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/igw.news/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/igw.news/privkey.pem
</VirtualHost>
</IfModule>
root@Ubuntu20:~#

Hmm ... now I see where the <VirtualHost *:443> that's good :slight_smile:

3 Likes
4

Hmm. Ok. (thanks for the formatting update)

Let's see the Apache main conf. Paste the contents of (with formatting):
/etc/httpd/conf/httpd.conf

For some reason not all the conf files are being loaded - somewhat odd.

2 Likes
5 
root@Ubuntu20:~# cat /etc/httpd/conf/httpd.conf
cat: /etc/httpd/conf/httpd.conf: No such file or directory

root@Ubuntu20:~# cat /etc/apache2/conf/httpd.conf
cat: /etc/apache2/conf/httpd.conf: No such file or directory

root@Ubuntu20:~#
1 Like
6

Maybe this is better ?

root@Ubuntu20:/etc/apache2# cat apache2.conf

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#       /etc/apache2/
#       |-- apache2.conf
#       |       `--  ports.conf
#       |-- mods-enabled
#       |       |-- *.load
#       |       `-- *.conf
#       |-- conf-enabled
#       |       `-- *.conf
#       `-- sites-enabled
#               `-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
#Mutex file:${APACHE_LOCK_DIR} default

#
# The directory where shm and other runtime files will be stored.
#

DefaultRuntimeDir ${APACHE_RUN_DIR}

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel debug

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
        Options FollowSymLinks
        AllowOverride None
        Require all denied
</Directory>

<Directory /usr/share>
        AllowOverride None
        Require all granted
</Directory>

<Directory /var/www/>
        Options Indexes FollowSymLinks
        AllowOverride None
        Require all granted
</Directory>

#<Directory /srv/>
#       Options Indexes FollowSymLinks
#       AllowOverride None
#       Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
        Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

root@Ubuntu20:/etc/apache2#
2 Likes
7

Update: Nevermind - you found it :slight_smile:

What about: /etc/apache2/apache2.conf

If that's not it we'll have to hunt for it. Do something like ls -lR /etc/apache2

2 Likes
8

Oh. In your first post you showed sites-available. What about:
ls -lR /etc/apache2/sites-enabled

From your Apache conf:

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf
2 Likes
9

root@Ubuntu20:~# ls -lR /etc/apache2/sites-enabled


/etc/apache2/sites-enabled:
total 0
lrwxrwxrwx 1 root root 34 Nov 16 11:23 bot10x.com.conf -> ../sites-available/bot10x.com.conf
lrwxrwxrwx 1 root root 36 Nov 16 11:24 cybxpert.com.conf -> ../sites-available/cybxpert.com.conf
lrwxrwxrwx 1 root root 43 Nov 16 11:24 expressresponse.net.conf -> ../sites-available/expressresponse.net.conf
lrwxrwxrwx 1 root root 33 Nov 16 11:24 gldn.page.conf -> ../sites-available/gldn.page.conf
lrwxrwxrwx 1 root root 32 Nov 16 11:25 igw.news.conf -> ../sites-available/igw.news.conf
lrwxrwxrwx 1 root root 35 Nov 16 11:25 pdg.reviews.conf -> ../sites-available/pdg.reviews.conf
lrwxrwxrwx 1 root root 37 Nov 16 11:25 reviewed.page.conf -> ../sites-available/reviewed.page.conf
lrwxrwxrwx 1 root root 36 Nov 16 11:26 smartbiz.pro.conf -> ../sites-available/smartbiz.pro.conf
lrwxrwxrwx 1 root root 34 Nov 16 11:26 ukncsa.com.conf -> ../sites-available/ukncsa.com.conf
lrwxrwxrwx 1 root root 32 Nov 16 11:26 yel.page.conf -> ../sites-available/yel.page.conf
1 Like
10

In case it helps, I also listed this ...
(as it appears to be included)

root@Ubuntu20:~# cat /etc/letsencrypt/options-ssl-apache.conf


# This file contains important security parameters. If you modify this file
# manually, Certbot will be unable to automatically provide future security
# updates. Instead, Certbot will print and log an error message with a path to
# the up-to-date file that you will need to refer to when manually updating
# this file.

SSLEngine on

# Intermediate configuration, tweak to your needs
SSLProtocol             all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite          ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
SSLHonorCipherOrder     off
SSLSessionTickets       off

SSLOptions +StrictRequire

# Add vhost name to log entries:
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" vhost_combined
LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common

root@Ubuntu20:~#

But probably this is standard?

1 Like
11

OK thanks. Your Apache conf only includes the VirtualHosts in sites-enabled so that is why no 443 VHosts are active. From:
IncludeOptional sites-enabled/*.conf

You need symlinks in there for each of the VHosts you want from sites-available

Or, just refer to sites-available in your Apache conf include statement instead of sites-enabled. I am not an Apache expert but I have seen people do both. Someone else will need to comment about which is "best practice" - I am just looking at the main failure and will now be away soon. Cheers

2 Likes
12

Hmm ( Updated )
I see In sites-enabled, there are those 10 files that contain the symlinks to the sites-available ...
but only the standard ones, not the -ssl ones.

And thanks very much for helping.

This is strange that it is not updated by the certbot ... it must be affecting everyone ... No?

So,, should I add IncludeOptional sites-available/*.conf
to the main apache2 conf file ?

1 Like
13

The symlinks are only to the VHost files for port 80. Should have for example both of these from sites-available in sites-enabled:

-rw-r--r-- 1 root root 423 Nov 16 11:20 igw.news.conf
-rw-r--r-- 1 root root 463 Nov 15 13:25 igw.news-le-ssl.conf

Do not add sites-available - you will get duplicates then. Some people use that instead of sites-enabled but it seems the more appropriate setup is as you have it but just fix the symlinks in sites-enabled (using a2ensite or however you did the ones you have).

2 Likes
14

My update "crossed" your reply

1 Like
15

Yeah, no problem. How that happened is not clear to me but need to be away now.

2 Likes
16

OK. Thanks again.

I'll give it a try.

2 Likes
17

OK,
I did as suggested and ran the a2ensite on the ...le-ssl.conf files as well.

And now in the sites-enabled I have:

root@Ubuntu20:/etc/apache2/sites-enabled# ls -l
total 0
lrwxrwxrwx 1 root root 34 Nov 16 11:23 bot10x.com.conf -> ../sites-available/bot10x.com.conf
lrwxrwxrwx 1 root root 41 Nov 17 16:31 bot10x.com-le-ssl.conf -> ../sites-available/bot10x.com-le-ssl.conf
lrwxrwxrwx 1 root root 36 Nov 16 11:24 cybxpert.com.conf -> ../sites-available/cybxpert.com.conf
lrwxrwxrwx 1 root root 43 Nov 17 16:33 cybxpert.com-le-ssl.conf -> ../sites-available/cybxpert.com-le-ssl.conf
lrwxrwxrwx 1 root root 43 Nov 16 11:24 expressresponse.net.conf -> ../sites-available/expressresponse.net.conf
lrwxrwxrwx 1 root root 50 Nov 17 16:33 expressresponse.net-le-ssl.conf -> ../sites-available/expressresponse.net-le-ssl.conf
lrwxrwxrwx 1 root root 33 Nov 16 11:24 gldn.page.conf -> ../sites-available/gldn.page.conf
lrwxrwxrwx 1 root root 40 Nov 17 16:34 gldn.page-le-ssl.conf -> ../sites-available/gldn.page-le-ssl.conf
lrwxrwxrwx 1 root root 32 Nov 16 11:25 igw.news.conf -> ../sites-available/igw.news.conf
lrwxrwxrwx 1 root root 39 Nov 17 16:34 igw.news-le-ssl.conf -> ../sites-available/igw.news-le-ssl.conf
lrwxrwxrwx 1 root root 35 Nov 16 11:25 pdg.reviews.conf -> ../sites-available/pdg.reviews.conf
lrwxrwxrwx 1 root root 42 Nov 17 16:34 pdg.reviews-le-ssl.conf -> ../sites-available/pdg.reviews-le-ssl.conf
lrwxrwxrwx 1 root root 37 Nov 16 11:25 reviewed.page.conf -> ../sites-available/reviewed.page.conf
lrwxrwxrwx 1 root root 44 Nov 17 16:34 reviewed.page-le-ssl.conf -> ../sites-available/reviewed.page-le-ssl.conf
lrwxrwxrwx 1 root root 36 Nov 16 11:26 smartbiz.pro.conf -> ../sites-available/smartbiz.pro.conf
lrwxrwxrwx 1 root root 34 Nov 16 11:26 ukncsa.com.conf -> ../sites-available/ukncsa.com.conf
lrwxrwxrwx 1 root root 41 Nov 17 16:35 ukncsa.com-le-ssl.conf -> ../sites-available/ukncsa.com-le-ssl.conf
lrwxrwxrwx 1 root root 32 Nov 16 11:26 yel.page.conf -> ../sites-available/yel.page.conf
lrwxrwxrwx 1 root root 39 Nov 17 16:35 yel.page-le-ssl.conf -> ../sites-available/yel.page-le-ssl.conf

So, there is a change.
I now get this error for browsing igw.news in Chrome

# Not Found
The requested URL was not found on this server.
Apache/2.4.41 (Ubuntu) Server at igw.news Port 443
1 Like
18

Your document root in the 443 server is not the same as the port 80 server:

443: DocumentRoot /var/www/igw.news/web

3 Likes
19

Ahh ...
Ok - that was a previous structure that I since amended trying to fix it.

Thanks, I'll make the changes

2 Likes
20

BTW ...
Do I need to have the /html after the igw.news ?

Is it more usual just to put the .html,.php files directly into the igw.news directory?

(In my mind, it would be cleaner not to have that /html sub directory)

If I change the structure, do I need new certificates?

1 Like