Puppeteer scraping stopped working

This topic is: resolved

 

Thank you for contacting me. Please note that I live in the GMT+3 time zone - responses might be delayed by this.

This topic has 8 replies, 2 voices, and was last updated 1 year, 5 months ago by Szabi – CodeRevolution.

Viewing 8 reply threads
  • Author
    Posts
    • #7942


      woutr
      Participant
      Skilled
      Post count: 10

      Since friday/saturday puppeteer ( and Tor ) can’t seem to scrape anymore. I get the error below:

      [3-Jul-2023 11:09:21 Europe/Amsterdam] An error occurred while getting content from HeadlessBrowserAPI: https://headlessbrowserapi.com/apis/scrape/v1/tor?apikey=REDACTED&url=https%3A%2F%2Fpadelalto.com%2F2023%2F07%2F03%2Fvalencia-gets-ready-to-welcome-the-world-padel-tour&custom_user_agent=default&custom_cookies=default&user_pass=default&timeout=default&proxy_url=default&proxy_auth=default – tor Unhandled Rejection [HeadlessBrowserAPI]Unhandled Rejection, reason: Error: net::ERR_TIMED_OUT at https://padelalto.com/2023/07/03/valencia-gets-ready-to-welcome-the-world-padel-tour at navigate (…/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:115:23) at process._tickCallback (internal/process/next_tick.js:68:7) …/tor.js:31 process.on(‘unhandledRejection’, up => { console.error(‘[HeadlessBrowserAPI]Unhandled Rejection, reason:’, up);throw up }) ^ Error: net::ERR_TIMED_OUT at https://padelalto.com/2023/07/03/valencia-gets-ready-to-welcome-the-world-padel-tour at navigate (…/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:115:23) at process._tickCallback (internal/process/next_tick.js:68:7)

      What could be causing this?

    • #7944


      Szabi – CodeRevolution
      Keymaster
      Post count: 4623

      Hello,

      I just checked on this and for me, the API URL you linked is working, it is returning correct HTML content now.

      Please recheck on this on your side and let me know if it worked.

      Regards,

      Szabi – CodeRevolution.

    • #7945


      woutr
      Participant
      Skilled
      Post count: 10
      This reply has been marked as private.
    • #7949


      Szabi – CodeRevolution
      Keymaster
      Post count: 4623
      This reply has been marked as private.
    • #7950


      woutr
      Participant
      Skilled
      Post count: 10

      Funny, this seems to be an other error lol. I’ve upgraded my DeepL account this morning..

      I’ll look into it

    • #7951


      woutr
      Participant
      Skilled
      Post count: 10

      It seems to get stuck on the DeepL api key, even after resetting the token it’s still telling me my quota is exceeded… Is there some api cache or something?

    • #7952


      Szabi – CodeRevolution
      Keymaster
      Post count: 4623

      No API cache on my part, I suggest you check the ‘auth_key’ parameter in the DeepL API link, it changes after you change the key in settings.

      I suggest you contact DeepL support and ask them about this issue, as it sounds like an issue on their part.

      Regards.

    • #7953


      woutr
      Participant
      Skilled
      Post count: 10

      That does work indeed. It’s on the DeepL side then. Thanks alot buddy, for now solved.

    • #7954


      Szabi – CodeRevolution
      Keymaster
      Post count: 4623

      I am glad to help!

Viewing 8 reply threads

The topic ‘Puppeteer scraping stopped working’ is closed to new replies.