SSL on Ubuntu 16.04 with apache and varnish

rg305 · May 22, 2018, 8:14am

Thus the “trick” I’ve been trying to supply.

markos · May 22, 2018, 8:14am

Probably

/etc/varnish/default.vcl

# Default backend definition. Set this to point to your content server.
backend default {
    .host = "195.201.138.70";
    .port = "8080";
}

EDIT:

/etc/default/varnish

VARNISH_LISTEN_PORT=80

@_az I didn't make any changes yet. So, I should give in to the certonly , right? What about the previous certificate that I created?

rg305 · May 22, 2018, 8:17am

Yes, but you could add (as I said earlier) another listener on another IP:80
Like:
Listen 127.0.0.123:80
that will suffice for the certbot listen port 80 check.
Then we simply face the check for FQDNs.
Which can be added as well.
I just need to grasp where…

Please show the apache.conf file.

_az · May 22, 2018, 8:18am

If you already have a certificate issued, then you can just create a virtual host on Apache.

e.g.

<VirtualHost *:443>
  ServerName leptokaropoulos.gr
  ServerAlias www.leptokaropoulos.gr
  ProxyPass / http://localhost:80/
  ProxyPassReverse / http://localhost:80/

  SSLEngine on
  SSLCertificateFile      /etc/letsencrypt/live/leptokaropoulos.gr/cert.pem
  SSLCertificateChainFile /etc/letsencrypt/live/leptokaropoulos.gr/chain.pem
  SSLCertificateKeyFile   /etc/letsencrypt/live/leptokaropoulos.gr/privkey.pem
</VirtualHost>

I think I understand what @rg305 was suggesting now, sorry for the outburst

rg305 · May 22, 2018, 8:19am

rethinking this through...

Apache listens on 443 (https)
Proxies to port 80 (varnish) http
varnish proxies to 8080 also http.

Yes, this can work.

markos · May 22, 2018, 8:21am

By seeing @_az 's response let me add this last thing (I don’t have a live folder inside /etc/letsencrypt):

etc/letsencrypt/
├── accounts
│   └── acme-v01.api.letsencrypt.org
│       └── directory
│           └── [random numbers and characters]
│               ├── meta.json
│               ├── private_key.json
│               └── regr.json
├── cli.ini
├── csr
│   └── 0000_csr-certbot.pem
├── keys
│   └── 0000_key-certbot.pem
├── options-ssl-apache.conf
├── renewal
└── renewal-hooks
    ├── deploy
    ├── post
    └── pre

_az · May 22, 2018, 8:21am

Well, it will be necessary in the end in order to include Varnish in the request path, so if it does cause a loop, it’ll need to be fixed with x-forwarded-proto etc.

_az · May 22, 2018, 8:22am

Looks like you haven’t created a certificate yet. Give it a try with the certonly command (or the way @rg305 suggested, up to you).

rg305 · May 22, 2018, 8:22am

try:
certbot certificates

and please show the apache.conf file.

markos · May 22, 2018, 8:26am

No certs found.

@rg305 do you mean ports.conf or apache2.conf ?

rg305 · May 22, 2018, 8:29am

send both if you can

just remove any lines that start with #

markos · May 22, 2018, 8:29am

Guys, I found this.

markos · May 22, 2018, 8:32am

/etc/apache2/ports.conf:

Listen 8080

<IfModule ssl_module>
        Listen 443
</IfModule>

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

/etc/apache2/apache2.conf:

Mutex file:${APACHE_LOCK_DIR} default
PidFile ${APACHE_PID_FILE}
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 5
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
HostnameLookups Off
ErrorLog ${APACHE_LOG_DIR}/error.log
LogLevel warn
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
Include ports.conf
<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 All
        Require all granted
</Directory>
<Directory /var/www/html/>
        AllowOverride All
        Require all granted
        Options Indexes FollowSymLinks
</Directory>
AccessFileName .htaccess
<FilesMatch "^\.ht">
        Require all denied
</FilesMatch>
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
IncludeOptional conf-enabled/*.conf
IncludeOptional sites-enabled/*.conf

_az · May 22, 2018, 8:32am

Sure, you can use that article. It’s more or less what I was proposing.

The only problem with it is that it’s incompatible with --apache, you’d need to use certonly with --webroot before you setup the HTTPS listener.

rg305 · May 22, 2018, 8:33am

The first design is exactly as @_az suggested.

rg305 · May 22, 2018, 8:36am

Ok that was lacking...
I need to see what's in these:

try here first:
ls -l /etc/apache2/sites-enabled/
Probably just a default.conf file, if so, post that here.
Otherwise show the list and post them all!

markos · May 22, 2018, 8:39am

/etc/apache2/sites-enabled/000-default.conf

<VirtualHost *:8080>
        # The ServerName directive sets the request scheme, hostname and port that
        # the server uses to identify itself. This is used when creating
        # redirection URLs. In the context of virtual hosts, the ServerName
        # specifies what hostname must appear in the request's Host: header to
        # match this virtual host. For the default virtual host (this file) this
        # value is not decisive as it is used as a last resort host regardless.
        # However, you must set it for any further virtual host explicitly.
        #ServerName www.example.com

        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/html

        # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
        # error, crit, alert, emerg.
        # It is also possible to configure the loglevel for particular
        # modules, e.g.
        #LogLevel info ssl:warn

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

        # For most configuration files from conf-available/, which are
        # enabled or disabled at a global level, it is possible to
        # include a line for only one particular virtual host. For example the
        # following line enables the CGI configuration for this host only
        # after it has been globally disabled with "a2disconf".
        #Include conf-available/serve-cgi-bin.conf
</VirtualHost>

EDIT:

ls /etc/apache2/conf-enabled/ :

charset.conf localized-error-pages.conf other-vhosts-access-log.conf security.conf serve-cgi-bin.conf

rg305 · May 22, 2018, 8:42am

Yeah this (and ports.conf) is were it all happens

markos · May 22, 2018, 8:47am

Could I make the following new entry (as mentioned from @_az), for simplicity, on ports.conf :

<VirtualHost *:443>
  ServerName leptokaropoulos.gr
  ServerAlias www.leptokaropoulos.gr
  ProxyPass / http://localhost:80/
  ProxyPassReverse / http://localhost:80/

  SSLEngine on
  SSLCertificateFile      /etc/letsencrypt/live/leptokaropoulos.gr/cert.pem
  SSLCertificateChainFile /etc/letsencrypt/live/leptokaropoulos.gr/chain.pem
  SSLCertificateKeyFile   /etc/letsencrypt/live/leptokaropoulos.gr/privkey.pem
</VirtualHost>

EDIT:

And then (or previously) create a new certificate by using certonly.

rg305 · May 22, 2018, 8:48am

I would try this:
modify file
ports.conf
add
Listen 127.0.0.123:80
right after
Listen 8080

copy 000-default.conf to new file
cp /etc/apache2/sites-enabled/000-default.conf /etc/apache2/sites-enabled/127-80-default.conf

modify /etc/apache2/sites-enabled/127-80-default.conf
change
<VirtualHost *:8080>
to
<VirtualHost 127.0.0.123:80>

restart apache web server
then let certbot do its’ thing.

Topic		Replies	Views
Let's Encrypt, Apache and Varnish - the right way? Help	5	2095	October 3, 2019
Certbot on apache unable to find virtual host listening on port 80 Help	3	827	January 30, 2022
Before I wander off into the weeds Help	17	504	June 27, 2022
Cannot install SSL Help	3	510	July 16, 2023
Virtual Host on port 71 Help	14	880	October 30, 2018

SSL on Ubuntu 16.04 with apache and varnish

Related topics