I am currently in the process of setting up a dedicated API backend for a website that operates on /mypath, but I am encountering issues with NGINX not properly proxying requests.
Below is the nginx configuration located within the sites-enabled directory:
upstream backend_website {
server 127.0.0.1:5173;
}
upstream backend_api {
server 127.0.0.1:5001;
}
# HTTP
#
server {
listen 80;
listen [::]:80;
server_name example.com;
# Redirect to HTTPS (:443)
return 301 https://$host$request_uri;
}
# HTTPS
#
server {
listen 443 ssl;
listen [::]:443 ssl;
ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
server_name example.com;
location / {
include proxy_params;
proxy_pass https://backend_website;
}
location /mypath {
include proxy_params;
proxy_pass https://backend_api;
}
}
The code snippet from the index.ts file for the service is displayed below:
import cors from "cors";
import express from "express";
import { config } from "config";
import { MyController } from "controllers/my.controller";
import * as https from "https";
import * as fs from "fs";
const certificate = fs.readFileSync("/etc/letsencrypt/live/example.com/fullchain.pem", "utf8");
const privateKey = fs.readFileSync("/etc/letsencrypt/live/example.com/privkey.pem", "utf8");
const app = express();
app.use(express.json());
app.use(cors());
app.use("/", MyController );
const httpsServer = https.createServer({
cert: certificate,
key: privateKey
}, app);
httpsServer.listen(config.PORT, "127.0.0.1", () => console.log(`Running api on https://127.0.0.1:${ config.PORT }/`));
Despite the setup, the server fails to correctly proxy requests to the API when accessed through the designated /mypath. While the root path (utilizing Vite) functions smoothly, attempting to access /mypath results in a Cannot GET /mypath error. Checking via lynx.browser.org reveals that 127.0.0.1:5001 does indeed work, indicating an issue somewhere within the NGINX configuration.