[bitnami/wordpress] HTTPS in WordPress Address and Site Address

[Teeptrak]

Name and Version

bitnami/wordpress:17.1.4

What is the problem this feature will solve?

After checking the Bitnami WordPress Docker Image and helm values, I couldn't find a way to have WordPress Address and Site Address to use HTTPS.

wp-config.php seems to be hardcoded with HTTP.

I tried using extraEnvVars:

  - name: WORDPRESS_ENABLE_HTTPS
    value: 'yes'

And also "wordpressScheme: https" but it's not changing anything.
Either I'm doing something wrong or the feature is not available.

Thank you!

What is the feature you are proposing to solve the problem?

Helm values or ENV that would change wp-admin.php HTTP to HTTPS.

What alternatives have you considered?

None yet

[fevisera]

Hi @Teeptrak,

The feature you refer to appears to be already available and can be configured using the wordpressScheme: https setting. After setting this value, when I navigate to https://127.0.0.1/wp-admin/options-general.php I see the https is included in the URL fields:

If you are referring to a different feature or functionality, please provide more details, and I will be happy to assist you further.

Thank you for getting in touch with us.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[Pivert]

Having the same issue with traefik in front handling the https. The pod is http only.

wordpressScheme: https in helm values

But :

1. Get the WordPress URL and associate WordPress hostname to your cluster external IP:

   export CLUSTER_IP=$(minikube ip) # On Minikube. Use: `kubectl cluster-info` on others K8s clusters
   echo "WordPress URL: http://www.pivert.org/"
   echo "$CLUSTER_IP  www.pivert.org" | sudo tee -a /etc/hosts

$ kubectl exec -i -t pivertwp-wordpress-b949cf5db-9h2l6 -- grep '^define.*URL' /bitnami/wordpress/wp-config.php
define( 'WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/' );

I did try:

extraEnvVars:
  - name: WP_SITEURL
    value: https://www.pivert.org/

wordpressSkipInstall: true
## @param wordpressExtraConfigContent Add extra content to the default wp-config.php file
## e.g:
## wordpressExtraConfigContent: |
##   @ini_set( 'post_max_size', '128M');
##   @ini_set( 'memory_limit', '256M' );
##
wordpressExtraConfigContent: |
  define( 'WP_SITEURL', 'https://www.pivert.org/');

But the WP_SITEURL remains in http scheme and the admin interface does not work because of "mixed-content" and CSP.

[carrodher]

Thank you for reaching out and for your interest in our project. We'd be happy to assist you, but to do so effectively, we'll need some more details. Could you please create a separate issue filling the Issue template?

Providing this information will help us better understand your situation and assist you in a more targeted manner.

[Pivert]

Tks. Please consider my case void:

• I was cascading 2 traefik during a migration.
• After the full switch (including turning off the original traefik to prevent being banned by letsencrypt), the problem fixed by itself.
• So I suspect the headers from the origin trafik (http) to override the headers from the internet exposed traefik (https).

Still, it does not explain why the above mentioned settings did not force the WP_SITEURL to the https scheme.

Thanks,