there is a big bug in Linode creation, first of all there are no linodes active but createproxy toolbox thinks they are still active, and when I try to manually delete from the proxy list they won't as they are glitched, due to this happening I wanted to delete the account but I don't see the option to do that, so I created another token inside the same account, worked, but when I tried to gen some new ones got a "unexpected error"
Really look after linode as it's one of the best, please get in touch with me to fix, thanks!
Awesome! This question has already 9 answers..
Have you tried removal of all instances in Account List? This feature may bypass this error, then you may be able to remove also non working Linode Account.
Let me know If this worked for you.
Hey, so remember I said I created a second account, well in the account list I managed to remove account and proxies but again this first list is totally bugged, it doesnt even let me delete it, it still bugs and does nothing, and of course in the linode site I have no active linodes, very weird, please look at it or try delete it yourself
sir I know what I am saying, created another API key, added it to accounts, created 15 proxies and it said accoutn limit reached, then I went to proxy list and nothing appears, but when I go to linode I see the 15 I tried to create, the machine is totally bugged, please fix but fix definetely
Hello, I said that its fixed, dont know what news you want.. In account list you should be able to remove instances even when API key is no longer works, then you should be able in account list remove account with non working API key - all this has been tested so this way you are able to remove instances with non working api key. Instances in Linode you have to remove manually, there is nothing I can do with this.
What is not removable? I have been in your account, than I have clicked on remove account in Account List (for Linode Account) and this linode account has been normally removed. Also you have no any proxies active (so there is no any error related to proxy removal). Then, what are you reporting here?