Cannot Sell This Reserved Instance

You may receive the following error message from AWS when trying to sell your reserved instance:

This issue is likely due to one of these two problems:

  • There was an error retrieving the selected reserved instances details
  • Failed to exchange reservation due to: Can’t exchange from non-convertible classic offering
  • You’re not a registered AWS instance seller, register here.
  • You’re trying to sell a Standard  EC2 Reserved Instance with No Available Zone Scope
    • Per Amazon’s Requirements: Standard EC2 Reserved Instances can only be listed in the Reserved Instance Marketplace, if they are purchased with an Availability Zone scope. Since capacity is not reserved with regional RIs, they cannot be sold on the Marketplace at this time.

If you’re a registered seller and you are still receiving this error, you may be stuck with this particular reserved instance.

Some notes about selling reserved instances:

  • Reserved instances can be sold after they have been active for at least 30 days and once AWS has received the upfront payment (if applicable).
  • There must be at least one month remaining in the term of the Reserved Instance you are listing.
  • You must have a US bank account to sell Reserved Instances on the Reserved Instance Marketplace. Support for non-US bank accounts will be coming soon.
  • You will retain the pricing and capacity benefit of your reservation until it’s sold and the transaction is complete.
  • Your company name (and address upon request) will be shared with the buyer for tax purposes.
  • A seller can set only the upfront price for a Reserved instance. The usage price and other configuration (e.g., instance type, Availability Zone, platform) will remain the same as when the Reserved instance was initially purchased.
  • The term length for a Reserved instance will be rounded down to the nearest month. For example, a reservation with 9 months and 15 days remaining will appear as 9 months on the Reserved Instance Marketplace.
  • You can sell up to $50,000 in Reserved instances per year. If you need to sell more Reserved instances, complete the form found here.
  • Reserved instances in the GovCloud region cannot be sold on the Reserved Instance Marketplace.
  • Reserved instances purchased as part of a tiering discount cannot be sold in the Reserved Instance Marketplace.


pdfsizeopt – AssertionError: Multivalent failed (status)

This error could mean you’re using a  newer version of Multivalent which no longer has the pdf tools bundled into it. You’ll need this older version with the proper tools.

Download: Multivalent.jar

Just as a note though, pdfsizeopt is a pretty old program that may not be able to handle newer pdfs and may do a poor job optimizing many others.


File “./pdfsizeopt”, line 30, in <module>
File “./lib/pdfsizeopt/”, line 8081, in main
is_flate_ok=not do_decompress_flate)
File “./lib/pdfsizeopt/”, line 7773, in Save
File “./lib/pdfsizeopt/”, line 7691, in _RunMultivalent
assert False, ‘Multivalent failed (status)’
AssertionError: Multivalent failed (status)

/usr/bin/java -cp /users/lukerehmann/Multivalent.jar -Djava.awt.headless=true tool.pdf.Compress -nopagepiece -noalt -mon ADTTD_Product_Manual-Approved_Labeling_optimized.pdf
Exception in thread “main” java.lang.NoClassDefFoundError: tool/pdf/Compress
Caused by: java.lang.ClassNotFoundException: tool.pdf.Compress
at Method)
at java.lang.ClassLoader.loadClass(
at sun.misc.Launcher$AppClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(

Google Cloud : Service account not enabled on this instance

PHP Fatal error: Uncaught exception ‘Google\\Cloud\\Core\\Exception\\NotFoundException’ with message ‘{“error”:”invalid_request”,”error_description”:”Service account not enabled on this instance”}’ in /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php:241\nStack trace:\n#0 /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php(150): Google\\Cloud\\Core\\RequestWrapper->convertToGoogleException(Object(Google\\Cloud\\Core\\Exception\\NotFoundException))\n#1 /var/www/html/vendor/google/cloud/src/Core/RestTrait.php(86): Google\\Cloud\\Core\\RequestWrapper->send(Object(GuzzleHttp\\Psr7\\Request), Array)\n#2 /var/www/html/vendor/google/cloud/src/Storage/Connection/Rest.php(132): Google\\Cloud\\Storage\\Connection\\Rest->send(‘buckets’, ‘insert’, Array)\n#3 /var/www/html/vendor/google/cloud/src/Storage/StorageClient.php(225): Google\\Cloud\\Storage\\Connection\\Rest->insertBucket(Array)\n#4 /var/www/html/gcloudtest.php(20): Google\\Cloud\\Storage\\StorageClient->createBucket(‘my-new-bucket’)\n#5 {main}\n thrown in /var/www/html/vendor/google/cloud/src/Core/RequestWrapper.php on line 241

The FuzeCard Problem – EMV Chip Payments and Bank Negotiations

In the past couple years, we’ve seen the coming and going of several smart card companies promising to merge all your credit, debit, and rewards cards into one smart connected wallet. Despite the excitement surrounding all these products, they seem to run into one common wall when it comes to consumer deployment – EMV “Chip” Payments.

Coin and Plastc Shutdown, leaving millions of backers (and their money) out to dry. While Stratos and Swyp seem to be in a perpetual “sign up to get notified” phase. None of the cards have ever successfully supported Chip and Pin or EMV Payments. Why? Because it requires big connections and a large customer base to convince banks to open up their secure chip and pin technology to your ‘smart card’, and, unfortunately, this requires negotiations with each card issuer.

From FuzeCard’s website:

EMV payments require the approval of the card issuer/banks. Fuze’s chip will be compatible from the launch and this feature will be fully available with a future firmware update

As promising as this may sound, it’s not a software problem that Fuze is up against here and no simple firmware update will give the card the EMV support it needs. BrilliantTS will need to first negotiate with big banks, and that’s a tough sell at least 4 companies have failed to do thus far.

Do their promo cards have working EMV chips? According to their Instagram content, no, not yet.

One post from their instagram shows a box of bpay cards from a startup in South Korea. So, what do bpay and FuzeCard have in common? Both appear to be owned by BrilliantTS.

BrilliantTS’s bpay cards appear to have come to the same brickwall for EMV Payments, indicating only “Reserve Now!” for EMV Chip enabled cards.

bpay Card Options





com.OptiBuy.agent and com.MyMacUpdater.agent

Noticed the following suspicious startup items on a  friend’s Mac OS X 10.10.5:




The friend had constant McAffe ads in her default browser (Google Chrome).  The computer doesn’t have any recently installed items. The startup items were removed with CCleaner, the computer was updated with the updates available in the app store and restarted. Upon computer restart, Google Chrome indicated “mac search manager” was added. The computer was then updated to the latest version of OSX (macOS Sierra) and restarted.

To update your computer to Sierra, search macOS Sierra in the app store, download, and install. This is a fairly large update so it may take several hours to download and additional time to install.

Recursively Finding (and replacing) All Depreciated

Running the following code from your starting will give you the location of all short open tags in .php extension files. This command recursively searches all directories from the directory you start in.
grep -r --include "*.php" "<?[ ]" .

You may need to modify it if you have .php5 files or other non-php extensions holding php content.

If you’re looking to repalce all of these en-masse, you can do that [very roughly] with the following commands:

replace ALL tags (< ?) with

grep -rl --include "*.php" "<?[^p]" | xargs sed -i 's/<?/<?php/g'

fix any accidently replaced tags that might have happened
grep -rl --include "*.php""<?php" | xargs sed -i 's/<?phpphp/<?php/g'

You should carefully review all replacements done by this code, some php code could break!

Simple Proxmark3 Getting Started Guide on Windows

In the below video, we’ll be scanning a high frequency 13.56 MHZ card (NXP Mifare Classic) and two low frequency 125 kHz cards (HID and EM410x Tag)


  1. First, assemble your proxmark
  2. Download the latest compiled Proxmark3 Software from
  3. Unzip the file contents, and rename the content folder to proxmark3. For the commands following, you should have a folder in your downloads called proxmark3 with the following subfolders: win32, firmware_win, and Windows Driver. If you haven’t already updated your proxmark3 firmware to the latest version, go here.
  4. Open Device Manager to get the COM port of the Proxmark. In this case, it is COM7.
  5. Open Command Prompt (CMD)
  6. Execute the following command to connect to your proxmark3, be sure to replace your COM port with the proper COM port found in Device Manager

    Downloads\proxmark3\win32\proxmark3.exe COM7

  7. You’re now connected to the proxmark3! The following commands will do a low-frequency and high-frequency search for known devices.

    lf search

    hf search

  8. Questions and commends below!

Cards Scanned:

  • T5577 @ 125 kHZ
  • EM410x Tag M1 S50 @ 13.56 MHZ
  • HID ProxCard II @ 125 kHZ