Bronzing

Yes, thank you, that worked and did not break the detection. Finally, with the ads loaded, the browserless docker recognized the end of the page loading and the detection finishes without failures.

Greetings, thank you for your work! I really like the Browserless / Changedetection setup but recently i run into some problems: Most of my queries throw an error because they fail at the browserless "CONNECTION_TIMEOUT" limit (default 300sec / 300000ms) . Changedetection prints this as and "Last fetch time" in Stats matches the Connection Timeout limit. I also switched between some of the stable chrome releases with no success. Sometimes they succeed and some other seem to work, then the fetch time is way below 30 seconds, so it could work. But for some reason, the "load" never finishes successfully. Two example pages: https://www.rebuy.de/i,12937/nintendo-game-boy-advance/pokmon-smaragd-edition https://store.analogue.co/ Do you have any idea, what could be wrong with my setup? Browserless and Changedetection are in the same subnet, container settings are on default (besides the ws://172.20.0.3:3000/?stealth=1&--disable-web-security=true url) and some of the checks are working fine and some do from time to time and some of them always fail. I think there is something happening on the browserless side that prevents to signal that the page load has been finished successfully.