# Google TTS node not working
**URL:** https://discourse.nodered.org/t/google-tts-node-not-working/34275
**Category:** General
**Created:** [15 October 2020 07:37 UTC](https://discourse.nodered.org/t/google-tts-node-not-working/34275 "2020-10-15T07:37:37Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@bigfeetneedbigboots](https://discourse.nodered.org/u/bigfeetneedbigboots)
#### Post date: [15 October 2020 07:37 UTC](https://discourse.nodered.org/t/google-tts-node-not-working/34275/1 "2020-10-15T07:37:37Z")
I have had a flow where I use the node-red-contrib-google-tts node to convert a string into a url then the node-red-contrib-cast node to play the resulting audio on a Google Nest device for over a year. During the last week I haven't heard many announcements in the house so I ran some tests today and found it doesn't work anymore.
In the logs I am getting:
> (node:537) UnhandledPromiseRejectionWarning: FetchError: request to [https://translate.google.com](https://translate.google.com) failed, reason: connect ECONNREFUSED 0.0.0.0:443
> at ClientRequest. (/config/node-red/node\_modules/node-fetch/index.js:133:11)
> at ClientRequest.emit (events.js:315:20)
> at TLSSocket.socketErrorListener (\_http\_client.js:426:9)
> at TLSSocket.emit (events.js:315:20)
> at emitErrorNT (internal/streams/destroy.js:92:8)
> at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
> at processTicksAndRejections (internal/process/task\_queues.js:84:21)
> (node:537) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see [Command-line API | Node.js v21.5.0 Documentation](https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode)). (rejection id: 6)
I have tried deactivating SSL for Node-RED but that didn't solve anything. The network hasn't changed.
Appreciate any help or insight offered.
---
### Author:  [@bigfeetneedbigboots](https://discourse.nodered.org/u/bigfeetneedbigboots)
#### Post date: [15 October 2020 21:21 UTC](https://discourse.nodered.org/t/google-tts-node-not-working/34275/2 "2020-10-15T21:21:01Z")
Update:
I've put debug nodes on either side of the node-red-contrib-google-tts node and I can see messages going in but not coming out i.e. the flow halts.
Also, I have tried this on a fairly fresh install of Node-RED (on IOTstack docker) and get the same issue.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [15 October 2020 21:38 UTC](https://discourse.nodered.org/t/google-tts-node-not-working/34275/3 "2020-10-15T21:38:36Z")
I suspect you may have to contact the author via the node's project page as it's not one I suspect many folk use regularly.
---
### Author:  [@bigfeetneedbigboots](https://discourse.nodered.org/u/bigfeetneedbigboots)
#### Post date: [16 October 2020 23:50 UTC](https://discourse.nodered.org/t/google-tts-node-not-working/34275/4 "2020-10-16T23:50:17Z")
OK, it is fixed. Turns out it was my AdGuard DNS filtering. "[translate.google.com](http://translate.google.com)" had been added to one of the blacklists it is subscribed to and that killed it. Hope this helps someone else in future.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [30 October 2020 23:50 UTC](https://discourse.nodered.org/t/google-tts-node-not-working/34275/5 "2020-10-30T23:50:30Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.