Nginx Proxy Manager: Can you use single IP address (no hostname) and different ports or paths to forward to different docker container applications?

2 min read 22-10-2024

the ifix

Nginx Proxy Manager: Can you use single IP address (no hostname) and different ports or paths to forward to different docker container applications?

In today's digital landscape, managing multiple web applications can be challenging, especially when you're running various services within Docker containers. One common question that arises is: Can you use a single IP address (without a hostname) along with different ports or paths to forward requests to different Docker container applications using Nginx Proxy Manager?

Understanding Nginx Proxy Manager

Nginx Proxy Manager is a user-friendly application that provides a simple interface for managing Nginx proxies. With it, you can easily configure reverse proxy hosts, stream services, and manage SSL certificates—all without needing to dive deep into configuration files.

Original Problem Scenario

Here’s a simplified version of the original query:

Can you use a single IP address (without a hostname) along with different ports or paths to forward to different Docker container applications using Nginx Proxy Manager?

Clarifying the Problem

The essence of the problem is whether it’s feasible to use a single IP address to route traffic to multiple Docker containers, each running different applications, using Nginx Proxy Manager. The answer is yes, and here's how you can achieve that!

Solution Overview

Using Different Ports

You can run multiple applications on different ports of the same IP address. For example, suppose you have the following applications running on Docker:

App 1: A web application on port 3000
App 2: A REST API on port 4000

By configuring Nginx Proxy Manager, you can route the requests based on the port number.

Configuring Nginx Proxy Manager

Set Up Your Docker Containers: Make sure your applications are accessible on their respective ports. You can run them using Docker Compose or individual Docker commands.
```
version: '3'
services:
  app1:
    image: your/app1
    ports:
      - "3000:3000"
  app2:
    image: your/app2
    ports:
      - "4000:4000"
```
Add Proxy Hosts in Nginx Proxy Manager:
- For App 1:
  - Domain Name: (Leave empty)
  - Scheme: http
  - Forward Hostname/IP: localhost
  - Forward Port: 3000
- For App 2:
  - Domain Name: (Leave empty)
  - Scheme: http
  - Forward Hostname/IP: localhost
  - Forward Port: 4000
Accessing the Applications:
- App 1 will be accessible at http://<your-ip-address>:3000
- App 2 will be accessible at http://<your-ip-address>:4000

Using Different Paths

If you prefer to use paths instead of ports, you can achieve this through Nginx's routing capabilities. This can make your applications accessible under a single hostname/IP:

Modify your Docker Setup: Ensure your applications are running.
Add Proxy Hosts in Nginx Proxy Manager:
- For App 1:
  - Domain Name: (Leave empty)
  - Scheme: http
  - Forward Hostname/IP: localhost
  - Forward Port: 3000
  - Location: /app1
- For App 2:
  - Domain Name: (Leave empty)
  - Scheme: http
  - Forward Hostname/IP: localhost
  - Forward Port: 4000
  - Location: /app2
Accessing the Applications:
- App 1 will be accessible at http://<your-ip-address>/app1
- App 2 will be accessible at http://<your-ip-address>/app2

Conclusion

Nginx Proxy Manager provides a flexible solution for routing traffic to multiple Docker containers using a single IP address. You can either use different ports or paths to distinguish between your applications. This capability is particularly useful for developers managing several microservices or applications hosted on a single server.

Additional Resources

Implementing the above configurations will allow you to effectively manage and access your applications seamlessly. For developers and system administrators, mastering these configurations can significantly enhance your workflow and operational efficiency.