"No sign permission." error while SIGN is granted

[chilly drift]

"No sign permission." error when SIGN is granted

[chilly drift]

"No sign permission." error while SIGN is granted

Debugged the issue and found out that in local IndexedDB of 🆙 extension controllerAddress is different from the Up Browser Extension address 👀 controllerAddress value is unknown to me and I don't know how it got set.

[analog thorn]

hey, sorry for not getting back earlier and thanks for the feedback.

the no sign permission is likely related to the relayer system and our team is looking into this right now. @grim marsh will be able to provide more information there.

Could you provide a screenshot and your profile address?

regarding the controllerAddress being different than the Up Browser Extension @knotty stone might be able to provide further context.

[grim marsh]

Hello! @chilly drift
The fact that some users end up with different controller addresses than the ones they actually have in the UP browser extension is the reason for No sign permission.
I'm working on a fix for this issue and will get back to you soon with updates.

[honest wadi]

Hi @grim marsh , I have the same issue. Is this still being looked into?

[grim marsh]

Hello @honest wadi ! Yes! The solution is under review now and we will notify the community when it's released as we did with previous updates and fixes.

Let me just clarify: did you do an import of a profile from one extension to the other, maybe you recovered your profile, or maybe you did some other actions that you think led to this issue? It's important for us to catch all possible causes and so far we had found one that could happen during import or recovery. I would appreciate any information! Thanks.

[honest wadi]

Hi @grim marsh thank you for your response. I recovered my profile and imported to a new UP. Had the issue since then, also get "is not allowed by this Transaction Relay Service." when trying to update any attributes on the profile. Also installed new version of UP extention in dev mode. I have my private keys backed up. But do have 40LYX and 9 chill whales on that profile so quite concerned

[honest wadi]

@grim marsh one thing I’ve noticed is that, I have 3 profiles. 1 of them works fine (all imported via recovery) the one that DOES work has 3 controllers, one being the recovery controller. The other 2 don’t work.

[zenith zodiac]

Hi, Icreated a up on my laptop through the chrome extension and created a backup in my google account. On my desktop i restored this account also in the browser extension, but when i want to sign in on the desktop i get an error no sign in permission. Also have only 2 controllers on the imported profile

[analog thorn]

@honest wadi @zenith zodiac @chilly drift this is all related to the recent controller incident that you can read more about on our support page: https://support.lukso.network/extension/incidents/controller-recovery. it appears that your controller in the extension is different than the one you added. as described in the incident report- this was fixed on version 3.0.0-beta.7. you can check out the version using this guide: https://support.lukso.network/extension/guides/check-extension-version

to resolve the issue, please follow this video https://support.lukso.network/extension/incidents/controller-recovery if you have either 2FA set (https://support.lukso.network/extension/guides/check-2fa-recovery) or still have access to the original extension where you created the profile on. ✅

If you do not have 2FA or access anymore, please bear with us and create a local backup by revealing the private keys on the settings screen of each extension. with this, you will be able to add controllers manually soon.

@zenith zodiac regarding the different controllers: yes, every import/recovery adds a new, individual controller to the profile, you can read more on the controller page of the support center: https://support.lukso.network/extension/controllers.

[honest wadi]

@analog thorn , thank you for your response. So i followed the video and attempted the above:

• I went through recovery in a new chrome profile.
• when going through the recovery and using 2fa, the profile im trying to recover in the UI gives the error "No recovery set up".
• the "waiting for profile import transaction" dialogue box shows for quite a long time.
• the tx doesn't show up on: https://explorer.execution.mainnet.lukso.network/address/0x775e260F15d52CDD7fAaE5be9181a7360BEDA3c9?tab=internal_txns
• The profile looks fine on the extension, apart from only 2 controllers.
• Still can't do any tx's or connect to any dapps, same issue.
• You'll see from the screenshot my extension has the controller for 0x89995FA1f07E89d204D810F9C7e1dBfF679007C2 which I DO have the private keys for.

Can you please check and see if this will be recoverable?

[wet abyss]

Here are the data i can read on chain:

Controllers:

0xA5467dfe7019bF2C7C5F7A707711B9d4cAD118c8 -> Receiver

0x89995FA1f07E89d204D810F9C7e1dBfF679007C2 -> "extension controller" (screenshot below)

Debug URL: https://erc725-inspect.lukso.tech/inspector?address=0x775e260F15d52CDD7fAaE5be9181a7360BEDA3c9&network=mainnet

So according to onchain data: 0x89995FA1f07E89d204D810F9C7e1dBfF679007C2 is a valid controller -> if you have the private key of that controller YOU ARE SAFE.

save the pk of 0x89995FA1f07E89d204D810F9C7e1dBfF679007C2 safely until the extension recovery is fixed

What is weird is that everything looks fine but somehow it doesnt sign properly

[honest wadi]

ok thank god

[zenith zodiac]

Thanks, will give it a go.

[honest wadi]

thanks for looking @wet abyss . so I guess i need to sit tight and wait until there is a feature to import the private key for the controller?

[analog thorn]

yep, indeed. we will keep you posted

[honest wadi]

@wet abyss upgraded to v3.0.0-beta.8, still the same issue - no changes

[analog thorn]

already responded on the other post #1194928755949436969 . extension updates cannot grant controllers roles. please hold tight until file backup / the tool for manually adding controller keys is ready using your original private key. 🙏🏻