If Possible to change Agent Connection Port
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
I'm running Remotely in Docker-Compose with Nginx Agent Proxy, Hardware Firewall and is working great. If there is possibility to change Agent Connection port so I can lock down Access URL https://remotely.mydomain.com to only specific IP Address. Agents are in remote locations and If lock down Port 443 which is also the URL to access Remotely, then Remote Agents will not be able to connect.
Describe the solution you'd like
If possible, to change Agent Connection Port to something else than Port 5000 (Port 443 with Nginx) which is for accessing management URL.
Describe alternatives you've considered
Currently, not having any alternative way or workaround.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the configuration and connection handling for the agent's port, then determine how management access through Nginx and agent connectivity are separated; done means the agent port can be configured independently and both access paths work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, nginx
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100