Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Change Detection
  3. "BrowserType.connect_over_cdp: Timeout 60000ms exceeded" error

"BrowserType.connect_over_cdp: Timeout 60000ms exceeded" error

Scheduled Pinned Locked Moved Change Detection
13 Posts 2 Posters 116 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • jamesJ Online
    jamesJ Online
    james
    Staff
    wrote last edited by
    #2

    Hello @p44
    When I visit changedetection.io even the browser loads for almost 60000ms to load all content.

    9de75038-1c07-4d49-bf8c-02ace476c925-image.png

    So I am assuming now that this is simply an issue of the site itself being slow and truly triggering a timeout in the app.

    1 Reply Last reply
    1
    • P Offline
      P Offline
      p44
      translator
      wrote last edited by p44
      #3

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

      1 Reply Last reply
      0
      • jamesJ Online
        jamesJ Online
        james
        Staff
        wrote last edited by
        #4

        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.

        1 Reply Last reply
        1
        • P Offline
          P Offline
          p44
          translator
          wrote last edited by
          #5

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

          1 Reply Last reply
          0
          • jamesJ Online
            jamesJ Online
            james
            Staff
            wrote last edited by
            #6

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

            P 1 Reply Last reply
            0
            • jamesJ james

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

              P Offline
              P Offline
              p44
              translator
              wrote last edited by
              #7

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

              1 Reply Last reply
              0
              • P Offline
                P Offline
                p44
                translator
                wrote last edited by p44
                #8

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

                1 Reply Last reply
                0
                • jamesJ Online
                  jamesJ Online
                  james
                  Staff
                  wrote last edited by
                  #9

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

                  1 Reply Last reply
                  0
                  • P Offline
                    P Offline
                    p44
                    translator
                    wrote last edited by
                    #10

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

                    1 Reply Last reply
                    0
                    • jamesJ Online
                      jamesJ Online
                      james
                      Staff
                      wrote last edited by
                      #11

                      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:
                      a2d6bec2-5dac-49db-8adb-8f0fac7424e7-image.png

                      1 Reply Last reply
                      1
                      • P Offline
                        P Offline
                        p44
                        translator
                        wrote last edited by
                        #12

                        @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

                        jamesJ 1 Reply Last reply
                        1
                        • P 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

                          jamesJ Online
                          jamesJ Online
                          james
                          Staff
                          wrote last edited by
                          #13

                          @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.

                          1 Reply Last reply
                          2
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Bookmarks
                          • Search