Why are all my websites red the majority of the time?

[vmsman]

I am not sure why, but my websites are generally RED most of the type meaning that the scan was in error. I don't know how to drill down and find out what the errors are. I increased the "wait seconds before extracting text" to 300 thinking that maybe it takes a crazy long time for the browser to render the data. Ideas? What does RED generally mean?

[dgtlmoon]

again you are writing discussion posts and giving no real information, no screenshots, no urls, we cannot help you.

[dgtlmoon]

reduce the "wait time" 30 seconds is too long, set it to 5 seconds maximum

[vmsman]

Is this right?

[dgtlmoon]

yes and in your settings of actual watches

[vmsman]

Ok, that is actually what I had set after the initial installation. Do I assume the the red error state is the desired state and that the fact that it says "with errors (7)" is, in fact not an error at all? Note I have newly scanned checks that all turned red after your suggested change. This is how the program has behaved since installation. Is 8GB and 4 vcpu's enough resources? It doesn't appear to be using many resources.

[vmsman]

At this point all seven of the websites that I am monitoring are red as in the screenshot above. I have set all of the watch wait times to be 5 seconds as suggested. There is negligible load on the server and I am unsure if this "red" state means everything is operating optimally or not. Just to be sure, I installed another instance and I am seeing the same. Is the docker installation less recommended?

[th12289]

I have 2 vcpu and 12 GB ram. I don't have your issues. Maybe it helps to adjust the docker compose file

playwright-chrome:
    hostname: playwright-chrome
    image: browserless/chrome
    restart: unless-stopped
    environment:
        - SCREEN_WIDTH=1920
        - SCREEN_HEIGHT=1024
        - SCREEN_DEPTH=16
        - ENABLE_DEBUGGER=false
        - PREBOOT_CHROME=true
        - CONNECTION_TIMEOUT=300000
        - MAX_CONCURRENT_SESSIONS=10
        - CHROME_REFRESH_TIME=600000
        - DEFAULT_BLOCK_ADS=false # original true
        - DEFAULT_STEALTH=false # original true
        - DEFAULT_IGNORE_HTTPS_ERRORS=true

[vmsman]

@th12289 Thanks Tim. After a lot of testing the image you are using above was just not working. I changed to:

  playwright-chrome:
    hostname: playwright-chrome
    image: dgtlmoon/sockpuppetbrowser:latest
    restart: unless-stopped
    environment:
      - SCREEN_WIDTH=1920
      - SCREEN_HEIGHT=1024
      - SCREEN_DEPTH=16
      - ENABLE_DEBUGGER=false
      - PREBOOT_CHROME=true
      - CONNECTION_TIMEOUT=600000
      - MAX_CONCURRENT_SESSIONS=10
      - CHROME_REFRESH_TIME=600000
      - DEFAULT_BLOCK_ADS=true
      - DEFAULT_STEALTH=true
      - DEFAULT_IGNORE_HTTPS_ERRORS=true

I now have no timeouts and everything is working like a champ.