Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] MCP SSE endpoint event omits the /server prefix, so clients behind the built-in nginx proxy get a 404 on /mcp/messages

Chiusa Adatta ai principianti
  • Qualcosa non va?
#1,854 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #1855 di @frdmn — integrata

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
nginx, python
Ambito
api, backend, networking

Direzione di ricerca

Inizia da server/api_server/mcp_endpoint.py, nell’emissione dell’endpoint SSE intorno alla riga 1061. Poi esamina come il proxy nginx integrato instrada /server/mcp/messages e come si comporta direttamente l’endpoint MCP. Riproduci il problema con i passaggi curl nell’issue e confronta i percorsi degli endpoint pubblicizzati. Il lavoro è completato quando l’evento SSE pubblicizza un URL che funziona tramite il proxy incluso e la richiesta del messaggio non riceve più un 404 da nginx.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What installation are you running?

Production (netalertx) 📦

Is there an existing issue for this?
The issue occurs in the following browsers. Select at least 2.
  • N/A - This is an issue with the backend
Current Behavior

When you connect to the MCP server through the built-in nginx proxy (http://<host>:20211/server/mcp/sse), the SSE endpoint event sends back an absolute path that has no /server prefix:

event: endpoint
data: /mcp/messages?session_id=0b6b10b07cd94f9989df9c38be26ed77

MCP clients resolve this against the origin and send their requests to http://<host>:20211/mcp/messages?.... nginx has no route for that path and tries to serve it as a static file from /app/front, which returns a 404. The client never finishes connecting. Claude Code shows Error POSTing to endpoint (HTTP 404): ... nginx.

The same request with the /server prefix works (202). Only the advertised URL is wrong. The cause is in server/api_server/mcp_endpoint.py:1061:

yield f"event: endpoint\ndata: /mcp/messages?session_id={session_id}\n\n"

Related but different: #1275 (MCP server), #1440 (backend and reverse proxy setup).

Expected Behavior

The advertised endpoint should resolve to a working URL behind the bundled proxy. Two possible fixes:

  • Send a relative path (messages?session_id=...). It resolves against .../mcp/sse, so it works both directly and behind any prefix.
  • Prepend the prefix from X-Forwarded-Prefix or request.script_root, and have the bundled nginx set that header for /server.

Workaround: connect straight to http://<host>:<GRAPHQL_PORT>/mcp/sse. This bypasses the reverse proxy and any auth middleware in front of it.

Steps To Reproduce
H='Authorization: Bearer <API_TOKEN>'; S='Sec-Fetch-Site: same-origin'
curl -sN -H "$H" -H "$S" http://<host>:20211/server/mcp/sse   # -> data: /mcp/messages?session_id=XYZ

curl -X POST -H "$H" -H "$S" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"ping"}' \
  "http://<host>:20211/mcp/messages?session_id=XYZ"           # -> 404 (nginx)

curl -X POST -H "$H" -H "$S" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"ping"}' \
  "http://<host>:20211/server/mcp/messages?session_id=XYZ"    # -> 202 accepted
Relevant app.conf settings
LOG_LEVEL='trace'
API_TOKEN='<redacted>'
# GRAPHQL_PORT=20214 set via environment
docker-compose.yml
services:
  netalertx:
    image: ghcr.io/netalertx/netalertx:latest
    container_name: netalertx
    network_mode: host
    read_only: true
    restart: unless-stopped
    cap_drop:
      - ALL
    cap_add:
      - NET_ADMIN
      - NET_RAW
      - NET_BIND_SERVICE
      - CHOWN
      - SETUID
      - SETGID
    volumes:
      - ./data:/data
      - /etc/localtime:/etc/localtime:ro
    tmpfs:
      - "/tmp:mode=1700,uid=0,gid=0,rw,noexec,nosuid,nodev,async,noatime,nodiratime"
    environment:
      PUID: "20211"
      PGID: "20211"
      LISTEN_ADDR: "0.0.0.0"
      PORT: "20211"
      GRAPHQL_PORT: "20214"
Debug or Trace enabled
  • I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.
Relevant app.log section
12:55:43 [MCP] Created session: 0b6b10b07cd94f9989df9c38be26ed77
12:55:46 [HTTP] POST /mcp/messages from 127.0.0.1
127.0.0.1 - - [21/Oct/2026 12:55:46] "POST /mcp/messages?session_id=0b6b10b07cd94f9989df9c38be26ed77 HTTP/1.1" 202 -
12:55:46 [MCP] Deleted session: 0b6b10b07cd94f9989df9c38be26ed77

nginx-access.log: the unprefixed request gets a 404, the prefixed one is proxied and gets a 202:

<client> - - [21/Oct/2026:12:55:46 +0200] "POST /mcp/messages?session_id=0b6b10b07cd94f9989df9c38be26ed77 HTTP/1.1" 404 146 "-" "curl/8.7.1" "-"
<client> - - [21/Oct/2026:12:55:46 +0200] "POST /server/mcp/messages?session_id=0b6b10b07cd94f9989df9c38be26ed77 HTTP/1.1" 202 37 "-" "curl/8.7.1" "-"

nginx-error.log: the unprefixed path falls through to static file serving:

2026/10/21 12:55:46 [error] 253#253: *40 open() "/app/front/mcp/messages" failed (2: No such file or directory), client: <client>, server: , request: "POST /mcp/messages?session_id=0b6b10b07cd94f9989df9c38be26ed77 HTTP/1.1", host: "<host>:20211"
Docker Logs
12:53:20 [MCP] Cleaning up expired session: bdf10972895f4efeafecfcf7b50d76c4

(docker logs netalertx --tail 200 2>&1 | grep -iE "mcp|error": nothing else relevant. The 404 happens in nginx before the request reaches the backend.)

Lingua principale
Python
Stelle
7.2k
Fork
456
Merge medio
16h 25m
PR unite (30g)
30

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di netalertx/NetAlertX

Tutte le issue di netalertx/NetAlertX

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.