mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #780] Support for limiting number of connections #659
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#659
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wpresident on GitHub (Dec 18, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/780
I need limit max connection speed for clients and i try this lines for my config:
When i insert it to
server {then server can't start and shows error:
How to user this properly with NPM?
@thytetgc commented on GitHub (Mar 15, 2021):
limit_rate is working fine!
But connection limit does not work!
It would be very good if there is support for
https://github.com/cfsego/limit_upload_rate
@chaptergy commented on GitHub (May 12, 2021):
See https://github.com/jc21/nginx-proxy-manager/issues/116
@mgutt commented on GitHub (May 18, 2023):
Does it? I tested the following code, but it has no effect 😢
I even tested only
limit_rate 1250k;outside the location block (= server block), but still no bandwidth limitation while downloading files 🤔PS the
Strict-Transport-Securityheader is set, so the condition works.@github-actions[bot] commented on GitHub (Mar 22, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 3, 2025):
Issue was closed due to inactivity.