I am not a programmer (especially not Java), but perhaps it is possible to influence the TLS fingerprint at this point:
Maybe not a solution but a way to find out if the TLS-Fingerprint is the problem or not.
I am not a programmer (especially not Java), but perhaps it is possible to influence the TLS fingerprint at this point:
Maybe not a solution but a way to find out if the TLS-Fingerprint is the problem or not.
@Mohammad_Rezaur_Rahm hat im deutschen Teil gerade die Doku zur Yahoo API gepostet: Rate Limits
GET Requests Per Minute 60 Number of GET requests allowed in a minute per user account.
per user account - PP has no account for yahoo. Is that the problem?
The Yahoo DSP API is a service that provides Yahoo and partner developers with RESTful access to Yahoo DSP advertising and reporting features. You can use these services to programmatically monitor, create and manage advertising campaigns.
Thats not the API used for quotes.
I have the same problem. It was working fine on Friday.
Edit
I tried using a VPN to see if the problem was linked to my IP, but it didnât resolve the problem.
Also ran into this issue today. Not sure that full-blown impersonation is required here. With curl, simply adding a user agent header to the request (e.g. -A âMozilla/5.0â) appears to already fix this. So this may be a simple fix?
For me Yahoo has been working fine with PP all the time until the recent PP update a couple of days ago. So, I share your suspicion. Who can shed light on this ? Is it possible to downgrade to the previous version ? Many thanks
I everyone, I tryed with the version 0.74.0 (january 2025) that keep not updated on another computer and it failed alsoâŚ
No, the update isnât the reason. Yahoo changed their API to limit the access/requests.
If you want, you could download an old version from GitHub, but trust me that wonât help.
Maybe this combined with a function that waits a random wait time between fetching each quote - e.g. wait a random time greater than 5 seconds and less than 15 seconds?
You can help yourself here: Releases ¡ portfolio-performance/portfolio ¡ GitHub
My advice: spent your time for something different.
The issue with downloading historical data occurred yesterday, May 5, 2025. Everything was still OK on May 2, 2025 (version 0.76.0).
Start reading the last answers. That isnât the issueâŚ
Such a yahoo change also has its good side - we havenât had as many new registrations in the forum as in the last few days for a long time.
But if everyone just writes âit doesnât work for me eitherâ, thatâs not really helpful either.
The problem is not a bug in PP, but the cat and mouse game that data providers (in this case yahoo), who would like you to display their data in a browser, including adverts etc., play with tools that only try to use the data.
Right now the cat is winning, so give the mouse a little break so it can think of a smart move.
Sorry, @Andreas, for comparing you to a mouse here, even though youâre actually the giant.
Thereâs also a bug when you are trying to add a new security in the app. Can you add it manualy from yahoo?
NO! This is not a bug but a side effect, with the same origin.
Do you think that it will be fixed?
If you follow this thread here, youâll realize people are already getting their heads around. Just be a little patient, world doesnât end today.
You can still make use of other sources.
Of course, but I guess that prob it could be unfixable. Thank you for answering