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

Coterm Does Not Support Multiple Nodes #50

Closed
2 tasks done
ericwang401 opened this issue Nov 6, 2023 · 0 comments
Closed
2 tasks done

Coterm Does Not Support Multiple Nodes #50

ericwang401 opened this issue Nov 6, 2023 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@ericwang401
Copy link
Collaborator

Current Behavior

One instance of Coterm can only be set to proxy one node for now.

Expected Behavior

Coterm should be able to be used for multiple nodes. The reason it is limited to one node is because Coterm only accepts 1 set of credentials and every node generates their own set of credentials.

In order to make Coterm support multiple nodes, nodes should share Coterm credentials instead of each generating their own unique credentials.

A new table in the database can be created to house all the instances of Coterm, and if a node has Coterm enabled, it is simply linked to one of the available Coterm instances in the Coterm table through a Has-One relationship.

Steps to Reproduce

N/A

Screenshots

No response

Proxmox OS Version

N/A

Operating System

N/A

Browser

N/A

Additional Context

No response

Panel Version

N/A

Error Logs

N/A

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
@ericwang401 ericwang401 added not confirmed The bug isn't confirmed to be reproducible/valid concern bug Something isn't working and removed not confirmed The bug isn't confirmed to be reproducible/valid concern labels Nov 6, 2023
@ericwang401 ericwang401 added this to the v4.0.0-beta milestone Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant