Update.
The troubles never gone.
What happened: I disabled virtual machine for my second Omeka’s site and then I enabled Domain Manager module and voila!
It was an illusion because Cloudflare made my first site available but when cache gone, Omeka-s display a Not Found page. The second site still working fine.
My configuration:
Debian 9
Omeka-S 2.1.2
Domain Manager 1.2 activated
Apache 2
My first (long last working) site: https://biblioteca.archivosdelarepresion.org
My second (brand new) site: https://biblioteca.archivosdelaresistencia.org
Currently virtual host for my first site is enabled and configured like this:
ServerName: www.biblioteca.archivosdelarepresion.org
ServerAlias: biblioteca.archivosdelarepresion.org
DocumentRoot: /var/www/html
Virtual host for my second site is configured like this:
ServerName: www.biblioteca.archivosdelaresistencia.org
ServerAlias: biblioteca.archivosdelaresistencia.org
DocumentRoot: /var/www/html
Virtual host for my second site is disabled.
DomainManager is activated and configured like this:
Site | Domain
Archivos de la represión | biblioteca.archivosdelarepresion.org
Archivos de la resistencia| biblioteca.archivosdelaresistencia.org
As I said, my second site (Archivos de la resistencia) works fine when I type biblioteca.archivosdelaresistencia.org on my browser but when I type biblioteca.archivosdelarepresion.org Omeka-S shows a Not found page.
If I enable the virtual host for my second site Omeka-S still showing Not Found page for my first site and Apache2 shows its Not found page for my second site.
If I desactivate DomainManager module (and virtual host for second site remains enabled), my first site works fine but my second site doesn’t work and Apache 2 displays its Not found page
If I desactivate DomainManager module and disable virtual host for my second site both domains shows the contents of my first site.
Thank to read above lines, any help and/or suggestions will be appreciate it.
Thanks again.
Ivan.