Open your Electrum wallet. Click on Tools -> Preferences and then check the box named "Write logs to file". Close Electrum and then reopen it and open your wallet again.
Try to make a transaction so you get shown the error message as before. Close Electrum, then navigate to the newly created logs folder inside the Electrum directory (~/.electrum/logs) and share the contents of the log file with us here.
Topic: help：RuntimeError('DataError: Forbidden key path') (Read 174 times)
Why can't I upload pictures to this forum?
This forum doesn't have that option so instead you have to upload your images to one of the image hosting platforms such as https://imgur.com/ and then post the Share link here.thank you
Why can't I upload pictures to this forum?
This forum doesn't have that option so instead you have to upload your images to one of the image hosting platforms such as https://imgur.com/ and then post the Share link here. I just continued to log in here today, thank you for your replies, but the problem is still not resolved. After setting the path with the trezor hardware wallet yesterday, I still can't sign.
"Setting the path", what do you mean?Anyways, have you upgraded your Trezor's firmware to the latest version? No?
Here's their official guide on it: https://trezor.io/learn/a/update-trezor-device-firmware
derivation path. Wallets have this functionality. Why can't I upload pictures to this forum? Upgraded to latest version still the same.
I just continued to log in here today, thank you for your replies, but the problem is still not resolved. After setting the path with the trezor hardware wallet yesterday, I still can't sign.
"Setting the path", what do you mean?Anyways, have you upgraded your Trezor's firmware to the latest version? No?
Here's their official guide on it: https://trezor.io/learn/a/update-trezor-device-firmware
I just continued to log in here today, thank you for your replies, but the problem is still not resolved. After setting the path with the trezor hardware wallet yesterday, I still can't sign. Unable to transfer btc out. Please help me, thank you。
Based on his screenshot, he's using Trezor hardware wallet since that hardware wallet icon (lower-right) is exclusive to Trezor.
It's most likely similar to the old issue (link in my second reply) which should be fixed by upgrading the firmware.
Yeah, it's probably solved already after following the first reply and OP didn't bothered replying.
It's most likely similar to the old issue (link in my second reply) which should be fixed by upgrading the firmware.
Yeah, it's probably solved already after following the first reply and OP didn't bothered replying.
OP is probably running an old version that was upgraded from an even older? Can't guess of anything else.
OP doesn't seem to be interested in this issue anymore (maybe solved already?) but in order to have any further information we need OP to post the results of the debug log as it was suggested by SomberNight in issue #7873 3 days ago. 
I managed to find something not related to Electrum directly but a fork for it for an altcoin.
The alt's Electrum wasn't made from scratch, it says it was forked from Electrum. Therefore there's a high chance this error comes from a prior version of Electrum, that was later removed. Electrum developers get used to doing these changes. Your transaction is most probably not signed because this error happens when Electrum can not derive the correct key using the information provided in your wallet. It requires your change value in your derivation path be either 0 or 1.
OP is probably running an old version that was upgraded from an even older? Can't guess of anything else.I'd back up my seed phrase (if I hadn't already) and move onto 4.1.5+.
I tried to google the error to see what would come up. I managed to find something not related to Electrum directly but a fork for it for an altcoin.
https://githubhot.com/repo/qtumproject/qtum-electrum/issues/115
The user experienced the same type of error and the fix was a simple settings change in something the software calls "Safety Check Level". Electrum obviously doesn't have anything like that, but it's interesting nonetheless that this error pops up after the alleged signing takes place and the the user is trying to broadcast the transaction.
https://githubhot.com/repo/qtumproject/qtum-electrum/issues/115
The user experienced the same type of error and the fix was a simple settings change in something the software calls "Safety Check Level". Electrum obviously doesn't have anything like that, but it's interesting nonetheless that this error pops up after the alleged signing takes place and the the user is trying to broadcast the transaction.
I suspect nc50lc is on the right track, i.e. you're using a hardware wallet and Electrum can't get the right signature from the hardware wallet. This is likely due to having the wrong Bip39 passphrase entered into the hardware wallet, which provides Electrum a completely different set of signing keys.
We should just take this as a new suggestion :)since what I suspected in case he's using a hardware wallet is: he might be using an outdated firmware that has a similar bug like this: link
So I can't take the credit.
There is someone who reported the same issue on the Electrum GitHub page are you the one who reported it there? I think you are?
It seems that you are using macOS and installed Electrum 4.1.5 would you mind trying to install the latest one which is 4.2.2 and test and maybe it is just a bug.
If it didn't solve the issue like on the reply on the Github page try to enable the debug logging. You can find this feature under tools>preferences>general and then check the write logs to file and reopen the Electrum and make a test transaction again if the error show you can now close the Electrum and check the logs.
Let's see if you can find the reason and issue under that logs you can share it here to help us identify the issue.
It seems that you are using macOS and installed Electrum 4.1.5 would you mind trying to install the latest one which is 4.2.2 and test and maybe it is just a bug.
If it didn't solve the issue like on the reply on the Github page try to enable the debug logging. You can find this feature under tools>preferences>general and then check the write logs to file and reopen the Electrum and make a test transaction again if the error show you can now close the Electrum and check the logs.
Let's see if you can find the reason and issue under that logs you can share it here to help us identify the issue.
I suspect nc50lc is on the right track, i.e. you're using a hardware wallet and Electrum can't get the right signature from the hardware wallet. This is likely due to having the wrong Bip39 passphrase entered into the hardware wallet, which provides Electrum a completely different set of signing keys.
If you're not using a hardware wallet, your wallet file may have been corrupted in which case you'll need to restore it from your seed phrase or a previous back up.
If you're not using a hardware wallet, your wallet file may have been corrupted in which case you'll need to restore it from your seed phrase or a previous back up.
Your transaction is most probably not signed because this error happens when Electrum can not derive the correct key using the information provided in your wallet. It requires your change value in your derivation path be either 0 or 1. Lack of signature is the reason why you can't click the Broadcast button.
The line that throws this exception: https://github.com/spesmilo/electrum/blob/574243b897f345208a3b9197c6b0b1e229d61271/electrum/keystore.py#L537-L538
The line that throws this exception: https://github.com/spesmilo/electrum/blob/574243b897f345208a3b9197c6b0b1e229d61271/electrum/keystore.py#L537-L538
Click "after signing", that's it. You can't click "broadcast._
So you can sign the transaction but not broadcast it?
If so, you should be able to broadcast it using a 3rd party broadcasting tool such as Blockcypher's.
If you can't transfer out, how can you handle it? thank you。
If it's not a hardware wallet, try to restore the wallet using the seed phrase.Are you using a hardware wallet?
If so, you might have to upgrade it to the latest firmware to work.
BTC cannot be transferred out. This will appear：
RuntimeError('DataError: Forbidden key path')
。。。。。
This is the prompt when you want to transfer out BTC.
If you can't transfer out, how can you handle it? thank you。
Click "after signing", that's it. You can't click "broadcast。
RuntimeError('DataError: Forbidden key path')
。。。。。
This is the prompt when you want to transfer out BTC.
If you can't transfer out, how can you handle it? thank you。
Click "after signing", that's it. You can't click "broadcast。
Jump to: