NOTE REVISED DATE:



We are planning a major system maintenance event for late this Wednesday night / early Thursday morning (22Sep2016, formerly 21Sep) starting at midnight MST/PDT (GMT -7). Our system will be unresponsive until this operation concludes, most likely within half an hour, though as a very conservative outside estimate it could potentially last as late as 2am. Sporadic periods of unresponsiveness, though unlikely, may also occur afterward. Our support team will be on-duty during and after this period to test and verify success of the operation and respond to any user inquiries or bug reports that could result.



TECHNICAL SUMMARY:



For the past few months we have been preparing to migrate E-junkie services into the Amazon Web Services (AWS) server cloud, so this event will formally engage that transition for our live production system. This migration will eliminate technical and performance limitations of our legacy colocated hosting provisions and related hardware, bringing the top-notch performance, responsiveness, security and reliability of the Amazon cloud to benefit E-junkie's services for you, our valued clientele.



This migration necessarily entails a change of server IPs for E-junkie.com, which should not affect the vast majority of you; however, if you know that you have set up a custom post-checkout integration script that verifies the transaction-data submissions it receives by either checking the originating IP or doing a reverse DNS lookup to confirm the IP resolves back to e-junkie.com, those IPs will change frequently henceforth, so your script will now need to either: A) check the originating IP against the list of IPs you get from a forward DNS lookup of e-junkie.com, or B) eliminate IP/DNS verification in favor of the 'handshake' value we provide in our integration POSTs, as we document here:

1http://www.e-junkie.com/ej/help.integration.htm1



(If you didn't understand the paragraph above, it almost certainly doesn't pertain to you, so don't worry about it. :^)



We thank all of you in advance for your patience and understanding as we engage this major upgrade to E-junkie's infrastructure.

As the revised post above indicates, we are now tentatively rescheduling this maintenance event for Thu22Sep2016 Midnight-2am MST/PDT (GMT -7) due to unexpected issues we encountered with consistency of data between our legacy transaction log database and the new DB we'd be using on AWS, so we have rolled back to our legacy system until then.



This DB synchronization is the reason for the extended service outage required to finalize this migration; we need to stop all DB changes on our production system, then resync the legacy DB to the new one on AWS for however long that takes, then validate the data matches at both ends before we could open the migrated system on AWS to public access. This time, we found the data did not match, so we need to identify and resolve the reason for that mismatch before we can proceed.



Thanks again to everyone for your patience and understanding, with our apologies for the fruitless disruption in service this time; we promise it will all be worthwhile in the end. :^)

Our Transaction Log server will be unavailable today (Wed21Sep2016) starting from 2pm MST/PDT (GMT -7) in preparation for our rescheduled cut-over to AWS later tonight. This will give us ample time to resync our legacy log DB to the new one on AWS and validate data consistency without needing to take our whole system down, then when we perform the actual cut-over, we'll only need to resync new log entries that have been added since this afternoon, which should minimize the necessary downtime. Thanks for your patience and understanding, with our apologies for the temporary inconvenience.

We have decided to postpone finalizing our migration to AWS for one more day, so this event is now rescheduled for Fri23Sep2016 starting at midnight. Our log server will be back online momentarily, and service was not disrupted at all tonight due to some remaining ambiguities that need to be settled before we can proceed. Thanks again for your patience, with our apologies for any inconvenience this rescheduling may pose for you.

We have now completed the migration of E-junkie services into the Amazon cloud as explained above. While we have done our utmost before and after this morning's cut-over period to prepare, test, and verify that everything should continue to work the same as before, please do not hesitate to contact us if you notice any strange misbehavior of our site, shopping cart, Admin panel, or other services:

https://www.e-junkie.com/ej/contact.htm



PayPal should automatically attempt to resend any IPNs (Instant Payment Notifications) that failed to reach us during the downtime, but if you're seeing payments in PayPal that still aren't showing up in your E-junkie Transaction Log, see step C here for instructions to have PayPal resend any failed IPNs:

1http://www.e-junkie.com/ej/trouble.paypal.order-not-processed.htm1



Thanks again to all of you for your patience, cooperation and understanding while we engaged this major upgrade to E-junkie's infrastructure.

One hiccup we've encountered so far is that AWS will not allow us to send emails with a From: address @ another domain, so from now on we will be sending all thank-you emails as From: "[your Display Name here]" <client@e-junkie.com>, with your actual Display Email in the Reply-to: header instead, so your buyers can still simply reply to their thank-you emails to contact you.



This was eventually going to become inevitable even with our old system anyway, as email providers get more strict about this sort of thing to cut down on spam, phishing, and other such nuisance emails. Operations is looking into resending the handful of early thank-you emails affected by this hiccup right now, but you can also use "Reactivate Expired Links / Resend Email" in your Seller Admin to reissue them yourself.