"BrowserType.connect_over_cdp: Timeout 60000ms exceeded" error

[p44]

@james is going to be happen to about 1/3 of checked websites... I don't think is nornal... Never had this issue before...

[james]

Hello @p44

@p44 said in "BrowserType.connect_over_cdp: Timeout 60000ms exceeded" error:

Never had this issue before...

I've also created a setup and was running it since my last post.
I had zero failures for 23 web pages.

[p44]

Very strange, could be a resource allocation issue? @james

[james]

Hello @p44
Could be but could also be some sites throttling this specific agent after some time.

[p44]

@james Ok thanks a lot ... or maybe some broken update... I should open a ticket on their GitHub area

[p44]

@james Some other user opened an issue: https://github.com/dgtlmoon/changedetection.io/discussions/2593 Please have a look. Thanks

[james]

@p44
This person had a solution for himself => https://github.com/dgtlmoon/changedetection.io/discussions/2593#discussioncomment-13567391
Might be also helpful to you.

[p44]

@james thanks, what is the standard value for FETCH_WORKERS in Cloudron?

[james]

It seems Cloudron sticks to the default:

https://github.com/dgtlmoon/changedetection.io/blob/58e2a41c9558a242e732320af4ab0b0ae6efe326/changedetectionio/realtime/README.md?plain=1#L107

| `FETCH_WORKERS` | `10` | Number of async workers for watch processing |

Also there is this line:
https://github.com/dgtlmoon/changedetection.io/blob/58e2a41c9558a242e732320af4ab0b0ae6efe326/changedetectionio/flask_app.py#L596

    # Start the async workers during app initialization
    # Can be overridden by ENV or use the default settings
    n_workers = int(os.getenv("FETCH_WORKERS", datastore.data['settings']['requests']['workers']))

Which is also confirmed by the web ui:

[p44]

@james Thanks. I changed value to "2" on the web UI, let see what will happen.

Thanks a lot for your patience and your support, James

[james]

@p44 said in "BrowserType.connect_over_cdp: Timeout 60000ms exceeded" error:

Thanks a lot for your patience and your support, James

No worries! That's what I'm here for.
Also, don't thank me yet, the issue is not resolved yet.