Account Creation Error: INVALID_INVITE_TOKEN
Archetype Zero
Member
Hey Support Team,
I am currently unable to use the key that was emailed to me to create my Artillery account, or log in with that account. I have included screenshots, steps to recreate the issue and email headers to verify the legitimacy of the email. I Will continue to monitor this thread in case additional information is requested.
Steps to recreate this issue:
1) Download and install the Atlas Client
2) Launch the Atlas Client
3) On the login page click 'Create One'
4) On the Create an Artillery Account page, enter account details, Copy and Paste the invite Key from the artillery email into the Invite key, then click Create Account
5) Receive INVALID_INVITE_TOKEN Error, click "try again"
6) Enter account details, Copy and Paste the invite Key from the artillery email into the Invite key, then click Create Account
5) Click Try again
6) Click Log In
7) Enter usename and password from previous page
8) Receive wrong login/password error
9) Open Browser and Navigate to https://atlas.artillery.com/login/home
10) Enter usename and password >> Receive wrong login/password error
11) Click 'Create One'
12) On the Create an Artillery Account page, enter account details, Copy and Paste the invite Key from the artillery email into the Invite key, then click Create Account
13) Receive INVALID_INVITE_TOKEN Error, click "try again"
14) Enter account details, Copy and Paste the invite Key from the artillery email into the Invite key, then click Create Account
Email Headers should verify legitimacy of message:
Delivered-To: [email protected]
Received: by 10.55.21.213 with SMTP id 82csp374620qkv;
Fri, 11 Dec 2015 15:48:24 -0800 (PST)
X-Received: by 10.98.67.156 with SMTP id l28mr5106733pfi.29.1449877704118;
Fri, 11 Dec 2015 15:48:24 -0800 (PST)
Return-Path: 0000015193720a12-23d7ef36-8446-4c8c-a450-c17833f00a16-000000@us-west-2.amazonses.com
Received: from a27-50.smtp-out.us-west-2.amazonses.com (a27-50.smtp-out.us-west-2.amazonses.com. [54.240.27.50])
by mx.google.com with ESMTPS id qg7si4130592pac.163.2015.12.11.15.48.23
for Deathprophetik@gmail.com
(version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Fri, 11 Dec 2015 15:48:24 -0800 (PST)
Received-SPF: pass (google.com: domain of 0000015193720a12-23d7ef36-8446-4c8c-a450-c17833f00a16-000000@us-west-2.amazonses.com designates 54.240.27.50 as permitted sender) client-ip=54.240.27.50;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of 0000015193720a12-23d7ef36-8446-4c8c-a450-c17833f00a16-000000@us-west-2.amazonses.com designates 54.240.27.50 as permitted sender) smtp.mailfrom=0000015193720a12-23d7ef36-8446-4c8c-a450-c17833f00a16-000000@us-west-2.amazonses.com;
dkim=pass [email protected]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=7v7vs6w47njt4pimodk5mmttbegzsi6n; d=amazonses.com; t=1449877703;
h=From:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Date:Message-ID:Feedback-ID;
bh=GuaDmRPLnKMvIKFSDAdh7OxB7b5PwAaso2+0o5JFL/U=;
b=ky/ml0hQfVc8SZa2xTl7MUP3oe0tK/VeX928a2bZKQyf4Xt7W5rKv+6BQftYhl5P
62WxdlAX0D+Xs+p6VBCd60rBjsRvuMuuXUXsXXPw2GfbVq8mFBtbwRLjyoYlVNuyDKo
g1ucv5223O+vlyVxZI/Tq4QY7DLBR6Kg4n+NZyMw=
From: Artillery support@artillery.com
To: [email protected]
Subject: You're invited to play Atlas. Here's your key!
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Dec 2015 23:48:23 +0000
Message-ID: 0000015193720a12-23d7ef36-8446-4c8c-a450-c17833f00a16-000000@us-west-2.amazonses.com
X-SES-Outgoing: 2015.12.11-54.240.27.50
Feedback-ID: 1.us-west-2.KBnraGDmY0hnvPMzpW8q/2fOfBVjGf2QHo00yE3w92Q=:AmazonSES
Comments
Invite keys can only be used once, and that was the key you used to create your account. Since you've successfully run the client and you're logged into the forums, I'm unclear as to what you're trying to do.
Ping me on chat or at [email protected] and we'll get you sorted out!
This issue has been resolved! The email field is CASE SENSITIVE! meaning that if you registered with [email protected], you must log in with [email protected] and not [email protected] or [email protected] etc.
Thanks Statico!