How to configure Nginx SSL certificate to achieve HTTPS access
Background
Due to project requirements and security reasons, it is necessary to change the previous http interface access to https access, so an SSL certificate needs to be configured. The architecture of the project is like this:
The basic architecture is hard load (readwhere) soft load (nginx) tomcat cluster. The current problem is that the ssl certificate must be configured in Where, configured directly on the hard load? Or configure it on nginx and tomcat respectively? Or is there any other configuration method?
First of all, I gave up configuring the hard load, and then after searching for information on the Internet, I found that I can only configure the certificate on nginx. That is to say, nginx uses https for access, and http is used for connection between nginx and tomcat. This gives you an overall idea.
About ssl certificate
About ssl certificate, here is a brief introduction. It is also because of the needs of the project that I have a brief understanding.
SSL certificates are roughly divided into three types, domain level (dv), enterprise level (ov), and enhanced level (ev), with security and price increasing in order. Choose according to your own needs. For personal use, you can use dv, which is cheap; for corporate use, ov is generally used, and ev is used under special circumstances.
ssl certificate configuration
Because nginx’s support for ssl certificate configuration makes this implementation possible, I have to lament nginx of strength.
Certificate preparation
nginx configuration requires .pem/.crt certificate.key. If you currently have other forms of certificates, please follow the relevant instructions to convert into the required certificate type, otherwise the certificate configuration cannot be completed. Generally, purchasing merchants will have corresponding conversion tools.
After you are ready, place the certificate and secret key in the conf directory of nginx (that is, in the same directory as the configuration file nginx.conf). Special attention needs to be paid here:
If it is configured under a Linux system, it is ready;
If it is configured under a Windows system, the password in the .key secret key file needs to be removed. Otherwise, nginx will not start after configuration. This is a pit. I am stuck here. The specific solution is also very simple. Download the windows version of openssl online, then switch cmd to the bin directory and execute openssl rsa. -in server.key -out server2.key, the generated server2.key is the secret key file required for configuration, but the file name needs to be changed to server.key.
Modify nginx configuration file
The following is part of my nginx.conf configuration file. The port is not the default 443, but changed It becomes 8185. Just modify it according to your needs. Other configurations are basically as follows and there will be no problem.
server { listen 8185; server_name localhost; ssl on; ssl_certificate server.pem; ssl_certificate_key server.key; ssl_session_timeout 5m; ssl_protocols tlsv1 tlsv1.1 tlsv1.2; ssl_ciphers high:!rc4:!md5:!anull:!enull:!null:!dh:!edh:!exp:+medium; ssl_prefer_server_ciphers on; location / { proxy_set_header host $host:$server_port; proxy_set_header x-real-ip $remote_addr; proxy_set_header x-forwarded-for $proxy_add_x_forwarded_for; proxy_set_header x-forwarded-proto $scheme; proxy_connect_timeout 5; proxy_send_timeout 5; proxy_read_timeout 5; proxy_pass http://qlddm_server; }
Modify the tomcat configuration file
Although there is no need to configure the certificate in tomcat, you still need to modify the tomcat configuration server.xml configuration file, which specifically includes two places :
<connector executor="tomcatthreadpool" port="7083" protocol="org.apache.coyote.http11.http11nio2protocol" connectiontimeout="20000" maxconnections="8000" redirectport="8185" proxyport="8185" enablelookups="false" acceptcount="100" maxpostsize="10485760" compression="on" disableuploadtimeout="true" compressionminsize="2048" acceptorthreadcount="2" compressablemimetype="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript" uriencoding="utf-8" />
You need to modify both redirectport and proxyport to your nginx listening port number.
<valve classname="org.apache.catalina.valves.remoteipvalve" remoteipheader="x-forwarded-for" protocolheader="x-forwarded-proto" protocolheaderhttpsvalue="https" httpsserverport="8185"/>
You need to add the above value tag. Note that httpsserverport also needs to be modified to the nginx listening port number.
The above is the detailed content of How to configure Nginx SSL certificate to achieve HTTPS access. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

There are two ways to solve the Nginx cross-domain problem: modify the cross-domain response header: add directives to allow cross-domain requests, specify allowed methods and headers, and set cache time. Use CORS modules: Enable modules and configure CORS rules that allow cross-domain requests, methods, headers, and cache times.

The methods to view the running status of Nginx are: use the ps command to view the process status; view the Nginx configuration file /etc/nginx/nginx.conf; use the Nginx status module to enable the status endpoint; use monitoring tools such as Prometheus, Zabbix, or Nagios.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.
