You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use case - running a public node unbounded is generally not the best idea.
i propose adding a documentation on how to perform some basic rate-limits with off the shelf services like nginx or haproxy that a node operator may use if they want to run a node publicly.
Hi, thanks for opening this — this would be very helpful for node operators.
As a newcomer, I think a short step-by-step example (e.g. basic nginx or haproxy config with rate-limits) would make this much easier to follow.
Even a minimal example showing common defaults would help operators avoid exposing nodes unintentionally.
Happy to help review or test docs
Activity
[-]Document how to run a node being a proxy[/-][+]Document how to run a node behind a proxy[/+]wileyj commentedon Jan 16, 2026
note: it should be short and simple
eric-stacks commentedon Jan 26, 2026
would this be a separate guide from the existing "Run a Node..." guides or would it be a small blurb we'd add into one of these existing guides?
wileyj commentedon Jan 26, 2026
Separate - more of a "best practices" type of infra design if a node operator wants to run a public node.
good question though - it should have links from the current "run a node" docs i would think
Royalsuitking commentedon Jan 27, 2026
Hi, thanks for opening this — this would be very helpful for node operators.
As a newcomer, I think a short step-by-step example (e.g. basic nginx or haproxy config with rate-limits) would make this much easier to follow.
Even a minimal example showing common defaults would help operators avoid exposing nodes unintentionally.
Happy to help review or test docs