Скачать или смотреть How to Use One SSL Certificate for Different Ports on Nginx

Learn how to configure Nginx to support SSL for different ports efficiently using a single SSL certificate.
---
This video is based on the question https://stackoverflow.com/q/68542990/ asked by the user 'Harvir' ( https://stackoverflow.com/u/16195196/ ) and on the answer https://stackoverflow.com/a/68556195/ provided by the user 'slauth' ( https://stackoverflow.com/u/6756090/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to use one ssl certificate for different ports on nginx

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Use One SSL Certificate for Different Ports on Nginx

Configuring SSL for multiple services running on different ports in Nginx can be challenging. One common scenario arises when you have a React app running on port 3000 and a Node.js API on port 5000, and only one service is accessible over HTTPS when the others remain on HTTP. This guide will guide you on how to effectively use a single SSL certificate to manage requests for both ports via Nginx.

Understanding the Problem

When you secure a specific port (like 3000 for your React app), it handles HTTPS requests correctly, but a request to another port (like 5000 for your Node.js API) might still be left unprotected as HTTP. This setup can lead to complications when your application tries to communicate with other services, especially in a production environment.

The Solution

Focus on a Single SSL Port

You typically only need to enable SSL on one port—port 443, the default for HTTPS. This way, you can direct incoming requests to different backend services using identifiable methods.

Distinguishing Incoming Requests

To effectively manage multiple services behind a single SSL certificate, you can use one of the following approaches:

Separate Subdomains:

Assign a distinct subdomain for the API service (e.g., api.merkle.org). Both your frontend and backend can then run on different subdomains while being protected by SSL.

Note: You may require an additional SSL certificate for the subdomain or a wildcard certificate that includes both the main domain and subdomains.

Routing by URL Path:

You can route based on URL path, for instance, directing all API requests to /api.

Example: Routes can be established under a designated path allowing requests to be effortlessly distinguished.

Example Nginx Configuration

Here is a sample configuration you would implement in your Nginx settings to achieve this.

[[See Video to Reveal this Text or Code Snippet]]

Key Elements in the Configuration:

HTTP to HTTPS Redirect: The first server block redirects all incoming HTTP requests to HTTPS.

SSL Configuration: The second server block configures SSL with your certificate and key.

Proxy Pass: The location directive specifies the backend connection for both the React frontend and the Node.js API.

Conclusion

By using a single SSL certificate with Nginx effectively, you can manage multiple services without compromising security. Whether you go for separate subdomains or a URL path to distinguish requests, ensuring all communications are encrypted and secure is paramount in today’s web applications.

If you're deploying these changes on AWS EC2, ensure your security groups allow traffic on the necessary ports (80 and 443) for successful communication.

By applying these techniques, you can ensure your applications run smoothly while maintaining a high level of security.