G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
41–50 of 138 posts
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#42I had this same issue with CloudFlare. Lost access to my email account. Had my CloudFlare username + password, but CloudFlare insisted that I verify with my email since I was trying to log in from a new IP (it wasn't a new IP, but maybe they time out after a few months?). No way to make progress. Can't use support if you don't have an account. Tried making a separate account, so I could at least open tickets. Their t…
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#43Similar issue if you cancel your GSuite account. I cancelled my account and was still billed for it, but now there's no way to contact support since I don't have an active billing account.
I was debating whether to purchase extra storage for Google Apps email as I am getting close to the 15GB free limit. I decided that I would pay Fastmail instead. I would not want to make my life/business dependent on Google’s whims.
Then you're in luck, because Fastmail's $5/month option has twice as much storage as you're using: $30GB.
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#44I had this same issue with CloudFlare. Lost access to my email account. Had my CloudFlare username + password, but CloudFlare insisted that I verify with my email since I was trying to log in from a new IP (it wasn't a new IP, but maybe they time out after a few months?). No way to make progress. Can't use support if you don't have an account. Tried making a separate account, so I could at least open tickets. Their t…
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#45Earlier quoted context omitted.
He said he set up 2FA and then lost the "corporate device" providing it. This is why you always set up backup codes. The 2FA is doing its job here keeping the account safe from someone who doesn't have the token, which unfortunately is the account holder.
Wow, didn't expect this post to blow up like this. For reference, I have no 2FA, nor did I lose my corporate device. I've always accessed it through a web browser, never through a mobile, therefore when it asks me to verify with my corporate mobile device, I do not know what device it is referring to.
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#46Earlier quoted context omitted.
FWIW this is why it's a good idea to have two MFA mechanisms. If you can afford it I recommend getting 2 hardware tokens, and storing them separately (you can leave one in your computer, hard to lose).
That's a great plan, but AWS notably doesn't support multiple hardware u2f devices. They've been sitting on the ask for about 7 years https://forums.aws.amazon.com/thread.jspa?threadID=137055
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#47Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#48Earlier quoted context omitted.
Where in the world are you to have banks which promote fraud? In my country (France) you can call your bank, declare that a fraud is going on and it then becomes their problem. They will usually issue you a new card and call it a day.
Not necessarily true for this case. I had a problem with a [very well known US-based bank] credit card where a re-curring monthly charge that I wanted stopped.. wouldn't be stopped by the bank because I had authorized the recurring charge at the outset. Bank told me to contact the entity charging me, and when I said I couldn't reach them (which was true) and they didn't respond via their support channels, bank said I…
Re: G Suite Doesn't Let You Contact Support Until Logged In. Locked Out = Stuck
#49if you provide identity services to more than 100k people or w/e, you need to have a defined dispute process, served by humans with the power to do shit, with legal recourse in the event that they fail to do so. the "run a flag up the pole on social media, hope you're important enough or friends with the right set of people if you want shit done" approach is terrible.
the inevitable "but that will be vulnerable to fraudsters" backlash is stupid--the existing systems are too; fraud prevention and such isn't something you can ever do perfectly, since it's inherently adversarial. the problem we have now is that EVERYONE is treated as if they're a mastermind professional fraud network from the outset, and this does seemingly little to prevent actual bad actors. Twitter's trust and safety team is an even more egregious example, where they very effectively and immediately suspended my attempt to create a single parody account, immediately suspended it again after unsuspending it, and said any future attempts to reach them would be blackholed because the first unsuspend request was still open (there's, of course, no way to see that ticket or respond to it--all you get are email notifications stating that the reply-to discards all inbound mail). this, of course, does seemingly nothing to deal with actual bot networks, since those are run by sophisticated actors who've figured out how to game the system.
something like Estonia's digital ID system is perhaps best, with, importantly, built-in protection against tracking: I should be able to generate an ID that a company can verify, but all they should be able to glean from that is that I have an ID and that I've authorized X other IDs for that company--it shouldn't be something that's traceable back to who I actually am or trace my actions across companies, which is very much not the case (and is something companies very obviously take advantage of for adtech purposes) for the de facto standard of using mobile phone numbers.