Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Ability to Assign Fixed Ports for Applications in Teleport Connect #49397

Closed
sarvalabs-deepakagrawal opened this issue Nov 25, 2024 · 1 comment
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements

Comments

@sarvalabs-deepakagrawal

I would like to request a feature enhancement in Teleport Connect that allows assigning fixed ports to each application when creating an App Connection.

Current Behavior:

I have configured Teleport with the following application settings:

- name: "devnet15-1600-rpc-call"
  uri: "http://95.216.xxx.xxx:1600/"  # Base URL Teleport proxies to  
  public_addr: "[devnet15-1600.teleport.moinet.io](http://devnet15-1600.teleport.moinet.io/)"       
- name: "devnet14-1600-rpc-call"
  uri: "http://65.109.xxx.xxx:1600/"  # Base URL Teleport proxies to  
  public_addr: "[devnet14-1600.teleport.moinet.io](http://devnet14-1600.teleport.moinet.io/)"
- name: "devnet14-1601-rpc-call"
  uri: "http://65.109.xxx.xxx:1601/"  # Base URL Teleport proxies to  
  public_addr: "[devnet14-1601.teleport.moinet.io](http://devnet14-1601.teleport.moinet.io/)"

When I open devnet14-1600-rpc-call in Teleport Connect, the App Connection assigns a random port (e.g., Port 62430) for local access, as shown below:

App Connection: Port 62430
Access URL: http://localhost:62430/

Desired Behavior:
I would like the ability to specify a static local port for each application in the Teleport configuration. For example:

devnet14-1600-rpc-call should always use Port 1600 locally, even if I log out and log back in to Teleport Connect.
Similarly, other applications should use their designated static ports (e.g., 1601 for devnet14-1601-rpc-call, etc.).
This setting should apply consistently for everyone who has access to the Teleport instance, ensuring uniform port mapping across all users.

This feature would make it easier to manage and remember local ports, avoid conflicts, and improve usability for scenarios requiring fixed port bindings.

@sarvalabs-deepakagrawal sarvalabs-deepakagrawal added the feature-request Used for new features in Teleport, improvements to current should be #enhancements label Nov 25, 2024
@zmb3
Copy link
Collaborator

zmb3 commented Nov 25, 2024

As I mentioned in your discussion post (#49315) we're currently not planning on doing this as we're investing in expanding Teleport VNet to other platforms. VNet completely removes the requirement to set up local proxies or think about local ports.

@zmb3 zmb3 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements
Projects
None yet
Development

No branches or pull requests

2 participants