# Struggling with Google Calendar on 2nd NR instance

**URL:** https://discourse.nodered.org/t/struggling-with-google-calendar-on-2nd-nr-instance/14471
**Category:** General
**Created:** [19 August 2019 07:00 UTC](https://discourse.nodered.org/t/struggling-with-google-calendar-on-2nd-nr-instance/14471 "2019-08-19T07:00:49Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![michaelblight](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/michaelblight/32/445_2.png) [@michaelblight](https://discourse.nodered.org/u/michaelblight)
#### Post date: [19 August 2019 07:00 UTC](https://discourse.nodered.org/t/struggling-with-google-calendar-on-2nd-nr-instance/14471/1 "2019-08-19T07:00:49Z")

</div>

I have the Google Calendar node configured in the Node Red add-on to [hass.io](http://hass.io). I did this ages ago, so I'm not sure if I had much trouble.

Now I want to use the same node in another Node Red Docker install on another machine. I've create a new client & secret, and updated my laptop's hosts file to redirect `http://node-red.example.com` to `192.168.0.18` but when I click on "Authenticate with Google" I'm getting "redirect\_uri\_mismatch". If I browse to `http://node-red.example.com:1888` it opens Node Red, so the hosts file update looks correct (that container maps 1888 to 1880).

Any ideas on what I'm doing wrong?

---

<div class="post-metadata">

### Author: ![michaelblight](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/michaelblight/32/445_2.png) [@michaelblight](https://discourse.nodered.org/u/michaelblight)
#### Post date: [19 August 2019 08:20 UTC](https://discourse.nodered.org/t/struggling-with-google-calendar-on-2nd-nr-instance/14471/2 "2019-08-19T08:20:23Z")

</div>

I worked it out. When I was entering the authorized redirect URI, I was pasting it and clicking Save. I didn't realise it wasn't actually saving what was pasted - you need to paste, press Enter, and then Save.