Hi,
I’ve been using Torizon’s remote access feature for a while, but today it stopped working. I now see the error message: “You do not have the required permission to use this feature.” The feature still works for the repository owner. However, despite having “full access” permissions to this repository, I cannot use it.
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
It seems like you are encountering a permissions issue with Torizon’s remote access feature. Here are a few steps you can take to troubleshoot and potentially resolve the issue:
Verify Permissions: Double-check that your user account has the correct permissions set in Torizon Cloud. Even though you mentioned having “full access” permissions, it’s worth re-confirming this in the Torizon Cloud interface.
Check Role Assignments: Ensure that your role within the repository or project includes permissions for remote access. Sometimes, roles and permissions can be granular, and specific features might require additional permissions.
Repository Owner Confirmation: Since the feature still works for the repository owner, ask the owner to verify and, if necessary, reassign your permissions. They can also check if there have been any recent changes to the permissions or roles that might have affected your access.
Session Management: Ensure that there are no active sessions that might be causing conflicts. You can do this by going to the Remote Access Manager on the Account page and closing any active sessions.
Rate Limits and Bans: Check if your IP address has been rate-limited or banned. If you see the error message kex_exchange_identification: read: Connection reset, it might indicate that your IP has hit the rate limit and is temporarily banned.
Contact Support: If the above steps do not resolve the issue, it might be best to contact Toradex support for further assistance. Provide them with the error message and any relevant details, such as the screenshot and the steps you’ve already taken.
If you need more specific guidance or if the issue persists, please reach out to Toradex support directly for a more detailed investigation.
Thanks for this bug report. We rolled out some changes to our authn service over the weekend, and this may have been an oversight.
We’re looking at reproducing the bug now. I’ll update this thread with more details as we continue.
We identified the issue; although a sufficient role was correctly assigned for the needed permission, the UI was checking for the presence of a different role (that would have also granted sufficient permissions).
I’ve pushed a fix now; can you please confirm that the issue is no longer present? You may need to refresh the browser tab and/or log out and log back in again.
