Closed Bug 1023518 Opened 11 years ago Closed 11 years ago

Invalid partner credentials

Categories

(Hello (Loop) :: Server, defect, P1)

x86_64
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: alexis+bugs, Assigned: alexis+bugs)

Details

(Whiteboard: [qa-])

Attachments

(1 file)

We're getting errors from tokbox: Error: Failed to createSession. Error: An authentcation error occurred: (403) <?xml version="1.0" encoding="UTF-8" standalone="yes"?><errorPayload><code>-1</code><message>Invalid partner credentials</message></errorPayload> http://sentry.shared.us-west-2.prod.mozaws.net/loop-prod/loop/group/80439/
ccing Rob and Adam from tokbox, do you have an idea about what's going on? We're seing a bunch of these errors on the server but our credentials are valid.
Severity: normal → major
Priority: -- → P1
Likely due to a network problem we are having at our NY data center. We have routed around it for now but this may have caused intermittent problems between about noon and 1:00pm Pacific time today.
Alexis, since its intermittent, would it make sense to add a retry-loop on some of those backend calls ? Could that reduce the number of errors the client gets ?
Flags: needinfo?(alexis+bugs)
Indeed, will work on that tomorrow.
Assignee: nobody → alexis+bugs
Flags: needinfo?(alexis+bugs)
Thanks alexis! Can you point the bug here for reference ?
Flags: needinfo?(alexis+bugs)
Attached file link to github PR
Attachment #8438447 - Flags: review?(tarek)
Flags: needinfo?(alexis+bugs)
Benson, needinfo you to be sure you got it: you can add a "retryOnError" option inside the tokbox settings!
Flags: needinfo?(bwong)
Changeset is here for loop-server. https://github.com/mozilla-services/loop-server/commit/ed2d0d1a9f88fcc06aa2a0c38ed07958dc59448a Keeping it open until Benson does the appropriate changes on the config.
Status: NEW → ASSIGNED
Attachment #8438447 - Flags: review?(tarek) → review+
Whiteboard: [qa-]
the 0.6.0-dev snapshot deployed yesterday has the change in it.
Flags: needinfo?(bwong)
To be clear: deployed to stage.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
This should be out in Prod by now...
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: