Apache2 on Debian 10 didn't accept my domains description

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: koala.poznan.pl, www.koala.poznan.pl, blog.koala.poznan.pl, img.koala.poznan.pl, calkiem.naukowa.it

I ran this command: sudo /etc/init.d/apache2 restart

It produced this output: failed!

My web server is (include version): * Serwer: Localhost via UNIX socket

  • Typ serwera: MySQL
  • Połączenie z serwerem: SSL nie jest używany
  • Wersja serwera: 8.0.28 - MySQL Community Server - GPL
  • Wersja protokołu: 10
  • Kodowanie znaków serwera: UTF-8 Unicode (utf8mb4)

Serwer WWW

  • Apache/2.4.51 (Debian)
  • Wersja klienta bazy danych: libmysql - mysqlnd 7.4.25
  • Rozszerzenie PHP: mysqli
  • Wersja PHP: 7.4.25

phpMyAdmin

  • Informacja o wersji: 5.1.2, ostatnia stabilna wersja: [5.1.3]

The operating system my web server runs on is (include version): Linux koala 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Feb 22 07:34:40 2022 from 79.163.139.77

My hosting provider, if applicable, is: Poznan University - wmi.uam.edu.pl

I can login to a root shell on my machine (yes or no, or I don't know): yes - 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 certbot --version or certbot-auto --version if you're using Certbot): andrzej@koala:~$ sudo certbot --version
certbot 1.12.0
andrzej@koala:~$
wordpress in blog folder installed
#DocumentRoot /var/www/html/wordpress
<Directory /var/www/html/blog/>
AllowOverride All

-rw-r--r-- 1 root root 348 Feb 22 11:21 /etc/apache2/sites-available/koala.poznan.pl-le-ssl.conf
1 <VirtualHost *:80>
2 ServerName koala.poznan.pl
3 ServerAlias koala.wmi.amu.edu.pl
4 # The ServerName directive sets the request scheme, hostname and port that
5 # the server uses to identify itself. This is used when creating
6 # redirection URLs. In the context of virtual hosts, the ServerName
7 # specifies what hostname must appear in the request's Host: header to
8 # match this virtual host. For the default virtual host (this file) this
9 # value is not decisive as it is used as a last resort host regardless.
10 # However, you must set it for any further virtual host explicitly.
11 #ServerName www.example.com
12
13 ServerAdmin webmaster@localhost
14 DocumentRoot /var/www/html
15
16 # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
17 # error, crit, alert, emerg.
18 # It is also possible to configure the loglevel for particular
19 # modules, e.g.
20 #LogLevel info ssl:warn
21
22 ErrorLog ${APACHE_LOG_DIR}/error.log
23 CustomLog ${APACHE_LOG_DIR}/access.log combined
24
25 # For most configuration files from conf-available/, which are
26 # enabled or disabled at a global level, it is possible to
27 # include a line for only one particular virtual host. For example the
28 # following line enables the CGI configuration for this host only
29 # after it has been globally disabled with "a2disconf".
30 #Include conf-available/serve-cgi-bin.conf
31 RewriteEngine on
32 RewriteCond %{SERVER_NAME} =koala.poznan.pl [OR]
33 RewriteCond %{SERVER_NAME} =www.koala.poznan.pl [OR]
34 RewriteCond %{SERVER_NAME} =koala.wmi.amu.edu.pl
35 RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
36

-rw-r--r-- 1 root root 927 Feb 22 16:02 /etc/apache2/sites-available/koala.poznan.pl.conf
103
104 # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
105 <VirtualHost *:80>
106 ServerName www.koala.poznan.pl
107 ServerAlias koala.poznan.pl
108 Redirect / https://koala.poznan.pl/
109
110
111
112 ServerName www.koala.poznan.pl
113 DocumentRoot /var/www/html
114 Redirect / https://koala.poznan.pl/
115
116 <VirtualHost *:80 *:443>
117 SSLEngine On
118 ServerName example.com
119 ServerAlias www.example.com
120 DocumentRoot /srv/www/example.www
121 </VirtualHost
122 <VirtualHost *:80>
123 # The ServerName directive sets the request scheme, hostname and port that
124 # the server uses to identify itself. This is used when creating
125 # redirection URLs. In the context of virtual hosts, the ServerName
126 # specifies what hostname must appear in the request's Host: header to
127 # match this virtual host. For the default virtual host (this file) this
128 # value is not decisive as it is used as a last resort host regardless.
129 # However, you must set it for any further virtual host explicitly.
130 #ServerName www.example.com
131
132 ServerAdmin webmaster@localhost
133 DocumentRoot /var/www/html
134
135 # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
136 # error, crit, alert, emerg.
137 # It is also possible to configure the loglevel for particular
138 # modules, e.g.
139 #LogLevel info ssl:warn
140
141 ErrorLog ${APACHE_LOG_DIR}/error.log
142 CustomLog ${APACHE_LOG_DIR}/access.log combined
143
144 # For most configuration files from conf-available/, which are
145 # enabled or disabled at a global level, it is possible to
146 # include a line for only one particular virtual host. For example the
147 # following line enables the CGI configuration for this host only
148 # after it has been globally disabled with "a2disconf".
149 #Include conf-available/serve-cgi-bin.conf
150 RewriteEngine on
151 RewriteCond %{SERVER_NAME} =koala.wmi.amu.edu.pl
152 RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
153

-rw-r--r-- 1 root root 289 Feb 22 19:34 /etc/apache2/sites-available/blog.koala.poznan.pl.conf
238 <VirtualHost *:80>
239 ServerName blog.koala.poznan.pl
240 DocumentRoot /var/www/html/blog/
241 RewriteEngine on
242 RewriteCond %{HTTPS} off
243 RewriteCond %{SERVER_NAME} = blog.koala.poznan.pl
244 RewriteRule ^ https://blog.koala.poznan.pl%{REQUEST_URI} [R=301,L,NE]
245

-rw-r--r-- 1 root root 1738 Feb 22 19:29 /etc/apache2/sites-available/blog.koala.poznan.pl-ssl.conf
247
248 <VirtualHost *:443>
249 # The ServerName directive sets the request scheme, hostname and port that
250 # the server uses to identify itself. This is used when creating
251 # redirection URLs. In the context of virtual hosts, the ServerName
252 # specifies what hostname must appear in the request's Host: header to
253 # match this virtual host. For the default virtual host (this file) this
254 # value is not decisive as it is used as a last resort host regardless.
255 # However, you must set it for any further virtual host explicitly.
256 #ServerName www.example.com
257 ServerName blog.koala.poznan.pl
258 ServerAdmin mobit@gazeta.pl
259 DocumentRoot /var/www/html/blog/
260
261 # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
262 # error, crit, alert, emerg.
263 # It is also possible to configure the loglevel for particular
264 # modules, e.g.
265 #LogLevel info ssl:warn
266
267 ErrorLog ${APACHE_LOG_DIR}/error.log
268 CustomLog ${APACHE_LOG_DIR}/access.log combined
269
270 # For most configuration files from conf-available/, which are
271 # enabled or disabled at a global level, it is possible to
272 # include a line for only one particular virtual host. For example the
273 # following line enables the CGI configuration for this host only
274 # after it has been globally disabled with "a2disconf".
275 #Include conf-available/serve-cgi-bin.conf
276
277
278
279 Include /etc/letsencrypt/options-ssl-apache.conf
280 SSLCertificateFile /etc/letsencrypt/live/blog.koala.poznan.pl-0001/fullchain.pem
281 SSLCertificateKeyFile /etc/letsencrypt/live/blog.koala.poznan.pl-0001/privkey.pem
282
283

-rw-r--r-- 1 root root 287 Feb 22 18:08 /etc/apache2/sites-available/calkiem.naukowa.it.conf
285 <VirtualHost *:80>
286 ServerName calkiem.naukowa.it
287 DocumentRoot /var/www/html/calkiem/
288 RewriteEngine on
289 RewriteCond %{HTTPS} !=on
290 RewriteCond %{SERVER_NAME} = calkiem.naukowa.it
291 RewriteRule ^ https://calkiem.naukowa.it%{REQUEST_URI} [R=301,L,NE]
292

-rw-r--r-- 1 root root 1725 Feb 22 18:05 /etc/apache2/sites-available/calkiem.naukowa.it-ssl.conf
294
295 <VirtualHost :443>
296 # The ServerName directive sets the request scheme, hostname and port that
297 # the server uses to identify itself. This is used when creating
298 # redirection URLs. In the context of virtual hosts, the ServerName
299 # specifies what hostname must appear in the request's Host: header to
300 # match this virtual host. For the default virtual host (this file) this
301 # value is not decisive as it is used as a last resort host regardless.
302 # However, you must set it for any further virtual host explicitly.
303 #ServerName www.example.com
304 ServerName calkiem.naukowa.it
305 ServerAdmin mobit@gazeta.pl
306 DocumentRoot /var/www/html/calkiem/
307
308 # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
309 # error, crit, alert, emerg.
310 # It is also possible to configure the loglevel for particular
311 # modules, e.g.
312 #LogLevel info ssl:warn
313
314 ErrorLog ${APACHE_LOG_DIR}/error.log
315 CustomLog ${APACHE_LOG_DIR}/access.log combined
316
317 # For most configuration files from conf-available/, which are
318 # enabled or disabled at a global level, it is possible to
319 # include a line for only one particular virtual host. For example the
320 # following line enables the CGI configuration for this host only
321 # after it has been globally disabled with "a2disconf".
322 #Include conf-available/serve-cgi-bin.conf
323
324
325
326 Include /etc/letsencrypt/options-ssl-apache.conf
327 SSLCertificateFile /etc/letsencrypt/live/calkiem.naukowa.it/fullchain.pem
328 SSLCertificateKeyFile /etc/letsencrypt/live/calkiem.naukowa.it/privkey.pem
329
330
331
332
333
334 ServerAdmin webmaster@localhost
335
336 DocumentRoot /var/www/html
337
338 # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
339 # error, crit, alert, emerg.
340 # It is also possible to configure the loglevel for particular
341 # modules, e.g.
342 #LogLevel info ssl:warn
343
344 ErrorLog ${APACHE_LOG_DIR}/error.log
345 CustomLog ${APACHE_LOG_DIR}/access.log combined
346
347 # For most configuration files from conf-available/, which are
348 # enabled or disabled at a global level, it is possible to
349 # include a line for only one particular virtual host. For example the
350 # following line enables the CGI configuration for this host only
351 # after it has been globally disabled with "a2disconf".
352 #Include conf-available/serve-cgi-bin.conf
353
354 # SSL Engine Switch:
355 # Enable/Disable SSL for this virtual host.
356 SSLEngine on
357
358 # A self-signed (snakeoil) certificate can be created by installing
359 # the ssl-cert package. See
360 # /usr/share/doc/apache2/README.Debian.gz for more info.
361 # If both key and certificate are stored in the same file, only the
362 # SSLCertificateFile directive is needed.
363 SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
364 SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key
365
366 # Server Certificate Chain:
367 # Point SSLCertificateChainFile at a file containing the
368 # concatenation of PEM encoded CA certificates which form the
369 # certificate chain for the server certificate. Alternatively
370 # the referenced file can be the same as SSLCertificateFile
371 # when the CA certificates are directly appended to the server
372 # certificate for convinience.
373 #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt
374
375 # Certificate Authority (CA):
376 # Set the CA certificate verification path where to find CA
377 # certificates for client authentication or alternatively one
378 # huge file containing all of them (file must be PEM encoded)
379 # Note: Inside SSLCACertificatePath you need hash symlinks
380 # to point to the certificate files. Use the provided
381 # Makefile to update the hash symlinks after changes.
382 #SSLCACertificatePath /etc/ssl/certs/
383 #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt
384
385 # Certificate Revocation Lists (CRL):
386 # Set the CA revocation path where to find CA CRLs for client
387 # authentication or alternatively one huge file containing all
388 # of them (file must be PEM encoded)
389 # Note: Inside SSLCARevocationPath you need hash symlinks
390 # to point to the certificate files. Use the provided
391 # Makefile to update the hash symlinks after changes.
392 #SSLCARevocationPath /etc/apache2/ssl.crl/
393 #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl
394
395 # Client Authentication (Type):
396 # Client certificate verification type and depth. Types are
397 # none, optional, require and optional_no_ca. Depth is a
398 # number which specifies how deeply to verify the certificate
399 # issuer chain before deciding the certificate is not valid.
400 #SSLVerifyClient require
401 #SSLVerifyDepth 10
402
403 # SSL Engine Options:
404 # Set various options for the SSL engine.
405 # o FakeBasicAuth:
406 # Translate the client X.509 into a Basic Authorisation. This means that
407 # the standard Auth/DBMAuth methods can be used for access control. The
408 # user name is the one line' version of the client's X.509 certificate. 409 # Note that no password is obtained from the user. Every entry in the user 410 # file needs this password: xxj31ZMTZzkVA'.
411 # o ExportCertData:
412 # This exports two additional environment variables: SSL_CLIENT_CERT and
413 # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
414 # server (always existing) and the client (only existing when client
415 # authentication is used). This can be used to import the certificates
416 # into CGI scripts.
417 # o StdEnvVars:
418 # This exports the standard SSL/TLS related `SSL_
' environment variables.
419 # Per default this exportation is switched off for performance reasons,
420 # because the extraction step is an expensive operation and is usually
421 # useless for serving static content. So one usually enables the
422 # exportation for CGI and SSI requests only.
423 # o OptRenegotiate:
424 # This enables optimized SSL connection renegotiation handling when SSL
425 # directives are used in per-directory context.
426 #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
427 <FilesMatch ".(cgi|shtml|phtml|php)$">
428 SSLOptions +StdEnvVars
429
430 <Directory /usr/lib/cgi-bin>
431 SSLOptions +StdEnvVars
432
433
434 # SSL Protocol Adjustments:
435 # The safe and default but still SSL/TLS standard compliant shutdown
436 # approach is that mod_ssl sends the close notify alert but doesn't wait for
437 # the close notify alert from client. When you need a different shutdown
438 # approach you can use one of the following variables:
439 # o ssl-unclean-shutdown:
440 # This forces an unclean shutdown when the connection is closed, i.e. no
441 # SSL close notify alert is send or allowed to received. This violates
442 # the SSL/TLS standard but is needed for some brain-dead browsers. Use
443 # this when you receive I/O errors because of the standard approach where
444 # mod_ssl sends the close notify alert.
445 # o ssl-accurate-shutdown:
446 # This forces an accurate shutdown when the connection is closed, i.e. a
447 # SSL close notify alert is send and mod_ssl waits for the close notify
448 # alert of the client. This is 100% SSL/TLS standard compliant, but in
449 # practice often causes hanging connections with brain-dead browsers. Use
450 # this only for browsers where you know that their SSL implementation
451 # works correctly.
452 # Notice: Most problems of broken clients are also related to the HTTP
453 # keep-alive facility, so you usually additionally want to disable
454 # keep-alive for those clients, too. Use variable "nokeepalive" for this.
455 # Similarly, one has to force some clients to use HTTP/1.0 to workaround
456 # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
457 # "force-response-1.0" for this.
458 # BrowserMatch "MSIE [2-6]"
459 # nokeepalive ssl-unclean-shutdown
460 # downgrade-1.0 force-response-1.0
461
462
463

-rw-r--r-- 1 root root 287 Feb 22 18:22 /etc/apache2/sites-available/img.koala.poznan.pl.conf
465 # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
466 <VirtualHost *:80>
467 ServerName img.koala.poznan.pl
468 DocumentRoot /home/andrzej/media/
469 RewriteEngine on
470 RewriteCond %{HTTPS} !=on
471 RewriteCond %{SERVER_NAME} =img.koala.poznan.pl
472 RewriteRule ^ https://img.koala.poznan.pl%{REQUEST_URI} [R=301,L,NE]
473
474
475
476 <VirtualHost *:443>
477 # The ServerName directive sets the request scheme, hostname and port that
478 # the server uses to identify itself. This is used when creating
479 # redirection URLs. In the context of virtual hosts, the ServerName
480 # specifies what hostname must appear in the request's Host: header to
481 # match this virtual host. For the default virtual host (this file) this
482 # value is not decisive as it is used as a last resort host regardless.
483 # However, you must set it for any further virtual host explicitly.
484 #ServerName www.example.com
485 ServerName img.koala.poznan.pl
486 ServerAdmin mobit@gazeta.pl
487 DocumentRoot /home/andrzeju/media/
488
489 # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
490 # error, crit, alert, emerg.
491 # It is also possible to configure the loglevel for particular
492 # modules, e.g.
493 #LogLevel info ssl:warn
494
495 ErrorLog ${APACHE_LOG_DIR}/error.log
496 CustomLog ${APACHE_LOG_DIR}/access.log combined
497
498 # For most configuration files from conf-available/, which are
499 # enabled or disabled at a global level, it is possible to
500 # include a line for only one particular virtual host. For example the
501 # following line enables the CGI configuration for this host only
502 # after it has been globally disabled with "a2disconf".
503 #Include conf-available/serve-cgi-bin.conf
504
505
506
507 Include /etc/letsencrypt/options-ssl-apache.conf
508 SSLCertificateFile /etc/letsencrypt/live/img.koala.poznan.pl/fullchain.pem
509 SSLCertificateKeyFile /etc/letsencrypt/live/img.koala.poznan.pl/privkey.pem
510
511

-rw-r--r-- 1 root root 1727 Feb 22 19:28 /etc/apache2/sites-available/img.koala.poznan.pl-ssl.conf
513 <VirtualHost :80>
514 ServerName koala.poznan.pl
515 ServerAdmin mobit@gazeta.pl
516 DocumentRoot /var/www/html
517 ErrorLog ${APACHE_LOG_DIR}/error.log
518 CustomLog ${APACHE_LOG_DIR}/access.logcombined koala.poznan.pl-le-ssl.conf
519 RewriteEngine on
520 RewriteCond %{HTTPS} off
521 RewriteCond %{SERVER_NAME} =koala.poznan.pl
522 RewriteCond %{HTTP_HOST} !^www
[NC]
523 RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
524
525 <VirtualHost *:80 :443>
526 ServerName www.koala.poznan.pl
527 RewriteEngine on
528 RewriteCond %{HTTP_HOST} ^www
[NC]
529 RewriteRule ^ https://koala.poznan.pl%{REQUEST_URI} [R=301,L]
530 Include /etc/letsencrypt/options-ssl-apache.conf
531 SSLCertificateFile /etc/letsencrypt/live/koala.poznan.pl/fullchain.pem
532 SSLCertificateKeyFile /etc/letsencrypt/live/koala.poznan.pl/privkey.pem
533
534
535 # vim: syntax=apache ts=4 sw=4 sts=4 sr noet
536
537 <VirtualHost *:443>
538 ServerName koala.poznan.pl
539 RewriteEngine on
540 RewriteCond %{HTTP_HOST} !^www. [NC]
541 Include /etc/letsencrypt/options-ssl-apache.conf
542 SSLCertificateFile /etc/letsencrypt/live/koala.poznan.pl/fullchain.pem
543 SSLCertificateKeyFile /etc/letsencrypt/live/koala.poznan.pl/privkey.pem
544
545
546
547 ServerName koala.poznan.pl
548 ServerAlias www.koala.poznan.pl
549 ServerSignature Off
550
551 RewriteEngine On
552 RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
553
554 ErrorLog /var/log/apache2/redirect.error.log
555 LogLevel warn
556
557 #DocumentRoot /var/www/html/wordpress
558 <Directory /var/www/html/blog/>
559 AllowOverride All
560

andrzej@koala:/var/www/html$ sudo ls -full /etc/apache2/sites-enabled
total 8
lrwxrwxrwx 1 root root 33 Feb 22 00:00 wordpress.conf -> ../sites-available/wordpress.conf
lrwxrwxrwx 1 root root 39 Feb 22 00:00 koala.poznan.pl.conf -> ../sites-available/koala.poznan.pl.conf
lrwxrwxrwx 1 root root 43 Feb 22 19:48 img.koala.poznan.pl.conf -> ../sites-available/img.koala.poznan.pl.conf
drwxr-xr-x 2 root root 4096 Feb 22 19:53 .
lrwxrwxrwx 1 root root 47 Feb 22 19:48 img.koala.poznan.pl-ssl.conf -> ../sites-available/img.koala.poznan.pl-ssl.conf
lrwxrwxrwx 1 root root 56 Feb 22 00:00 koala.poznan.pl-le-ssl.conf -> /etc/apache2/sites-available/koala.poznan.pl-le-ssl.conf
drwxr-xr-x 8 root root 4096 Feb 22 19:55 ..
andrzej@koala:/var/www/html$ sudo a2ensite calkiem.naukowa.it.conf
Enabling site calkiem.naukowa.it.
To activate the new configuration, you need to run:
systemctl reload apache2
andrzej@koala:/var/www/html$ sudo a2ensite calkiem.naukowa.it-ssl.conf
Enabling site calkiem.naukowa.it-ssl.
To activate the new configuration, you need to run:
systemctl reload apache2
andrzej@koala:/var/www/html$ sudo a2ensite blog.koala.poznan.pl-ssl.conf
Enabling site blog.koala.poznan.pl-ssl.
To activate the new configuration, you need to run:
systemctl reload apache2
andrzej@koala:/var/www/html$ sudo a2ensite blog.koala.poznan.pl.conf
Enabling site blog.koala.poznan.pl.
To activate the new configuration, you need to run:
systemctl reload apache2
andrzej@koala:/var/www/html$ sudo ls -full /etc/apache2/sites-enabled
total 8
lrwxrwxrwx 1 root root 33 Feb 22 00:00 wordpress.conf -> ../sites-available/wordpress.conf
lrwxrwxrwx 1 root root 39 Feb 22 00:00 koala.poznan.pl.conf -> ../sites-available/koala.poznan.pl.conf
lrwxrwxrwx 1 root root 44 Feb 22 20:54 blog.koala.poznan.pl.conf -> ../sites-available/blog.koala.poznan.pl.conf
lrwxrwxrwx 1 root root 43 Feb 22 19:48 img.koala.poznan.pl.conf -> ../sites-available/img.koala.poznan.pl.conf
lrwxrwxrwx 1 root root 48 Feb 22 20:54 blog.koala.poznan.pl-ssl.conf -> ../sites-available/blog.koala.poznan.pl-ssl.conf
lrwxrwxrwx 1 root root 46 Feb 22 20:54 calkiem.naukowa.it-ssl.conf -> ../sites-available/calkiem.naukowa.it-ssl.conf
drwxr-xr-x 2 root root 4096 Feb 22 20:55 .
lrwxrwxrwx 1 root root 47 Feb 22 19:48 img.koala.poznan.pl-ssl.conf -> ../sites-available/img.koala.poznan.pl-ssl.conf
lrwxrwxrwx 1 root root 42 Feb 22 20:53 calkiem.naukowa.it.conf -> ../sites-available/calkiem.naukowa.it.conf
lrwxrwxrwx 1 root root 56 Feb 22 00:00 koala.poznan.pl-le-ssl.conf -> /etc/apache2/sites-available/koala.poznan.pl-le-ssl.conf
drwxr-xr-x 8 root root 4096 Feb 22 19:55 ..
andrzej@koala:/var/www/html$ sudo /etc/init.d/apache2 restart
Restarting apache2 (via systemctl): apache2.serviceJob for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
failed!
andrzej@koala:/var/www/html$
andrzej@koala:/var/www/html$ sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Found the following certs:
Certificate Name: blog.koala.poznan.pl-0001
Serial Number: 4348fa016c577032d43e1f13d7ba1da71da
Key Type: RSA
Domains: blog.koala.poznan.pl
Expiry Date: 2022-05-23 14:48:03+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/blog.koala.poznan.pl-0001/fullchain.pem
Private Key Path: /etc/letsencrypt/live/blog.koala.poznan.pl-0001/privkey.pem
Certificate Name: calkiem.naukowa.it
Serial Number: 4b48e3c2ebc1316f0fe76bc5721ca1550ad
Key Type: RSA
Domains: calkiem.naukowa.it
Expiry Date: 2022-05-23 14:38:58+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/calkiem.naukowa.it/fullchain.pem
Private Key Path: /etc/letsencrypt/live/calkiem.naukowa.it/privkey.pem
Certificate Name: img.koala.poznan.pl
Serial Number: 381032732bd9f53172d3e4d78a982b2ae26
Key Type: RSA
Domains: img.koala.poznan.pl
Expiry Date: 2022-05-23 17:26:45+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/img.koala.poznan.pl/fullchain.pem
Private Key Path: /etc/letsencrypt/live/img.koala.poznan.pl/privkey.pem
Certificate Name: koala.poznan.pl
Serial Number: 30a31df9afd3bd7e113fd520c13959394b0
Key Type: RSA
Domains: koala.poznan.pl www.koala.poznan.pl
Expiry Date: 2022-03-31 20:40:49+00:00 (VALID: 36 days)
Certificate Path: /etc/letsencrypt/live/koala.poznan.pl/fullchain.pem
Private Key Path: /etc/letsencrypt/live/koala.poznan.pl/privkey.pem


andrzej@koala:/var/www/html$

What's in /var/log/apache2/error.log?

(use three backticks ``` on the line before you paste and another three on the line after. by themselves)

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