NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Adding a Custom Location takes the Site offline

Open
#929 25 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

Are you in the right place?

  • Yes

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
  • If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Yes

Describe the bug

  • I have a very simple Site setup, which proxies to a quasar app (Works). The only thing I have enabled (though I tried all settings) is to force ssl
  • Now everything works fine. I can reach my site under the domain name. SSL is enabled, http requests get redirected to https
  • Now I edit the Proxy Host and add a custom location /api
  • Upon Saving my changes the site is taken offline

To Reproduce
Steps to reproduce the behavior:

  1. Create a Simple Proxy Host with SSL (Lets Encrypt Enabled)
  2. After Certificate is setup make sure the site is reachable
  3. Now Edit the proxy host and add a simple Custom location (/api)
  4. Site is taken offline

Expected behavior
The Site stays online and is reachable. The /api Url is also reachable

Operating System

  • Current Debian as Docker host

Additional context
Basically I am trying to host a modern SPA Website. The Frontend is created using quasar/vue 3 and the Backend, which is a simple rest api is done using Dotnet Core C#. I want to host the quasar App under / and the api under /api.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue using the listed Proxy Host, SSL, and /api Custom Location steps on the Docker setup described. The issue names no source files or tests, so inspect the generated proxy configuration and the failure behavior after saving. Done means the existing site remains reachable and /api is reachable as well.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.