System Messages and Troubleshooting

System messages and troubleshooting offer guidelines to trace and correct problems. Topics are listed alphabetically and explained here.

Access

Why do I Get Access Denied Logging in as Root User?

When logging in as the Root user, you may see an "Access Denied" message while attempting to view Buckets:

This might occur when S3 endpoints cannot be reached. The following tests can help isolate what may be blocking access:

• In a different web browser or a private/incognito browsing session, try logging in to the Wasabi Console again. If this works, it is likely a browser extension/blocker did not permit access to the S3 endpoints.
• If the error persists, try logging in to the Wasabi Console on a different device on a different network. Ideally, try a mobile device over a cellular network (not WiFi). If this works, either local antivirus (AV) software OR a local network firewall is blocking access to S3 endpoints.

If it is determined that a firewall is blocking access, you can whitelist your desired/needed S3 endpoints.

If neither test works, contact support@wasabi.com

Account Email

I did not receive an email I was expecting from Wasabi.

If you do not receive the Wasabi system-generated email you are expecting, check your spam filters and/or 'junk' mail folder. To whitelist Wasabi-associated emails, this article provides information on How to safelist emails.

Wasabi uses leading a third-party email service provider (Mandrill Mailchimp) to deliver Wasabi system-generated emails. These emails are generated by the Wasabi service for trial invitations, password resets, payment-related issues, and so on. In a rare case, you may not receive one of these system-generated messages. This is generally because a spam filter caught the message, particularly if the spam filter previously caught emails from other companies. This Mailchimp Developer article offers more detail about our third-party provider spam filters.

For a deeper look, the following is an example of how the wasabi.com and mandrillapp.com email domains show up in the expanded email headers of a trial invitation message sent from Wasabi to an email address of user@email.com

Delivered-To: user@email.com
Received: by 2002:a4a:49c:0:0:0:0:0 with SMTP id 28-v6csp3039466oos;
        Mon, 3 Sep 2018 16:11:29 -0700 (PDT)
X-Received: by 2002:a25:2410:: with SMTP id k16-v6mr16626804ybk.325.1536016049721;
        Mon, 03 Sep 2018 16:07:29 -0700 (PDT)
X-Google-Smtp-Source: ANB0VdYCtfW8IjegWLZxygbUXjfkfvd0d6vYUDRqu5fexpp4qaAvxVl5+edYPdopS+WBh+jcG336
X-Received: by 2002:a25:2410:: with SMTP id k16-v6mr16626776ybk.325.1536016048831;
        Mon, 03 Sep 2018 16:07:28 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1536016048; cv=none;
        d=google.com; s=arc-20160816;
        b=k2PVVpyRvV/KcU+NHpAzJE+z9fiuMwXE3w4iAnJ8dzBkQPp5jQqHUQnI/gVLEHE9mQ
         G4MOLsL8WWGa0tzFG9iMAxI+gC5Cod3iOREGyJYixsnn4SG1IFWYYusAxzA7P0t5jk25
         3LTHwALjcbCrkF8yNzLEqTmL9x5YtMfBPRNK9MMQ60Jtjmiq7LpmsBKjrjMzCC30csWs
         90k6JfhyQblGnZ1DI+yGk76syWcm213nuO2RRAkyE1WJcHUaBvVsRzoO2ZfL2IwVveqU
         DNucgaLkgeNjU9swQvwGdSX6pcCiC+HBF/ytmhC9L1848jNqowpv3sIl1PT6+WB6Fewf
         G7qw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=mime-version:date:message-id:to:subject:from:dkim-signature
         :dkim-signature:arc-authentication-results;
        bh=82z2Mc1QNBdGfh188VscSl064/gyaNAjcuAbuYmXS7g=;
        b=XBr6kdaXDwbPFXMymTU7dmKI9LVfW09ETHbYBdPpfmlocqMdFO/D+tW64uRHvF+nBl
         S1zHmdHhy/OOhO8JaI9aFn6YOZ9OubHDUtlYJFZ56UnqbrxV4Xsu4If84J+UGe2hsT9N
         qfNhCSUWFPswblQdcTvCpT2lOaOlwFyPyUm8isWxOCWgUXVOaWg2wA1lOfx+e9EF62cn
         G1R9Sn6OlUd/Q7IIyiLtpSa4/pPblIMD5QnlnmxO5ymiu73/3gRHW+boxr7Tcy2BEivT
         FdA7zX1xJbdCbH4QWtVaR5visAr9OVgpSoog8r+q7L2HPwwzp0gHYl0Xvu/Dy8en3mG8
         /ytw==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@wasabi.com header.s=mandrill header.b=LnMTXeuF;
       dkim=pass header.i=@mandrillapp.com header.s=mandrill header.b=MS7Tcc68;
       spf=pass (google.com: domain of bounce-md_30990426.5b8dbeb0.v1-0d9c9d25ad3341219526be42e2f05695@mandrillapp.com designates 198.2.186.27 as permitted sender) smtp.mailfrom=bounce-md_30990426.5b8dbeb0.v1-0d9c9d25ad3341219526be42e2f05695@mandrillapp.com
Return-Path: <>mandrillapp.com>
Received: from mail186-27.suw21.mandrillapp.com (mail186-27.suw21.mandrillapp.com. [198.2.186.27])
        by mx.google.com with ESMTPS id o125-v6si4929475ywe.615.2018.09.03.16.07.28
        for 
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 03 Sep 2018 16:07:28 -0700 (PDT)
Received-SPF: pass (google.com: domain of bounce-md_30990426.5b8dbeb0.v1-0d9c9d25ad3341219526be42e2f05695@mandrillapp.com designates 198.2.186.27 as permitted sender) client-ip=198.2.186.27;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@wasabi.com header.s=mandrill header.b=LnMTXeuF;
       dkim=pass header.i=@mandrillapp.com header.s=mandrill header.b=MS7Tcc68;
       spf=pass (google.com: domain of bounce-md_30990426.5b8dbeb0.v1-0d9c9d25ad3341219526be42e2f05695@mandrillapp.com designates 198.2.186.27 as permitted sender) smtp.mailfrom=bounce-md_30990426.5b8dbeb0.v1-0d9c9d25ad3341219526be42e2f05695@mandrillapp.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=mandrill; d=wasabi.com; h=From:Subject:To:Message-Id:Date:MIME-Version:Content-Type; i=support@wasabi.com; bh=82z2Mc1QNBdGfh188VscSl064/gyaNAjcuAbuYmXS7g=; b=LnMTXeuFa4+8YnKPOFVxUx/Xpw919neeUB3VdXjLAO3j8bkT+GKIvYoLWDYA6mwuuRSmENf1OjMG
   yT/GDbX98XN5XrYw/L1O3/khXttBaXU2AnZfH+TyfIG9rjFk31DG6/s8hXRqLatgVvK3RaItGFdE
   RkD3uCdmF/FF8Drrg0Y=
Received: from pmta02.mandrill.prod.suw01.rsglab.com (127.0.0.1) by mail186-27.suw21.mandrillapp.com id hhmvb0174bkv for <user@email.com>; Mon, 3 Sep 2018 23:07:28 +0000 (envelope-from <>mandrillapp.com>)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mandrillapp.com;
  i=@mandrillapp.com; q=dns/txt; s=mandrill; t=1536016048; h=From :
  Subject : To : Message-Id : Date : MIME-Version : Content-Type : From :
  Subject : Date : X-Mandrill-User : List-Unsubscribe;
  bh=82z2Mc1QNBdGfh188VscSl064/gyaNAjcuAbuYmXS7g=;
  b=MS7Tcc68LsT9NkBSPeIAyiyqbS+V+145ThlfWFcZGhX7MQqgcyLZa3tcrEuwubh6pE3T6b sCaG3otVfTFcC92NZjYmejOqo+tX0voBUVz/ESMtiiQJn6QV46qWos0W9NpICrhRqOj0aoO+ +7sYqHoVUrbhRU5BiVd5JPlfDAicM=
From: Wasabi Support 
Subject: You are invited to try Wasabi
Return-Path: <>mandrillapp.com>
Received: from [38.27.106.15] by mandrillapp.com id 0d9c9d25ad3341219526be42e2f05695; Mon, 03 Sep 2018 23:07:28 +0000
To: "user@email.com" 
X-Report-Abuse: Please forward a copy of this message, including all headers, to abuse@mandrill.com
X-Report-Abuse: You can also report abuse here: http://mandrillapp.com/contact/abuse?id=30990426.0d9c9d25ad3341219526be42e2f05695
X-Mandrill-User: md_30990426
Message-Id: <30990426.20180903230728.5b8dbeb03a86d7.57750918@mail186-27.suw21.mandrillapp.com>
Date: Mon, 03 Sep 2018 23:07:28 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="_av-XXsX_i1lVGG6_sT1XkKpRQ"

Resetting my account email doesn't seem to be working. What should I do?

If you run into problems changing the email address associated with your Wasabi account in the Wasabi Management Console, check the following:

1. If logged in using an alias, log out and log in again using your root account email address.
If you attempt to change an email address when logged in with an alias, email address updating issues may occur.

2. Log in with your current email address.
The email change system requires that you log in with your current email address in order to initiate a change. Once you log in with your email you will see a dialog showing the Console updating your email.

3. log out of your account once your email address is changed.
The console will not reflect your email change until you log out and log back in. When logging in again, use your new email address.

Credit Card

Fixing a problem while submitting a credit card to become a paid subscriber.

Wasabi uses Stripe as our payment processor, and Stripe sends the credit card information to the credit card issuing bank.

• If the bank rejects the charge attempt, you will get an error message such as, "Problem with card, please contact support" or "Card declined". These messages are sent from Stripe, and Wasabi does not have additional information on the reason the card was not accepted. We recommend you contact your credit card issuing bank for details. 
• Stripe uses the billing address to confirm your identity. An error can occur if there is a misspelling in the billing address. Make sure your address and zip code are entered correctly.
• An error may occur if the credit card is issued from a country that Stripe does not yet support. Refer to the list of countries Stripe supports.

Network

What should I do if I'm not seeing the network performance I expect?

Wasabi Technical Support periodically gets network performance questions from our customers.  These questions occur when a customer is not able to realize the upload or download speed performance they expect when exchanging files with Wasabi.  With any cloud storage service, the speed of file exchange is based on a number of factors including:

• The size and number of files you are trying to transfer to the cloud
• The speed of your network connection (and the presence of other traffic on this connection) 
• The performance capabilities of the application you are using to transfer files to the cloud
• The performance capabilities of the cloud storage service 

Wasabi only has control over the last factor.  To do our part in maximizing customer data throughput, we have multiple (and redundant) high-speed connections from our storage service data centers to the Internet and the private network services we support.   These connections are traffic engineered  to always have sufficient capacity to accommodate the bandwidth needs for the expected worst case loads & throughput from our customers.    

When investigating file transfer time issues, it is sometimes helpful to understand the theoretical maximum time it will take.  There are many free file transfer time calculators (here is an example) that will help you determine the theoretical transfer time it will take to exchange X amount for data over a network connection transfer rate of Y speed.   

Keep in mind that these file transfer times are only theoretical in nature and subject to the factors discussed earlier regarding performance capabilities of the network connection, storage application, and storage service.  This means that under real-world conditions, it is generally not possible obtain the theoretical transfer time these tools indicate. However, it's a starting point to consider when looking into file transfer time issue.  

In the event you are not seeing the network performance you are expecting, one of the simplest troubleshooting steps is to run a speedtest from your location to the Wasabi storage region data center that you are using.  There are two ways to do this:

1. Utilize the speedtest utility that is embedded in the Wasabi Management Console.
2. Utilize the speedtest utility that is available as a separate webpage 

Both approaches work the same way in terms of testing the speed from your location to a custom Ookla speedtest server hosted in our data center.   Instructions on how to use each approach are provided below.

Using Speedtest via Wasabi Management Console

1. Log in to the Wasabi Management Console and go to Settings -> Speed Test.
2. When prompted, cut / paste in the password into the Enter Test Password field.
3. Below the GO image, select the Wasabi storage region you wish to use, then select GOto start the speed test. Sample results are shown below.  If you are contacting Wasabi Support for help with a performance, include these results with your support ticket.

   

   

   

Using Speedtest via Separate Webpage

If for some reason (for example, you do not yet have a Wasabi account) you are not able to access the speedtest utility from the Wasabi Management Console, you can also access this utility from http://wasabi.speedtestcustom.com/. (Contact Wasabi Support for the password.)

Once you have entered in the test password when prompted, you can follow the same usage instructions that are provided above for the speedtest utility 

Access the speedtest server that is appropriate for the Wasabi region you are trying to use (see pick list below). 

Contacting Wasabi Support Regarding Performance Issues

If you contact Wasabi Support regarding a performance issue, in order to isolate the root cause of the problem, we request that you provide the following info:

1. Details on your geo-location, internet speed, and internet provider.
2. Details on the storage client you are using to exchange the files with Wasabi.
3. Details on the file size(s) being transferred.
4. Details on whether or not the problem occurs all the time or just some of the time. For example, did you previously experience a better/expected level of performance?
5. Results of the speedtest (as described earlier in this article).
   
6. Results from a traceroute to:

   — s3.wasabisys.com for us-east-1
   — s3.us-east-2.wasabisys.com for us-east-2
   — s3.us-central-1.wasabisys.com for us-central-1
   — s3.us-west-1.wasabisys.com for us-west
   — s3.eu-central-1.wasabisys.com for eu-central
   — s3.ap-northeast-1 for  ap-northeast-1

   For the traceroute test, it is preferred that you provide the 'mtr' output that you get from sudo mtr -T -P 443 -rw s3.wasabisys.com

Depending on the data from the first set of questions & network tests described above, Wasabi Support may also ask you for the following additional info:

• If possible, put a 10 MB test file in one of your buckets and make it "public" (as described in Public Access). Once done, provide this output:
  for count in {1..5}; do dig +noall +answer s3.wasabisys.com | tail -1; echo -n `date`" -- ";curl -w 'bytesPerSecondDownload %{speed_download}\n' -so /dev/null http://s3.wasabisys.com/<your-bucket>/<your-file-keyname>; done

  The above example uses a us-east-1 service URL; use the appropriate service URL for the region you are trying to test.

• If you are able to perform a packet capture of the upload or download action and share the file with Wasabi Support.

How do I resolve a network error when accessing the Wasabi Management Console?

The Wasabi Management Console relies on IP connectivity to console.wasabisys.com as well as several other wasabisys.com sub-domains. These sub-domains include:

• console.wasabisys.com
• iam.wasabisys.com
• billing.wasabisys.com
• Wasabi service URL(s) you are using

If you are seeing "Network Error" messages when trying to use the Wasabi Management Console, one possible cause is that there is a firewall or web security gateway blocking the connectivity to these sub-domains from your location. You can verify connectivity to these sub-domains by running a simple ping test.

If you successfully verified connectivity to all of the sub-domains and still receive a "Network Error" message, contact a Wasabi Customer Support representative: support@wasabi.com.

How do I resolve a Network Failure problem due to firewall issues at Comcast/Xfinity?

Problem: I am a Comcast customer. When accessing the Wasabi Management Console, I am able to log in. But when attempting to access the buckets, the screen returns a “Network Failure” error and am unable to access any of my files.

Solution: This is specific to Comcast customers who are facing a “Network failure” and are unable to resolve the issue with the information above.

Check your xFi Advanced Security Firewall to see if these sites are blocked or blacklisted:

• console.wasabisys.com
• iam.wasabisys.com
• billing.wasabisys.com
• Wasabi service URL(s) you are using

You may want to disable this Firewall and then try accessing the web site again.

Time

The difference between the request time and the current time is too large.

Type: A valid error message in S3-style storage (AWS S3 or Wasabi).
Meaning: The machine you are using to access the Wasabi Management Console (or the Wasabi service via S3 API) is not in time sync with the Wasabi service.
Action: Ensure your machine is synced to a valid time source. For more information on the root cause, refer to:
https://stackoverflow.com/questions/4770635/s3-error-the-difference-between-the-request-time-and-the-current-time-is-too-la