I'll check the debug logs too and see what you're doing there.
Edit: Found the problem. It seems like you have an add-on that contains an unofficial rtbInfo.txt file which specifies the id as "3284" (which doesn't exist in our system) and the version number as "1.337" and since I break down the data on periods, it thinks you're checking for updates for "337" (God Gun Fixed) but not providing a version number.
Here's an example of the data you're transmitting with the broken part bolded:
121-1.475-2.442-1.327-2.579-3.961-2.4-1.13-2.285-1.647-1.881-3.337-1.840-2.1003-1.130-2.789-1.751-1.470-3.141-1.29-1.292-1.231-1.988-2.87-1.65-1.226-1.507-1.799-1.504-3.160-1.124-1.346-2.228-2.633-1.41-1.162-1.74-1.604-1.1682-1.301-1.746-1.735-9.188-3.134-1.189-2.136-1.706-1.210-1.187-3.66-1.132-1.890-1.1015-5.68-2.546-1.193-2.146-2.46-2.21-2.7-3.47-1.45-7.598-5.339-1.800-1.178-2.1544-1.311-10.1188-1.788-3.71-1.119-1.150-11.78-2.84-2.35-1.293-1.612-1.673-6.58-1.326-1.233-1.3284-1.337.209-1.641-2.105-2.61-2.230-2.102-1.97-2.148-2.205-2.108-1.229-1.227-1
It's in the format: fileId-version.fileId-version so putting a . in the version number is going to mess stuff up.
Long story short, it's some stuff you've downloaded or changed yourself and RTB is just doing what it was programmed to do.