starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 09:55:51 +03:00

[GH-ISSUE #3230] website without port / only path #2184

New issue

Closed

opened 2026-02-26 07:34:23 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:34:23 +03:00

Owner

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

I already use NginxProxyManager for 4 webpages without any problems. Now I would like to run our time tracking via the proxy. I can do whatever I want, I can't manage it. The frontend is made available via port 80. But according to the manufacturer, the frontend cannot be opened via the port. Only a provided path works. Now I have the problem that Nginx necessarily expects a port. Has anyone ever had a problem like this? And if so, is there a solution for this?

Many thanks in advance for our help
Alexander Schmidt

Originally created by @schmidtas on GitHub (Oct 2, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3230 I already use NginxProxyManager for 4 webpages without any problems. Now I would like to run our time tracking via the proxy. I can do whatever I want, I can't manage it. The frontend is made available via port 80. But according to the manufacturer, the frontend cannot be opened via the port. Only a provided path works. Now I have the problem that Nginx necessarily expects a port. Has anyone ever had a problem like this? And if so, is there a solution for this? Many thanks in advance for our help Alexander Schmidt

kerem

2026-02-26 07:34:23 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:23 +03:00

Author

Owner

@UndyingSoul commented on GitHub (Oct 3, 2023):

The PiHole project has a similar issue to yours, in which the admin panel isn't located at the root page (ex. http://127.0.0.1/) instead, you have to specify the page you want to load at the root / location (ex. http://127.0.0.1/admin/).

By default, when you load http://127.0.0.1, your browser assumes you're trying to load port 80, but it's a good idea to specify it anyway. Not the problem here.

Try creating a proxy by specifying the forward hostname like your.service.host.ip:80 then under the custom locations, define the location / to forward to your.service.host.ip:80/path/you/want/to/use

Relevant issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1027

P.S. The GitHub issues is not the most appropriate place for support. I recommend heading over to reddit and get help from there.

Not a bug, recommending the issue to be closed.

@UndyingSoul commented on GitHub (Oct 3, 2023): The PiHole project has a similar issue to yours, in which the admin panel isn't located at the root page (ex. `http://127.0.0.1/`) instead, you have to specify the page you want to load at the root `/` location (ex. `http://127.0.0.1/admin/`). By default, when you load `http://127.0.0.1`, your browser assumes you're trying to load port 80, but it's a good idea to specify it anyway. Not the problem here. Try creating a proxy by specifying the forward hostname like `your.service.host.ip:80` then under the custom locations, define the location `/` to forward to `your.service.host.ip:80/path/you/want/to/use` Relevant issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1027 P.S. The GitHub issues is not the most appropriate place for support. I recommend heading over to reddit and get help from there. Not a bug, recommending the issue to be closed.

kerem commented

2026-02-26 07:34:23 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 5, 2024):

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

@github-actions[bot] commented on GitHub (Apr 5, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:34:23 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 2, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Jun 2, 2025): Issue was closed due to inactivity.

No milestone

No project

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#2184

No description provided.

Rows
Columns