I’m assuming a pb of mixed content with a Joomla website when I visit it in https and when I’ve set the SEF urls (url rewriting).
I don’t think the pb is from Joomla, because for exemple: I moved a production website from another server and it was working fine on the old server (debian).
I done a test on a fresh Joomla install, and I’ve still the pb.
What I done:
set php7 for the entire server
create a Vhost
create certificat let’s encrypt for this vhost
upload joomla, create database, activate htaccess and RewriteEngine is On
I have a content mixed : CSS, .js and images are not loaded because they aren’t called in SSL.
If I force the https access in joomla params, I have the error: “The page is not redirected correctly” (this message is my translation, “La page n’est pas redirigée correctement” in french).
So, I don’t know what to do now…
Can you help me please ?
The issue is not on NS side
You must be sure that your template can manage https links
Sometimes all CSS files and js ones are linked as http (hardcoded)
I tried it again and it seems to be a problem with joomla and virtualhosts. If you put your joomla site to /var/www/html, which is the NethServer default web site location, it works with HTTPS. This could be a solution for you as your other sites work as vhosts.
But I am still interested, why joomla is not working with virtualhosts so I uncommented the entries in /etc/httpd/conf.d/virtualhosts.conf and Joomla .htaccess but no success.
Well the broken css comes because the vhost name is not part of the ssl certificate. If you create a letsencrypt certificate with the vhost name (let’s say joomla.domain.com) and if in the vhost setting you apply to use the letsencrypt certificate, then the css is no more broken.
Fun
@giacomo and @davidep why do not we repeat to write the ssl certificate setting (SSLCertificateFile,SSLCertificateKeyFile, SSLCertificateChainFile) in each vhost configuration even if it is the default one, for this case we could avoid this bug.
If we set default to the ssl certificate in the vhost panel page, there is no definition and and the self signed certificate is used even if the letsencrypt one is set to default.
I believe we have a bug here
before you ask it…no custom modules
[root@test joomla.de-labrusse.fr]# httpd -S
VirtualHost configuration:
*:443 is a NameVirtualHost
default server test.de-labrusse.fr (/etc/httpd/conf.d/ssl.conf:56)
port 443 namevhost test.de-labrusse.fr (/etc/httpd/conf.d/ssl.conf:56)
port 443 namevhost joomla.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:24)
port 443 namevhost test2.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:90)
port 443 namevhost test3.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:156)
port 443 namevhost wordpress.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:222)
*:80 is a NameVirtualHost
default server test.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:12)
port 80 namevhost test.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:12)
port 80 namevhost joomla.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:57)
port 80 namevhost test2.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:123)
port 80 namevhost test3.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:189)
port 80 namevhost wordpress.de-labrusse.fr (/etc/httpd/conf.d/virtualhosts.conf:255)
ServerRoot: "/etc/httpd"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/etc/httpd/logs/error_log"
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
Mutex authn-socache: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/run/httpd/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex authdigest-opaque: using_defaults
Mutex proxy-balancer-shm: using_defaults
Mutex rewrite-map: using_defaults
Mutex authdigest-client: using_defaults
PidFile: "/run/httpd/httpd.pid"
Define: _RH_HAS_HTTPPROTOCOLOPTIONS
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name="apache" id=48
Group: name="apache" id=48
Thanks