Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Can't login: 403 Client Error: Forbidden for url: https://login.ford.com #488

Open
frankie-boy-hgv opened this issue May 7, 2024 · 336 comments
Open

Can't login: 403 Client Error: Forbidden for url: https://login.ford.com #488

frankie-boy-hgv opened this issue May 7, 2024 · 336 comments
Labels
bug Something isn't working

Comments

@frankie-boy-hgv
Copy link

2024-05-07 15:47:24.506 WARNING (MainThread) [custom_components.fordpass] 403 Client Error: Forbidden for url: https://login.ford.com/xxxxxxxxxxxxxxxxxxx/B2C_1A_SignInSignUp_EN-GB/SelfAsserted?tx=StateProperties=xxxxxxxxxxxxxxxxxxx&p=B2C_1A_SignInSignUp_en-AU
2024-05-07 15:47:24.506 WARNING (MainThread) [custom_components.fordpass] Error communicating with FordPass for xxxxxxxxxxxxxxxxxxx
2024-05-07 15:47:24.506 WARNING (MainThread) [custom_components.fordpass] Returning Stale data to prevent unavaliable status
2024-05-07 15:47:24.507 ERROR (MainThread) [custom_components.fordpass] Error fetching fordpass data: Error communicating with FordPass for xxxxxxxxxxxxxxxxxxx

Ford changed things again?
@JVTEAM
Copy link

JVTEAM commented May 7, 2024

Same issue here. Thought it was because I upgrade the Core, but it seems just bad timing.

@frankie-boy-hgv
Copy link
Author

Same here, right after updating to 2024.5.2 (from 2024.5.1)

@JVTEAM
Copy link

JVTEAM commented May 7, 2024

Same here, right after updating to 2024.5.2 (from 2024.5.1)

Ok, so it is core related.

@keller1982
Copy link

Seems like it.

I didn't change the core, I still have 2024.4.2 and I have the same error.

@400HPMustang
Copy link

Same issue on 2024.5.1

@JanosBerke
Copy link

Hi,

It is the same here, Ford must have changed something.

@D0NY3NK0
Copy link

D0NY3NK0 commented May 7, 2024

Same issue here.

@AndreiGavriliu
Copy link

Same here. I thought I got banned or something

@Picard16
Copy link

Picard16 commented May 7, 2024 •
edited
Loading

Same here in Germany with my Kuga.
Last successful sync was yesterday, 2024-05-06, at 16:20 CEST Europe.

@EnDoubleU
Copy link

EnDoubleU commented May 7, 2024 •
edited
Loading

Since 2024.5.2 the FordPass integration cannot initalize anymore. Logfile says: "Error fetching fordpass data: Error communicating with FordPass for vin number"
And since 16:10:07 of today (may 7) the "403 Client Error: Forbidden for url: https://login.ford.com/..." error.

@AlanJ500
Copy link

AlanJ500 commented May 7, 2024

Issue isn't core, it's on Fords side for this one. Maybe it will resolve itself? Or maybe some tweaks will need to be made.

@clabern
Copy link

clabern commented May 7, 2024

Same issue here, started around 9:31AM eastern.

@0sAND1s
Copy link

0sAND1s commented May 7, 2024 •
edited
Loading

Hi! The error I get in the log starting today is below. Thanks for any idea.

[139683214187072] 403 Client Error: Forbidden for url: https://login.ford.com/GUID-REMOVED/B2C_1A_SignInSignUp_EN-GB/SelfAsserted?tx=StateProperties=eyJUSUQiOiIxY2ZkMGNhZS1iMWQ1LTQ3ZTQtYTc1Yi1jNjMwZDUyOTEyOGIifQ&p=B2C_1A_SignInSignUp_en-AU

@alessandro1898
Copy link

Same issue for me in Italy with a Ford Puma. Can't login.

@bmwhitetx
Copy link

Have not updated anything HA related in a month. On Core 2024.4.3. Got this error today. Can't be HA related.

@dizzybro
Copy link

dizzybro commented May 7, 2024

Same here, can't login as of 5-7-2024

@itchannel
Copy link
Owner

Looks like an API change to the login flow. Will try and take a look later today. In the meantime I recommend people disable the integration in HA until I can fix it :)

@itchannel itchannel pinned this issue May 7, 2024
@domolys
Copy link

domolys commented May 8, 2024

Still running core 2024.1.6 and having the same issue

@scotty1395
Copy link

Working again for me in Australia. Entities became available about 90 minutes ago without a HA restart.

@frankie-boy-hgv
Copy link
Author

Not working here yet.

@frankie-boy-hgv frankie-boy-hgv mentioned this issue May 8, 2024
Closed
@0sAND1s
Copy link

0sAND1s commented May 8, 2024

I also noticed that the official FORDPASS app now shows some details that were previously unavailable/removed:

  • charging details (charging power, time, energy added, etc)
  • charging history
  • charging times & places
  • leaving time
    So it may seem that the API was changed on the FORD side.

@itchannel
Copy link
Owner

Initial looks it seems Ford have enabled Akamai Bot Manager in a fairly aggressive mode to prevent people calling the API Login from tools other than Fords own app.

This probably isn't going to be a quick fix. It does look like they have officially launched their developer api that people could use but only available in Northern America and severely limited so I'm unable to test or implement that.

Will keep playing and seeing if there's away round it.

@AlanJ500
Copy link

AlanJ500 commented May 8, 2024

@itchannel The new FordPass Connect API in the developer program does have feature parity according to the Ford team in charge of it. The only difference is that anyone who wants to use it must register their FordPass account to use it and prevent lockouts.

The Ford team has been attempting to reach out to you to get this functional / supported.

@ve6rah
Copy link

ve6rah commented May 8, 2024

You say only available in North America, in fact the website specifies only available in the US, so not even Canada!
That said, if I have to create a developer account to get things working, I'm willing to do that, but if it's not even going to work in my country, that's severely disappointing! And less than a week after I bought my truck!

If the Ford team is really trying to reach out to you though, absolutely take this opportunity! That's exactly what we've been waiting for! Anything they can do to help make this official would go a very long way to helping all of us.

@AlanJ500
Copy link

AlanJ500 commented May 8, 2024

^ The Ford team is. I don't speak for them, however my interactions with the team is that they do want to enable this type of functionality but also balance security concerns and legal concerns. The developer program is new, which is why it's US only right now. I am sure that will change over time.

@mclever
Copy link

mclever commented May 8, 2024

I signed up for a dev account, put n/a for company, and was poking around. From https://developer.ford.com/use-cases/connect-ford-to-daily-tracking-apps it says that the FordConnect API is available globally except for China. You can connect your dev account to Fordpass account and get API creds.

@400HPMustang
Copy link

You can connect your dev account to Fordpass account and get API creds.

Are you able to log in to the fordpass integration with those creds or does it require a different login URL?

@ve6rah
Copy link

ve6rah commented May 8, 2024

I signed up for a dev account, put n/a for company, and was poking around. From https://developer.ford.com/use-cases/connect-ford-to-daily-tracking-apps it says that the FordConnect API is available globally except for China. You can connect your dev account to Fordpass account and get API creds.

That's the tracking API only, that doesn't include things like unlocking or locking, remote start, etc. Scroll to the bottom of that page that you linked and will show the actual connect API separate and listed as USA only

@thoompje
Copy link

thoompje commented Jul 8, 2024

@thoompje:

I am seeing the same thing (and more). My debug log is also showing the .au URL and EN-AU language type, which is likely central to the issue. It looks like Ford changed their authentication also because when I attempt to do what you did, the location/payload for the authentication has changed from the instructions provided here. The location no longer references "fordapp://", but rather "account.ford.com..." Even if you did get the code though, it likely wouldn't matter if the add-in is still sending the request to the .au endpoint URL.

Ford

Thanks for sharing! Happy that I am not the only one. Hopefully somebody can jump in and help us!

@SquidBytes
Copy link
Collaborator

SquidBytes commented Jul 9, 2024 •
edited
Loading

Just popping in for an update from me.
I have been very sick the past few weeks and as soon as I recovered I had a very unexpected loss of a pet.
In addition, as usual, I am very swamped with work and its going to get busier for the next few weeks.

Thank you to everyone for helping each other out.
I'll still be around, just wanted to post something instead of nothing.
I get some free time, and have the mental bandwidth, I would like to get back into this. I just have nothing to give right now.

@JTertin
Copy link

JTertin commented Jul 10, 2024

Rest up, @SquidBytes... not being able to see my vehicle's odometer from Home Assistant isn't worth risking your health over, so take time and take care. :-) Really sorry to hear about your pet - we went through the same late last year with our Rottweiler-Shepherd dog and that was really tough.

@danielbrunt57
Copy link

My integration just started working again a couple of minutes ago after weeks of the integration not loading. I did not update to the beta version and I didn't disable the integration, so I wonder if Ford changed something on their end.

There's a pretty good chance they have!

@thewolfman56
Copy link

thewolfman56 commented Jul 17, 2024 •
edited
Loading

Accidentally deleted my comment...

The weird thing is that the integration is showing last refreshed 5 days ago, even though it just started working again.

@thoompje
Copy link

Finally it's working here! It's important that you get the whole string included "fordapp://userauthorized/?code=" with the rest of the code/token. and if you fill in one time the wrong code in home assistant you get invalid_token if you fill in the right code after it you get invalid_token / unknown error. So then you need to re add the integration into home assistant and do it the first time good, other wise it will fail a second time.

@ziptbm
Copy link

ziptbm commented Jul 29, 2024

Is anyone else seeing the 1.70 workaround failing periodically and requiring a re-auth? It seems like every other day, I check something on my vehicle and it's unavailable. The only thing I've found that fixes it is to try to re-auth with a new token and it comes back online.

@thewolfman56
Copy link

Finally moved to 1.70 . Is there any way to move to 1.70 other than manually replacing all of the files? HACS never showed anything higher than 1.68-Release (still shows as 1.68-Release in HACS even though I manually updated each file).

The instructions were pretty easy to follow. Now, my integration is refreshing at a more regular interval. The 1.68-Release would still connect every once in a while and update the sensors, but with old data. 1.70 seems to be working.

@sfumarolo
Copy link

@thewolfman56 Not until the maintainers mark 1.70 as an official "Beta" release.

@thewolfman56
Copy link

@thewolfman56 Not until the maintainers mark 1.70 as an official "Beta" release.

Thanks. Glad I didn't miss anything then.

@philipgo
Copy link

philipgo commented Aug 21, 2024 •
edited
Loading

Is there any way to move to 1.70 other than manually replacing all of the files?

HACS 2.0 was just released. It allows (via "Developer Tools") to install not only a release but also a Github branch. (I just entered 1.70 as version in the developer tools)

See the HACS instructions:
https://hacs.xyz/docs/use/entities/update/#considerations

@philipgo
Copy link

Does generating a token via ford.ie (for region UK/Europe, I am in Germany) work for anyone? When accessing the link generated by fordpass, the login form never opens.

@LarsTh86
Copy link

LarsTh86 commented Aug 21, 2024 via email

@mkernel
Copy link

mkernel commented Aug 22, 2024

I had the same problem with ford.ie and out of curiosity i tried using the US as country even though I'm in Germany and the car is registered and bought in Germany. That worked for me. I had no problems with the integration since then.

@dsolera
Copy link

dsolera commented Aug 22, 2024 via email

@philipgo
Copy link

Cool, thank you! I am in Germany, US endpoint works. NL produced an error and IE did not work at all.

@dmz006
Copy link

dmz006 commented Aug 22, 2024 via email

@400HPMustang
Copy link

How did you use developer tools to specify a branch?
…
On Wed, Aug 21, 2024 at 1:38 PM philipgo @.> wrote: Is there any way to move to 1.70 other than manually replacing all of the files? HACS 2.0 was just released. It allows (via "Developer Tools") to install not only a release but also a Github branch. (I just entered 1.70 as version in the developer tools) — Reply to this email directly, view it on GitHub <#488 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEGAC343IY3CQCA4IWXI5LZSTGAXAVCNFSM6AAAAABHLB227CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBSGYZDGOJWHE . You are receiving this because you commented.Message ID: @.>

https://hacs.xyz/docs/use/entities/update/#considerations

@dovy6
Copy link

dovy6 commented Aug 22, 2024 via email

@danchace
Copy link

This is what I did: Install version 1.68 (but don't set anything up), then go to 'Developer tools' in Home Assistant, perform the following "action" with these settings and button. This will trigger an offer to update to version 1.70. Restart HA and ignore the prompt to update back to 1.68.
Screenshot 2024-08-22 at 12 38 47 PM

@degrashopper
Copy link

1.70 works for me! located in NL, used NL setup. Follow @danchace instructions after you update HACS to 2.0 and you can easily update fordpass to 1.70.

@aeicherly
Copy link

The instructions on how to get 1.70 installed were excellent. Is there a way to get lincoln vehicles working with the new token process? Has anyone had success doing this? Thanks.

@LarsTh86
Copy link

LarsTh86 commented Sep 3, 2024

Does anyone have any instructions? I don't get it to run. I always get an error message. I'm from Germany and use North America.

@philipgo
Copy link

philipgo commented Sep 3, 2024

Could you provide more details on where you encounter which error? Did you install fordpass-ha 1.70?

@LarsTh86
Copy link

LarsTh86 commented Sep 4, 2024

the installation of 1.70 worked. that's not the problem, that was already before the description. it's about setting up the Fordpass instance. there always comes "unknown error" in the end.

@philipgo
Copy link

philipgo commented Sep 4, 2024

"There" is still not very specific. On the Ford web site? In HA?

@LarsTh86
Copy link

LarsTh86 commented Sep 4, 2024

After insert the token from Ford-website to Homeassistant, ha try to implement the Fordpass-instances. That is also my problem, that the error message is really unspecified

@gmbrown21 gmbrown21 mentioned this issue Sep 9, 2024
Closed
@Dangeryeen
Copy link

This is what I did: Install version 1.68 (but don't set anything up), then go to 'Developer tools' in Home Assistant, perform the following "action" with these settings and button. This will trigger an offer to update to version 1.70. Restart HA and ignore the prompt to update back to 1.68. Screenshot 2024-08-22 at 12 38 47 PM

I can't even get fordpass to show under targets, everything is to update, not sure what I'm doing wrong.

Installed 1.68 on hacs, restarted, went to dev actions to update and 'fordpass' won't show under anything

@TheLizard TheLizard mentioned this issue Oct 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests