Frankfurt Text-to-Speech service gives Unauthorized when Dallas TTS doesn't
I have a nodeJS web app that I have deployed many times to Frankfurt and suddenly the TextToSpeechV1.synthesize call is returning the message.
"Unauthorized: Access is denied due to invalid credentials." with stack info: "Error: Unauthorized: Access is denied due to invalid credentials.
at Request._callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/watson-developer-cloud/lib/requestwrapper.js:102:21)
at Request.self.callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:185:22)
at Request.emit (events.js:180:13)
at Request.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1157:10)
at Request.emit (events.js:185:15)
at IncomingMessage.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:272:13)
at IncomingMessage.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)"
This doesn't happen if I switch the username, password and url to a TTS running for the same web app in Dallas region. This was working earlier. The username, password and url are from a TTS service in Frankfurt so I know those are right and valid.
I've tried creating a brand new TTS service in Frankfurt and use the iam_apikey but there I just get null back from the synthesize call and null back on the object returned in the callback.
I'm using watson-developer-cloud 3.13.0, but I was using 3.5.0 without problems. Both 3.13.0 and 3.5 have behaved the same.
node.js text-to-speech ibm-watson
edited Nov 14 at 0:48
Mamoon Raja
42416
asked Nov 12 at 17:42
Troy
1618
add a comment |
I have a nodeJS web app that I have deployed many times to Frankfurt and suddenly the TextToSpeechV1.synthesize call is returning the message.
"Unauthorized: Access is denied due to invalid credentials." with stack info: "Error: Unauthorized: Access is denied due to invalid credentials.
at Request._callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/watson-developer-cloud/lib/requestwrapper.js:102:21)
at Request.self.callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:185:22)
at Request.emit (events.js:180:13)
at Request.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1157:10)
at Request.emit (events.js:185:15)
at IncomingMessage.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:272:13)
at IncomingMessage.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)"
This doesn't happen if I switch the username, password and url to a TTS running for the same web app in Dallas region. This was working earlier. The username, password and url are from a TTS service in Frankfurt so I know those are right and valid.
I've tried creating a brand new TTS service in Frankfurt and use the iam_apikey but there I just get null back from the synthesize call and null back on the object returned in the callback.
I'm using watson-developer-cloud 3.13.0, but I was using 3.5.0 without problems. Both 3.13.0 and 3.5 have behaved the same.
node.js text-to-speech ibm-watson
edited Nov 14 at 0:48
Mamoon Raja
42416
asked Nov 12 at 17:42
Troy
1618
Thanks for the edits and I'll do better next time. :)
– Troy
Nov 14 at 23:11
add a comment |
I have a nodeJS web app that I have deployed many times to Frankfurt and suddenly the TextToSpeechV1.synthesize call is returning the message.
"Unauthorized: Access is denied due to invalid credentials." with stack info: "Error: Unauthorized: Access is denied due to invalid credentials.
at Request._callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/watson-developer-cloud/lib/requestwrapper.js:102:21)
at Request.self.callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:185:22)
at Request.emit (events.js:180:13)
at Request.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1157:10)
at Request.emit (events.js:185:15)
at IncomingMessage.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:272:13)
at IncomingMessage.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)"
This doesn't happen if I switch the username, password and url to a TTS running for the same web app in Dallas region. This was working earlier. The username, password and url are from a TTS service in Frankfurt so I know those are right and valid.
I've tried creating a brand new TTS service in Frankfurt and use the iam_apikey but there I just get null back from the synthesize call and null back on the object returned in the callback.
I'm using watson-developer-cloud 3.13.0, but I was using 3.5.0 without problems. Both 3.13.0 and 3.5 have behaved the same.
node.js text-to-speech ibm-watson
edited Nov 14 at 0:48
Mamoon Raja
42416
asked Nov 12 at 17:42
Troy
1618
I have a nodeJS web app that I have deployed many times to Frankfurt and suddenly the TextToSpeechV1.synthesize call is returning the message.
"Unauthorized: Access is denied due to invalid credentials." with stack info: "Error: Unauthorized: Access is denied due to invalid credentials.
at Request._callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/watson-developer-cloud/lib/requestwrapper.js:102:21)
at Request.self.callback (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:185:22)
at Request.emit (events.js:180:13)
at Request.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1157:10)
at Request.emit (events.js:185:15)
at IncomingMessage.<anonymous> (/Users/troy/git/WA-for-Auto-WebApp-master/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:272:13)
at IncomingMessage.emit (events.js:185:15)
at endReadableNT (_stream_readable.js:1106:12)
at process._tickCallback (internal/process/next_tick.js:178:19)"
This doesn't happen if I switch the username, password and url to a TTS running for the same web app in Dallas region. This was working earlier. The username, password and url are from a TTS service in Frankfurt so I know those are right and valid.
I've tried creating a brand new TTS service in Frankfurt and use the iam_apikey but there I just get null back from the synthesize call and null back on the object returned in the callback.
I'm using watson-developer-cloud 3.13.0, but I was using 3.5.0 without problems. Both 3.13.0 and 3.5 have behaved the same.
node.js text-to-speech ibm-watson
node.js text-to-speech ibm-watson
edited Nov 14 at 0:48
Mamoon Raja
42416
asked Nov 12 at 17:42
Troy
1618
edited Nov 14 at 0:48
Mamoon Raja
42416
asked Nov 12 at 17:42
Troy
1618
edited Nov 14 at 0:48
Mamoon Raja
42416
edited Nov 14 at 0:48
Mamoon Raja
42416
edited Nov 14 at 0:48
Mamoon Raja
42416
42416
asked Nov 12 at 17:42
Troy
1618
asked Nov 12 at 17:42
Troy
1618
asked Nov 12 at 17:42
Troy
1618
1618
Thanks for the edits and I'll do better next time. :)
– Troy
Nov 14 at 23:11
add a comment |
Thanks for the edits and I'll do better next time. :)
– Troy
Nov 14 at 23:11
Thanks for the edits and I'll do better next time. :)
– Troy
Nov 14 at 23:11
Thanks for the edits and I'll do better next time. :)
– Troy
Nov 14 at 23:11
add a comment |
1 Answer
1
active
oldest
votes
Changing to the standard plan fixed the problem. The TTS service in Dallas was standard plan, but the TTS service in Frankfurt was lite plan. Something must have changed in the lite plan that caused this to break as it was working earlier.
answered Nov 12 at 19:29
Troy
1618
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267423%2ffrankfurt-text-to-speech-service-gives-unauthorized-when-dallas-tts-doesnt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Changing to the standard plan fixed the problem. The TTS service in Dallas was standard plan, but the TTS service in Frankfurt was lite plan. Something must have changed in the lite plan that caused this to break as it was working earlier.
answered Nov 12 at 19:29
Troy
1618
add a comment |
Changing to the standard plan fixed the problem. The TTS service in Dallas was standard plan, but the TTS service in Frankfurt was lite plan. Something must have changed in the lite plan that caused this to break as it was working earlier.
answered Nov 12 at 19:29
Troy
1618
add a comment |
Changing to the standard plan fixed the problem. The TTS service in Dallas was standard plan, but the TTS service in Frankfurt was lite plan. Something must have changed in the lite plan that caused this to break as it was working earlier.
answered Nov 12 at 19:29
Troy
1618
Changing to the standard plan fixed the problem. The TTS service in Dallas was standard plan, but the TTS service in Frankfurt was lite plan. Something must have changed in the lite plan that caused this to break as it was working earlier.
answered Nov 12 at 19:29
Troy
1618
answered Nov 12 at 19:29
Troy
1618
answered Nov 12 at 19:29
Troy
1618
answered Nov 12 at 19:29
Troy
1618
1618
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267423%2ffrankfurt-text-to-speech-service-gives-unauthorized-when-dallas-tts-doesnt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Thanks for the edits and I'll do better next time. :)
– Troy
Nov 14 at 23:11