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

Used already activated #254

Open
Coedgy opened this issue Jul 11, 2024 · 2 comments
Open

Used already activated #254

Coedgy opened this issue Jul 11, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Coedgy
Copy link

Coedgy commented Jul 11, 2024

When trying to add instance on an already activated account, the client want's me to set up passwords and such, which leads to an unexpected error. On the proxy servers' logs it shows that the device was added successfully, but then it tries to activate user which leads to the error.

I assume it should only ask me for instance URL, token and device name? The device does get added, but the client doesn't show the instance as it gets stuck on the enrollment.

@teon
Copy link
Contributor

teon commented Aug 15, 2024

@Coedgy can you specify what versions of core, proxy & client do you use?
Did you test on latest?

@Coedgy
Copy link
Author

Coedgy commented Aug 15, 2024

@Coedgy can you specify what versions of core, proxy & client do you use?
Did you test on latest?

All on latest.

@teon teon added the bug Something isn't working label Aug 18, 2024
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
Status: Refined & Ready
Development

No branches or pull requests

2 participants