Hacker News Reader

Comment by kross | Hacker News Reader

http://shop.oculus.com - blank screen...awesome. It has been since the moment the pre-order link showed on oculus.com.

It isn't blank anymore, but it was nearly impossible to place an order.

I kept getting vague "Something went wrong. Please try again." messages on both the Payment Method and (when I finally got there) the Review and Complete Order pages. Meanwhile, my expected ship date went from March to April. It wouldn't accept my AMEX at all, for some reason.

I stand corrected. I just got a $1 authorization charge placed against my AMEX even though it never once even got to the point of storing my AMEX information as my "Credit Card" in their system.

I guess I should be happy it was only a single authorization charge?

Rule #1 of hugely anticipated release testing: Make sure you over-provision servers.

Rule #1: Make sure you UNDER-provision servers so your PR guys have something to tell the media.

33 minutes start to finish, it finally went through.

Palmer's thread on twitter "insanely high load": https://twitter.com/PalmerLuckey/status/684772857625231360

Same here. I got in, though, after about five minutes of re-trying. $599 base, $32 shipping, plus tax, totaled $680.

I saw the same thing, but it appears to be fixed now. A quick fix/reaction by Oculus!

Very quick on the bundle fix! Unfortunately, "Something went wrong. Please try again." with both credit cards and paypal.

So it isn't just one problem...

I get the same error

It finally went through although no confirmation email or any trace of the payment on my paypal account (or confirmation email from paypal which is usually immediate). So not sure if it actually went through...

app-bundle-3.15.14.js:50 Uncaught TypeError: Cannot read property 'hostname' of undefined

Some great QA went into this release.

Shit happens.

Site's up, now declining credit cards? I guess I'll have to paypal it...smooth!

This happened to me, the issue was that I entered my expiration date as MM/YY rather than MM/YYYY. Give it a shot if that's happening to you.

The site seems to autocorrect it to MM/YYYY if you enter MM/YY. At least, when it works. Even when I entered the information in manually I got the same vague errors.

I wonder what the purpose of collecting at as MM/YYYY even is given that everyone will have an expiration date of 20YY for a long time; and that when they don't, the ones collected now will be expired so not an issue. Even if they store it locally as 20YY to avoid some bug in 2100 (which would be rather long term thinking at this point), it still makes no sense to collect it that way and to autocorrect. Why not just append the digits on the back end?

Paypal and credit cards are both declined with "Something went wrong", console shows "Failed to load resource: the server responded with a status of 500 (Internal Server Error)"

Watching my ship date go from March to April and now probably May was a bit disheartening.

Still no success.

Reply on news.ycombinator.com