InfinityRazz

I've been told in previous support requests that I can not activate this api myself.. And while the rest api is great for fetching data, it does little to provide editing data outside of pages/forums/groups (pretty much not license keys specifically). Like I know I could do a custom datetime/string field on the license/purchase object, then check if field is null or has invalid data on first usage, then post that and yadda yadda, But that requires ~ 2-4 other rest calls to fetch surrounding data. I'm just looking for something ez breezy to "click and run" pretty much 😛

Sadly as a cloud user I don't have access to any api that requires me to edit constants in the index to activate it though right? The license key activation/usage api would work for that I believe (Activate license key, post activation/expiration date to my azure db on successful activation from Invision) but I can't activate it 😞 or i'm completely misunderstanding how that api works I feel like nothing in the rest api will allow me to edit the license directly, though I'm sure I could piecemeal something together with enough effort. 😛 A way to edit multiple licenses (or group edit expiration dates) in future versions sure would be a nice feature... 😉 https://tenor.com/rYclqw6noiG.gif

That's... unfortunate. 80+ license's by hands gonna be rough. :') May have to look into utilizing an external DB to handle expiration dates then, or see if we can rig something up in pages for a customized date.. 🤔

Hey community! Is there a simple way to batch update the expiration date of all active license keys generated by the site? Or would I be stuck manually updating every single license by hand? Using the cloud hosted community if that makes a difference at all 😛 Not really my area of expertise, and I'm weary of running any google found code for fear of damaging my community severely. 😅

For reference: Here's what I get when I try to log in externally: and what my partner is getting on his end now: message-3.txt

So all of a sudden today, as of about 11am mst, absolutely none of my users can log into our custom external app via OAuth.. Every single one of us is getting a 401 exception with some cloudlfare message popping up telling them to contact the admin.... Well I have no idea what the hell is going on so... what's up? This is affecting business and costing us money...

Ditto 😅 I still have 2 days left to pay my invoice so at least I know it's not that 🤣

I also just experienced this for the last 10 minutes trying to access my site, and Invision its self was ridiculously slow to load (15+ seconds per page, if it loaded at all)

"Not to mention, there is a significant update to Pages underway." Oh God no, our applications are closely ingrained with pages xD might be time to move our databases to azure/AWS O.o One thing one of our admins can't seem to let go of: Version 5 will be available to all cloud customers correct? Including the ones still on a legacy plan?

So again, we haven't changed how we handle Rest API requests in a long while now. The library performing said requests hasn't been recompiled in nearly a year as it's been stable until 7 days ago. This seems to be the most common error our users get (Again, we have not changed the type or frequency of calls) Like sure we've had a small influx of new users this month, but it's just replacing users that have already left our community. I would like some clarification on what classifies as "Too many requests" and "Short Time" please. We hardly ever have 65 unique users online on the website / making requests via oAuth at any given moment. Nor do I see any immediate indication of our site hitting our user cap in admin panel. According to admin panel: "Active user" graph Bandwidth usage: I don't see anything in system or error logs to indicate my users having connection issues, nor are Rest API requests made with an oAuth token actually logged in our logs (they're supposed to when checked no?) so I don't get to see what the users actually doing/experiencing. Could it be they're hitting a node that's under attack and therefore can't connect to the site properly? (they do report slow connection speeds via browser as well). Majority of users are fine, but it's the one's affected that complain the loudest 🤷‍♀️

Also getting this issue, tons of 4XX errors on my RestAPI calls in the last hour or so. Couldn't connect to here via PC but had no issue via mobile however 🤷‍♂️ Some of my users have been having issues since December 24/25 at this point, and at least 1 of the sites mentioned above by @David have shown multiple servers offline the whole week while Invision status tracker shows no problem.

I'll admit one use case was my fault.. Was trying to use 'ExecuteAsync' instead of 'PostAsync' to generate an oAuth token (whoops) However (and we have tested with multiple users): ever since December 25/26 once a user connects to our site on their 3rd -5th account -> ALL of their connected tokens start throwing 403 exceptions and wind up crashing their active sessions. Upon login we should only be calling oAuth/token for the token-> /core/me for user id/email -> nexus/purchases for users purchases, then query every active license for its custom fields (1-10 license) + it's corresponding records DB entry, as well as periodic heartbeat to /core/hello to verify token validity/site connection which doesn't seem like an "excessive" amount of rest API calls to me. Keeping in mind we haven't touched and/or made changes to the client side of the API calls in over a year.

So has this problem since been fixed? While I noticed no "slowing" of our cloud community, suddenly users randomly get a 403 "Request could not be satisfied" error randomly while utilizing our sites rest API.

https://status.invisioncommunity.com/ Tbf, does say systems under maintenance..

My thread (while not 1:1, follows the same gist): Then I made a post ~ a year after because posting an image to a database records upload field would also not work, but I stopped getting responses on that thread. 🤷‍♂️ Either way, excited to see this change coming. Really need to go over the updates as I also just noticed new options for OAuth tokens 🙂