HTTPS connection to NGINX Proxy Manager

[ad_1]

Hi there,
I’m currently running WordPress in a Docker stack, and it it proxied through Nginx Proxy Manager to the outside world. Visitors see the HTTPS lock, all is well there.

My issue is, the connection between Nginx Proxy Manager and WordPress is over HTTP, so anyone on the wire could see login credentials, for example. Is there an easy way to configure a self-signed certificate on the WordPress side to allow for Nginx Proxy Manager to communicate with WordPress over HTTPS?

Thanks!

How to solve the connection between Nginx Proxy Manager and WordPress is over HTTP? Read below:

To solve the connection between Nginx Proxy Manager and WordPress over HTTP, you will need to configure Nginx Proxy Manager to use HTTPS when connecting to WordPress.

Here are the steps to do this:

1. Obtain an SSL/TLS certificate for your domain. You can obtain a free certificate from Let’s Encrypt or purchase one from a certificate authority.
2. Install the certificate on Nginx Proxy Manager. This can typically be done through the Nginx Proxy Manager web interface or by modifying the Nginx configuration files directly.
3. Configure Nginx Proxy Manager to use HTTPS when proxying requests to WordPress. This can also typically be done through the Nginx Proxy Manager web interface or by modifying the Nginx configuration files.
4. Update the WordPress site URL to use HTTPS. This can be done by logging in to the WordPress dashboard and going to Settings > General. In the WordPress Address (URL) and Site Address (URL) fields, update the URLs to use HTTPS.
5. Flush the WordPress cache, if applicable. If you are using a caching plugin or a server-side caching solution, you will need to flush the cache to ensure that the changes take effect.
6. Test the connection to ensure that it is working properly. You can do this by visiting the WordPress site using a web browser and checking that the connection is secure (displaying a lock icon in the address bar).

If you continue to have problems, you may need to troubleshoot further to identify the cause of the issue. Some common issues to check include misconfigured SSL/TLS certificates, firewall rules, and server-side caching.

 

[ad_2]