Runtime Exception: EDIT: Ended up being an IP ban of my shared hosting to home.nest.com

[sparky672]

Runtime Exception: Response to login request doesn't contain required transport_url. Response: null

Been working great for years. Suddenly today, I am getting the above error. I regenerated the $issue_token and $cookies values as per the detailed instructions, but this error continues.

Any suggestions?

Thank you!

EDIT: On this step, not sure if it matters much, but this value is no longer "ending with nest.com".

• In the Headers tab, under General, copy the entire Request URL (beginning with https://accounts.google.com, ending with nest.com). This is your $issue_token.

After nest.com, it then has &include_granted_scopes=true&auto=0

---

Here is the code from nest.class.php that is generating the message I am seeing:

$result = $this->doPOST("https://home.nest.com/api/0.1/user/{$this->userid}/app_launch", json_encode($params), array('Content-type: text/json'));
            if (empty($result->service_urls->urls->transport_url)) {
                throw new RuntimeException("Response to login request doesn't contain required transport_url. Response: " . json_encode($result));
            }

I am fairly stuck here. Why is transport_url suddenly empty? Is the api URL different now? Inspecting the network traffic in Chrome is getting me nowhere. This problem just started yesterday or today.

[bauzer714]

Login to the device on home.nest.com and after clicking on your device, see if the end of the url is DEVICE_{a hexidecimal value} or if it's the serial number.

If it is the DEVICE_, should be back in business following the below. We've seen this happen seemingly random for several years, this seems to be the fix: #115 (comment)

[sparky672]

Login to the device on home.nest.com and after clicking on your device, see if the end of the url is DEVICE_{a hexidecimal value} or if it's the serial number.

If it is the DEVICE_, should be back in business following the below. We've seen this happen seemingly random for several years, this seems to be the fix: #115 (comment)

Thank you for your reply. The URL contains the serial number, not "DEVICE_"

https://home.nest.com/thermostat/09AA0xxxxxxxx

[sparky672]

For session, Request URL does not match Transport URL ... not sure if this is relevant?

[bauzer714]

My session response looks similar to yours. I went through setting up the cookies and account token again and it's working properly. Might want to walk through the login again, perhaps in incognito or guest mode. I recall at one point having issues where my multiple google accounts caused some issues too.

As another attempt... perhaps there's an issue with the temporary files - and you can delete the php temporary files starting with nest_php_.

[sparky672]

My session response looks similar to yours. I went through setting up the cookies and account token again and it's working properly. Might want to walk through the login again, perhaps in incognito or guest mode. I recall at one point having issues where my multiple google accounts caused some issues too.

I carefully went through it four times yesterday, each in a new Chrome Incognito window. I am at a total loss with this.

I did notice the new cookie value is huge compared to the last working value. About 4 times the size.

As another attempt... perhaps there's an issue with the temporary files - and you can delete the php temporary files starting with nest_php_.

Where are those stored? I cannot seem to find them on my server? EDIT: NVM... I found them in .cagefs/tmp in my root. Deleting these made no difference.

Thank you for your help and suggestions.

[bauzer714]

Sorry @sparky672, wish I could help more but I haven't been able to reproduce it. I've tried incognito, guest mode, everything I do to grab the values following the instructions work as expected. And I didn't address it previously, but my new value also included these values: &include_granted_scopes=true&auto=0

[sparky672]

Sorry @sparky672, wish I could help more but I haven't been able to reproduce it. I've tried incognito, guest mode, everything I do to grab the values following the instructions work as expected. And I didn't address it previously, but my new value also included these values: &include_granted_scopes=true&auto=0

I appreciate everything you've done. I have dumped those cache files and regenerated the token and cookie twice more today.
I am using an Incognito window every single time. I have no idea why this is not working.

[sparky672]

On this step...

• Several network calls will appear in the Dev Tools window. Click on the last iframe call.

Sometimes this list only contains xhr and sometimes there are also document calls. So which one is considered "the last iframe call"? The last document or the last xhr? This is critical as the cookie value is different between these calls.

I have been trying it both ways and nothing is working. Also trying in Guest mode as well as Incognito.

At this point, I need some solid troubleshooting advice.

[sparky672]

Another thought... is it possible that caching on my server is breaking this?

So I enter the new token and cookie and upload the config file. I immediately try it out, but because of my server's cache, it's still using the old token and cookie. I noticed this when updating other files... that it took several minutes for the file to reflect the updates on the public site.

Does using the old expired token and cookie trigger a removal or invalidation of the new one?? Could this simply be a timing issue?

[bauzer714]

We can't with full confidence speak to your server configuration and it's caching, but the only cache that the library has is in the temporary files, but it attempts to delete them upon a failure. There is no auth invalidation occurring.

[sparky672]

We can't with full confidence speak to your server configuration and it's caching, but the only cache that the library has is in the temporary files, but it attempts to delete them upon a failure.

Yes. I found those cache files and have been deleting them. I am at a total loss. I've been using this package for years and years, and never had an issue to this extent. Although, now I am on a new hosting account as of a couple months ago.

Thinking out loud.... I don't think deleting and re-adding the thermostat would matter since I cannot even get into the nest account via this API for any of the nest data.

There is no auth invalidation occurring.

Thank you. That is helpful in avoiding a red herring.

I really do appreciate you sticking with me on this.

[sparky672]

UPDATE:

I went to Firefox to try...

Now I am getting this instead:

Unexpected Value Exception: Response to login request doesn't contain required access token. Response: {"error":"USER_LOGGED_OUT","detail":"No active session found."}

NOTES & QUESTIONS?:

• I noticed the cookie values in Firefox are very different than the values I was getting from Chrome. The cookie value is much shorter and starts with different characters.

• The Issue Token is the same no matter how many times I generate it and no matter which browser I use. The only difference is that the value from Firefox does not have the spaces encodes as %20. When looking at my last known working value for $issue_token, the spaces are %20 and the URL ends with home.nest.com&include_granted_scopes=true&auto=0 I don't know if this value should be fully encoded, not encoded, or only spaces encoded. All I know is that my last known working values have stopped working and give me the Transport URL Missing error.

• As far as which "iframe" request to use for obtaining the new cookie, I am assuming it's the last xhr iframeprc on the network list since its Referrer URL matches the URL used the nest PHP class.

• I have been using Chrome on Mac High Sierra. I installed Chrome fresh on Windows 11 and tried it there. I am right back to Runtime Exception: Response to login request doesn't contain required transport_url. Response: null.

• Another weird observation. Using Chrome in Win 11 with Incognito window results in a login loop. Asks for Google account and after I enter it, it asks to login via Google again... stuck in this loop forever. Since it's new install, I just dump the browsing cache and use a regular window to log in.

[sparky672]

Depending on the browser used, the error message is different. Since I have be repeatedly going through the steps using various browsers, I am discovering these results repeatable, which would seem to indicate an issue that would have nothing to do with me not following the steps exactly.

Values obtained from Chrome (Mac High Sierra) in Incognito mode:

Runtime Exception: Response to login request doesn't contain required transport_url. Response: null

Values obtained from Chrome (Mac High Sierra) in Guest mode:

Runtime Exception: Error: HTTP 403 from request to https://home.nest.com/api/0.1/user/xxxxxx/app_launch. Response: 403 Forbidden

Values obtained from Chrome (Windows 11) in Guest mode:

Runtime Exception: Error: HTTP 403 from request to https://home.nest.com/api/0.1/user/xxxxxx/app_launch. Response: 403 Forbidden

Values obtained from Edge (Windows 11) in normal mode:

Runtime Exception: Error: HTTP 403 from request to https://home.nest.com/api/0.1/user/xxxxxx/app_launch. Response: 403 Forbidden

Values obtained from Firefox (Mac) private browsing mode:

Unexpected Value Exception: Response to login request doesn't contain required access token. Response: {"error":"USER_LOGGED_OUT","detail":"No active session found."}

Chrome (Windows 11) in Incognito mode results in an endless Google login loop. - After correctly entering my password, it just redirects back to the login page. Tried several times, each in a new Incognito window.

---

On the main page of this repository in the README are these comments:

"Unexpected Value Exception: " // Happens when the issue_token or cookie is not working, for whatever reason

"Runtime Exception: " // Probably a temporary server-error

[sparky672]

After a ton of work and troubleshooting, a test script that works locally is giving the 403 errors when put onto my shared server. Apparently, my shared server has been "IP banned" by Google. I was able to prove this by borrowing proxy credentials and trying again. It works.

However,

• I cannot explain why cookie values obtained from different browsers are giving different error messages.
• I do not know if the Google IP ban is permanent or temporary.

My options at this point...

• buy a monthly proxy
• upgrade my shared hosting to a dedicated IP (same price as proxy)
• just wait it out and hopefully the Google IP ban is temporary
• run this Nest API locally from my machine, rather than from my shared hosting

I am leaning toward the 4th bullet if the third doesn't resolve.

EDIT: Tried it on another hosting account that I manage, and it's working fine there. The hosting company confirmed that there is an IP ban from "home.nest.com" on their server.