Site Login

This Months Donations

$65.35
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
SiesMAN01
$2.00
andrea
$2.00
André Philipi da Silva
$2.00
Ruslan
$2.00
Keanu Allridge
$5.00
Number of donations
23
Highest donation
$10.00
Average donation
$3.26

REGARDING 403 ERRORS

7 months 4 days ago #1 by Wobbles
Huy guys, I have seen the uptick in reports of...

Huy guys, I have seen the uptick in reports of 403 errors over the past week or so. IM 1.6 as you know has not been updated in a couple years now and the production site it gets it's live info from (https://InputMapper.com) has not had any changes in roughly a year, so in short we have no clue what could have caused this (yet) but are pretty confident it is not from our side. To further investigate, anybody experiencing 403 errors please post at https://beta.inputmapper.com/forum/general-chit-chat/403-errors-data-collection-thread/ your ISP (internet service provider), geographic location (as detailed as you care to provide but please no full addresses), OS (including build # found by typing "winver" into a run or find box), and frequency of error occurance (every time, nearly every time, rare etc)

As a temporary fix, you can disable error prompts in 1.6 in the settings, or you can log into an account, so far tests indicate this only happens when no login info is provided.

NOTE: 403 errors have absolutely NOTHING to do with the operation of the controller or other issues you may be having, 403 error just means it had issues fetching news, donation data, updates, or user account info from our server. Any controller or program issues you are having that affect the devices operation should be reported as if the 403 error does not exist because it has nothing to do with it.

UPDATE 5/16: Further investigation into this is being suspended indefinately for the following reasons;

  • The issue has no bearing on operation of InputMapper

  • The dialog generated by the error can be disabled in IM settings

  • The issue seems to originate from the CDN due to increased security measures

  • The modifications to 1.6 would be pointless with it nearing the end of it's life and 1.7 not having this error

The topic has been locked.
Powered by Kunena Forum