![]() Mariadb_1 | mariadb 20:56:20.56 Submit issues and feature requests at Mariadb_1 | mariadb 20:56:20.54 Subscribe to project updates by watching Mariadb_1 | mariadb 20:56:20.54 Welcome to the Bitnami mariadb container doneĪttaching to mywordpress_mariadb_1, mywordpress_wordpress_1 *** Logged information when docker-compose is started docker-compose up # END WordPress fix for plugins and themes # Certain WordPress plugins and themes do not properly link to PHP files because of symbolic links # BEGIN WordPress fix for plugins and themes Options -Indexes +FollowSymLinks -MultiViews SSLCertificateKeyFile "/opt/bitnami/apache/conf/bitnami/certs/server.key" SSLCertificateFile "/opt/bitnami/apache/conf/bitnami/certs/server.crt" Include "/opt/bitnami/apache/conf/vhosts/htaccess/nf" SSLCertificateKeyFile "/opt/bitnami/apache/conf/bitnami/certs/otherdomainpriv.pem" SSLCertificateFile "/opt/bitnami/apache/conf/bitnami/certs/otherdomain.pem" WORDPRESS_DATABASE_NAME=bitnami_wordpress WORDPRESS_MULTISITE_HOST=wordpress.domain WORDPRESS_MULTISITE_NETWORK_TYPE=subdirectory persistent-docker-cons/mywordpress/otherdomain:/otherdomain ![]() persistent-docker-cons/mywordpress/vhosts/:/opt/bitnami/apache/conf/vhosts/ ![]() persistent-docker-cons/mywordpress/certs:/certs:ro persistent-docker-cons/mywordpress/wordpress:/bitnami/wordpress persistent-docker-cons/mywordpress/mariadb:/bitnami/mariadb The bottom line is configuration for should should not be in the nf file, unless I'm missing something and there's a valid reason why it's included for the bitnami WordPress docker image.ĭrwxr-xr-x 3 root root 4096 May 27 21:25 back-upsĭrwxr-xr-x 2 1001 1001 4096 May 26 14:08 certs You can view the site after firing up the docker container and creating host entry for and pointing it to 127.0.0.1 and then connecting to the specified port on that container from your host machine. That preconfigered example site/domain makes since for an apache only container, but not for a WordPress container. Since a domain/site for WordPress is configured via its own vhosts conf file, the configuration for in nf is surpurflous and not needed. In the nf there is a domain that's preconfigered called, and since apache can't match the SSL cert for it, it's throwing that error message. The error message is happening because the SSL certs I'm using are for a different domain that I'm using for WordPress.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |