Master API key disappeared after disabling 2FA on Bittrex- what to do?

[Checkist]

Hello,

Some time ago I disabled 2FA on Bittrex, and surprisingly found that all my API keys on exchange disappeared, including the master key. Then I generated new key, but when I put it to Gunbot, it can't connect to Bittrex anymore. I tried both v7 that I still use and new v12.

The errors are:
 v7 + original master key + new trade key:

Loading config...
Loading exchange - bittrex [Stays forever at this line]

(node:10408) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: [object Object]
(node:10408) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

v12 + original master key + new trade key:

Loading config...
   info  - socket.io started
GUI Server Deployed: http://localhost:5000
Available Token Balance on this ETH wallet: 0
Total Required Balance: 0
Total Available Balance: 0
Loading exchange - bittrex
Loading data....
Error: {}
    at errorHandler (C:\snapshot\Gunbotv12.8.3\ctx-wrapper.js:0:0)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
Unable to connect to bittrex
Please if this error persists, stop Gunbot, wait a few minutes and then start it
 again...

If I try to use my new trade key as master key - I have a message about invalid license.

So I guess Gunbot somehow checks if master key still exists on exchange and can't find it?

What are my options? Probably I need to ask someone to change my master key.

[sbogovac]

Contact your reseller to adjust your API key.

[Aitor]

Try changing your api yourself with Gunbot v12. It allows to change your api as far as the new api belongs to the same account.
On the other hand, you should take care of your api, it's your license. Here are some tips on how to keep your apis safe:

https://gunbot.shop/taking-care-of-your-gunbot-api-key-and-secret/

[olliecrypto]

the newest stable releases should allow you to change and manage your api key yourself, so hopefully this fixes your problem.