New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
No. He said he stopped hosting mail for the domain, and then bitched that it wanted him to answer a security answer that was sent over SMTP.
/thread
I don't see any relevance to how the email got messed up or whose fault it was. Email gets messed up sometimes. rm_'s got messed up and then fixed, which is all anyone can really ask for. The question is whether rm_ and/or DO are acting unreasonably after the fix. As far I can tell, rm_'s view is that DO is busted since its web UI won't automatically send a new token to the now-fixed email. My view is that the UI has an imperfection because of this, but it falls short of DO being busted because there's a natural workaround which is submit a ticket. So unless I'm missing something rm_ is being unreasonable in not being willing to use the workaround.
I missed that part, but it doesn't seem bad to me. My email is with Fastmail and I use it as my billing address including for Fastmail, so I get stuff like Fastmail renewal notifications at my Fastmail inbox which is where I want them. If something happened to my access I'd have to contact their support, but unlike rm_ I don't object to doing that. (Added: I remember now I have a backup address on file with them, but that's not the billing address. Otherwise they have other points of contact like my phone number).
You could re-read everything I said and then quote the part which gave that impression, I can clarify it.
Perhaps the bit about DO's DNS caches? It was about my guess that their sending mailserver doesn't retry sending verification because it has remembered the bogus MX record which was on my domain (basically pointing to nowhere) far beyond the 10 minute TTL that it had, and didn't refresh its cache from the actual records on the domain, which had proper MXes reinstated long since then.
But as it turned out later that was not the reason, the problem is that it just doesn't retry at all, no matter what.
Not sure whether this was asked. Have you contacted them?
Those are reasonable concerns, but I don't think it's valid to present them as objections unless they actually happen. Why don't you open a ticket saying you didn't get the 6 digit code because your email address was temporarily not working, but it's now fixed and you'd like to request another one. If they ask you for stuff like passport scans at that point, then post a complaint here.
Well, at first that was it, and it was only a mild annoyance -- "Oh, I have to reconfigure my mail again" -- at that point I didn't imagine their system is so borked that it won't even help.
I see your point and I will do so if I will have a really urgent need to have that account back. For now I can live with the fact that they locked me out on a whim, know about brokenness of the system which did that, and proceed to do nothing to fix it. After all there are many other and better providers around, I think I'll somehow manage.
So after 4 pages.
@Jarland has offered to help, you seem unwilling to accept. He appeared to suggest he could override whatever it is stopping the code being sent again.
You don't know what the requirements are to get this sorted without @Jarland help as you seem unwilling to email DO because they may ask for things you don't want to provide, but you don't know that.
I am certain this could easily have been resolved by now, but you don't want that do you? This is not really about you wanting to have access again, is it?
You just wanted this thread. Nothing more.
It might have tried, retried, and given up, all within the 10 minute TTL.
Re-read the whole thing?!!
No problem though - It's OK because @WSS was kind enough to answer my question up above.
Repeating from previous page:
And if you re-read the first post, it is a reminder to people to recheck what E-Mail address they have at DO, and that if it stops working at some point, they can lose the ability to login to even change it -- a very uncommon practice across VPS/dedi providers in general.
So..., what's this thread about? Not contacting DO and just literally "bitching"?
"I stopped accepting email for this domain and they wanted me to prove my login, since I haven't used it in awhile!!!1!"11o1
@rm_ My apologies for the mistake. Still, you should accept @jarland’s help so you can get access back to your account.
This is a good point. Many companies deactivate accounts which are dorment for security. More important for stuff that could contain billing info.
Many sites include "email" in their definition of the 2nd factor.
While looking into this thread an reading the many reactions above. My judgement about 2FA at DigitalOcean the should use a 4 / 6 digit pin that the user can enable from their client settings. instead of forcing this policy to enable it on all accounts.
However you should contact them regarding your failing to login due to their policy on the 2FA side.
Also about the cache of their nameservers this can vary from an hour to a couple of days.
All depends on their configuration.
For the third time - if you contacted support, you'd (usually) have this resolved within a couple of hours.
Repeating "for the third time" something that's been already answered twice just feels like a rude thing to do in a conversation. Should I answer to you personally "for the third time", or how about you scroll up and read this or that instead.
It's not about me or my account, it's about DO, I prefer to leave the account as is for now, as a bonus I am able to re-check at any time if they have fixed the problem via implementing unconditional retries for verification, or if the system is still broken.
You're really hopeless.
^ let's all thank the above post now. Mr. Aidan is thanking my posts all the time, it's finally time to give back.
^ Someone has quite a bit of growing up to do.
^ Someone has yet to find a way into my wallet.
^ Someone already works on it
If You can't login to DO and using fake name then you can take a backup of VPS from SSH and move data or do not revoke paypal subscription else you will lose your VPS.
Sound advice.
Bozo 2.0.
Careful, that’ll be trademarked along with AutoBoot.
@Nekki Unfortunately, AutoBoot has been discontinued as of... err, sometime in 2015.
Heart-breaking news. True innovation that never received the attention it deserved.
Sad, but I had to Google "autoboot" to see if you guys were serious.
I've never encountered a system that didn't boot by itself when turned on, so I thought you were joking. But it seems that there are actually people out there who use the word to refer to starting a program automatically at boot time. (eg autoexec.bat) It seems we have a newfangled definition of "boot".