starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #3255] 502 Bad Gateway, connect failed (refused) while connecting to upstream, Can't Load Either Frontend nor Backend #2196

New issue
Closed
opened 2026-02-26 07:34:27 +03:00 by kerem · 4 comments
kerem commented 2026-02-26 07:34:27 +03:00
Owner
Copy link

Originally created by @khalidrizki01 on GitHub (Oct 13, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3255

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes (Haven't found similar issues)

Describe the bug
I'm still new to nginx and full stack web deployment. I'm encountering a 502 Bad Gateway error every time I attempt to load both the frontend and backend. I've dockerized my application into frontend (React Vite) and backend (FastAPI Python) containers, then deployed them on a VPS. I've configured the proxy host using Nginx Proxy Manager. The configuration for the frontend proxy host is as follows:

server {
  set $forward_scheme https;
  set $server         "frontend";
  set $port           5173;

  listen 80;
  listen [::]:80;

  listen 443 ssl http2;
  listen [::]:443 ssl http2;

  server_name myweb.mydomain.com;

  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-1/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-1/privkey.pem;

  # Block Exploits
  include conf.d/include/block-exploits.conf;

  # Force SSL
  include conf.d/include/force-ssl.conf;

  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_http_version 1.1;

  access_log /data/logs/proxy-host-1_access.log proxy;
  error_log /data/logs/proxy-host-1_error.log warn;

  location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;

    # Proxy!
    include conf.d/include/proxy.conf;
  }

  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

And here's the configuration for the backend proxy host:

server {
  set $forward_scheme https;
  set $server         "backend";
  set $port           8000;

  listen 80;
  listen [::]:80;

  listen 443 ssl http2;
  listen [::]:443 ssl http2;

  server_name api.myweb.mydomain.com;

  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem;

  include conf.d/include/block-exploits.conf;

  include conf.d/include/force-ssl.conf;

  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection $http_connection;
  proxy_http_version 1.1;

  access_log /data/logs/proxy-host-2_access.log proxy;
  error_log /data/logs/proxy-host-2_error.log warn;

  location / {
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;

    # Proxy!
    include conf.d/include/proxy.conf;
  }

  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

My Docker Compose file looks like this:

version: "3"
name: "jawabot-development"
services:
  backend:
    restart: always
    build: 
      context: ./backend
      dockerfile: Dockerfile
    env_file:
    - ./backend/dev.env
    networks:
      - nginx-proxy
      - jawabot-dev-network
    command: uvicorn main:app --reload --port 8000 --proxy-headers
  frontend:
    build:
      context: ./frontend
      dockerfile: Dockerfile
    depends_on:
      - backend
    networks:
      - nginx-proxy
      - jawabot-dev-network
    command: npm run dev -- --port 5173

networks:
  nginx-proxy:
    name: nginx-proxy
    external: true
  jawabot-dev-network:
    name: jawabot-dev-network

The error logs for both frontend and backend show a connection refused error with an upstream IP address of https://172.#.#.#. However, my VPS IP is 203.#.#.#. Below are the logs:

frontend proxy host error logs:
`

2023/10/12 23:59:47 [error] 771#771: *2578 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: myweb.mydomain.com, request: "GET / HTTP/2.0", upstream: "https://172.~.~.~:5173/", host: "myweb.mydomain.com"

2023/10/12 23:59:47 [error] 771#771: *2578 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: myweb.mydomain.com, request: "GET /favicon.ico HTTP/2.0", upstream: "https://172.~.~.~:5173/favicon.ico", host: "frontend.myweb.mydomain.com", referrer: "https://myweb.mydomain.com/"

backend proxy host error logs:

2023/10/13 00:27:01 [error] 805#805: *2717 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: api.myweb.mydomain.com, request: "GET / HTTP/2.0", upstream: "https://172.~.~.~:8000/", host: "api.myweb.mydomain.com"

2023/10/13 00:27:01 [error] 805#805: *2717 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: api.myweb.mydomain.com, request: "GET /favicon.ico HTTP/2.0", upstream: "https://172.~.~.~:8000/favicon.ico", host: "api.myweb.mydomain.com", referrer: "https://api.myweb.mydomain.com/"

Thank you for your help!

Nginx Proxy Manager Version
2.10.4

To Reproduce
Steps to reproduce the behavior:

  1. docker compose -f docker-compose.dev.yml
  2. set up the nginx proxy host configurations (for frontend and backend) through nginx proxy manager
  3. Load the frontend or backend from my local pc through a web browser

Expected behavior
Can load the frontend and backend from local pc

Screenshots
502 bad gateway
image

backend proxy host configuration:
image

frontend proxy host configuration:
image

Operating System
Ubuntu 22.04.1 LTS

Additional context
Additionally, I've included CORS settings in the backend and an API URL in the frontend as follows:

backend (fastapi python):

app = FastAPI()

origins = [
    "http://frontend:5173",
    "https://frontend:5173"]

app.add_middleware(
    CORSMiddleware,
    allow_origins = origins,
    allow_credentials = True,
    allow_methods=['*'],
    allow_headers=['*'],
)
...

frontend (react vite)

const API_URL="https://backend:8000"

function App() {
...
  async function processMessageToJawabot(chatMessages){
    await fetch(`${API_URL}/ask`,{
      method: 'POST',
      mode: 'cors',
      headers: {
        "Content-Type" : "application/json"
      },
      body : JSON.stringify({"question": chatMessages[chatMessages.length-1].message})
    }).then((response) => {
      return response.json()
    })
...
  }
}

Below is the docker compose for my nginx proxy manager:

version: '3.8'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    networks:
      - nginx-proxy

networks:
  nginx-proxy:
    name: nginx-proxy
    external: true
Originally created by @khalidrizki01 on GitHub (Oct 13, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3255 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes (Haven't found similar issues) **Describe the bug** I'm still new to nginx and full stack web deployment. I'm encountering a 502 Bad Gateway error every time I attempt to load both the frontend and backend. I've dockerized my application into frontend (React Vite) and backend (FastAPI Python) containers, then deployed them on a VPS. I've configured the proxy host using Nginx Proxy Manager. The configuration for the frontend proxy host is as follows: ``` server { set $forward_scheme https; set $server "frontend"; set $port 5173; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; server_name myweb.mydomain.com; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-1/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-1/privkey.pem; # Block Exploits include conf.d/include/block-exploits.conf; # Force SSL include conf.d/include/force-ssl.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; access_log /data/logs/proxy-host-1_access.log proxy; error_log /data/logs/proxy-host-1_error.log warn; location / { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } ``` And here's the configuration for the backend proxy host: ``` server { set $forward_scheme https; set $server "backend"; set $port 8000; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; server_name api.myweb.mydomain.com; include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem; include conf.d/include/block-exploits.conf; include conf.d/include/force-ssl.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; access_log /data/logs/proxy-host-2_access.log proxy; error_log /data/logs/proxy-host-2_error.log warn; location / { proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } ``` My Docker Compose file looks like this: ``` version: "3" name: "jawabot-development" services: backend: restart: always build: context: ./backend dockerfile: Dockerfile env_file: - ./backend/dev.env networks: - nginx-proxy - jawabot-dev-network command: uvicorn main:app --reload --port 8000 --proxy-headers frontend: build: context: ./frontend dockerfile: Dockerfile depends_on: - backend networks: - nginx-proxy - jawabot-dev-network command: npm run dev -- --port 5173 networks: nginx-proxy: name: nginx-proxy external: true jawabot-dev-network: name: jawabot-dev-network ``` The error logs for both frontend and backend show a connection refused error with an upstream IP address of https://172.#.#.#. However, my VPS IP is 203.#.#.#. Below are the logs: frontend proxy host error logs: ` ``` 2023/10/12 23:59:47 [error] 771#771: *2578 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: myweb.mydomain.com, request: "GET / HTTP/2.0", upstream: "https://172.~.~.~:5173/", host: "myweb.mydomain.com" 2023/10/12 23:59:47 [error] 771#771: *2578 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: myweb.mydomain.com, request: "GET /favicon.ico HTTP/2.0", upstream: "https://172.~.~.~:5173/favicon.ico", host: "frontend.myweb.mydomain.com", referrer: "https://myweb.mydomain.com/" ``` backend proxy host error logs: ``` 2023/10/13 00:27:01 [error] 805#805: *2717 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: api.myweb.mydomain.com, request: "GET / HTTP/2.0", upstream: "https://172.~.~.~:8000/", host: "api.myweb.mydomain.com" 2023/10/13 00:27:01 [error] 805#805: *2717 connect() failed (111: Connection refused) while connecting to upstream, client: my-local-pc-ip-addr, server: api.myweb.mydomain.com, request: "GET /favicon.ico HTTP/2.0", upstream: "https://172.~.~.~:8000/favicon.ico", host: "api.myweb.mydomain.com", referrer: "https://api.myweb.mydomain.com/" ``` Thank you for your help! **Nginx Proxy Manager Version** 2.10.4 **To Reproduce** Steps to reproduce the behavior: 1. docker compose -f docker-compose.dev.yml 2. set up the nginx proxy host configurations (for frontend and backend) through nginx proxy manager 3. Load the frontend or backend from my local pc through a web browser **Expected behavior** Can load the frontend and backend from local pc **Screenshots** 502 bad gateway ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/79208746/d543147c-af8f-4b90-86a5-55c8e0a7d71e) backend proxy host configuration: ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/79208746/dd5e9084-cbee-4f92-9457-1e845c00cb96) frontend proxy host configuration: ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/79208746/930b3636-78a1-4616-bdcd-8562225bb9f2) **Operating System** Ubuntu 22.04.1 LTS **Additional context** Additionally, I've included CORS settings in the backend and an API URL in the frontend as follows: backend (fastapi python): ``` app = FastAPI() origins = [ "http://frontend:5173", "https://frontend:5173"] app.add_middleware( CORSMiddleware, allow_origins = origins, allow_credentials = True, allow_methods=['*'], allow_headers=['*'], ) ... ``` frontend (react vite) ``` const API_URL="https://backend:8000" function App() { ... async function processMessageToJawabot(chatMessages){ await fetch(`${API_URL}/ask`,{ method: 'POST', mode: 'cors', headers: { "Content-Type" : "application/json" }, body : JSON.stringify({"question": chatMessages[chatMessages.length-1].message}) }).then((response) => { return response.json() }) ... } } ``` Below is the docker compose for my nginx proxy manager: ``` version: '3.8' services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: - '80:80' - '81:81' - '443:443' volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt networks: - nginx-proxy networks: nginx-proxy: name: nginx-proxy external: true ```
kerem 2026-02-26 07:34:27 +03:00
  • closed this issue
  • added the
    stale
    bug
         labels
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@1xtr commented on GitHub (Oct 14, 2023):

If you use backend behind NPM you don't need https
image
Here is my config for one simple service. NPM redirect request to container by container name.

But I'm here because custom locations don't work for me.
Here is props
image
Nginx logs say that upstream don't exist

How I can solve this ?

<!-- gh-comment-id:1762900822 --> @1xtr commented on GitHub (Oct 14, 2023): If you use backend behind NPM you don't need `https` ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/59780048/a81fdf9e-f3e7-4893-8a56-d0a4a1c4ecbb) Here is my config for one simple service. NPM redirect request to container by container name. But I'm here because `custom locations` don't work for me. Here is props ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/59780048/e9e2192f-a96c-4c72-a1d8-687696267e21) Nginx logs say that upstream don't exist How I can solve this ?
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@Meticulous7 commented on GitHub (Dec 1, 2023):

Also here for this issue. OP, ever find a solution?

<!-- gh-comment-id:1836449915 --> @Meticulous7 commented on GitHub (Dec 1, 2023): Also here for this issue. OP, ever find a solution?
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Jul 19, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2237885473 --> @github-actions[bot] commented on GitHub (Jul 19, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:34:28 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Aug 9, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:3169661109 --> @github-actions[bot] commented on GitHub (Aug 9, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#2196
No description provided.