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.

Sign up for GitHub

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

Jump to bottom

Fix client unable to connect to Core running on custom port #259

Open
Shackless opened this issue Oct 13, 2024 · 2 comments
Open

Fix client unable to connect to Core running on custom port #259

Shackless opened this issue Oct 13, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Shackless
Copy link
Contributor

The client should be able to connect to Core running on a port other than 8000. This currently doesn't work because a Tauri exception is thrown before you can reach the /connect page.
@Shackless
Copy link
Contributor Author

Potentially fixed in the client but needs further testing on Tauri/Windows.

@Shackless Shackless added the bug Something isn't working label Oct 26, 2024
Shackless added a commit that referenced this issue Oct 26, 2024
@Shackless
change default port to 49111 (widely unused)
3064441 
#259
@Shackless
Copy link
Contributor Author

also changed the default port to 49111 on 'develop'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Shackless