Static files remain on pending in browser.

[1337cookie]

I'm using docker-compose method from the latest commit a4e6fd1 docker-compose.yml states version: '3.2'. This is running on Ubuntu 22.04.1 LTS
When I load the frontend I get some static files stuck on pending for a long time or indefinitely.

Here's what I see in the docker logs:

changedetection    | Saving JSON..
changedetection    | System env MINIMUM_SECONDS_RECHECK_TIME 20
changedetection    | USE_X_SETTINGS is ENABLED
changedetection    |
changedetection    | (7) wsgi starting up on http://0.0.0.0:5000
changedetection    | (7) accepted ('192.168.191.57', 53902)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:07:52] "GET /preview/40c37be8-bdd7-4a50-a452-4e60a58fb373 HTTP/1.1" 200 5625 0.046519
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:07:52] "GET /static/styles/pure-min.css HTTP/1.1" 304 274 0.002282
changedetection    | (7) accepted ('192.168.191.57', 53905)
changedetection    | (7) accepted ('192.168.191.57', 53906)
changedetection    | (7) accepted ('192.168.191.57', 53907)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:07:52] "GET /static/styles/styles.css HTTP/1.1" 304 272 0.001645
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:07:52] "GET /static/styles/diff.css?ver=1000 HTTP/1.1" 304 270 0.001420
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:07:52] "GET /static/js/jquery-3.6.0.min.js HTTP/1.1" 304 281 0.001431
changedetection    | (7) accepted ('192.168.191.57', 53922)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET / HTTP/1.1" 200 6537 0.117243
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/styles/pure-min.css HTTP/1.1" 304 274 0.001619
changedetection    | (7) accepted ('192.168.191.57', 53923)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/styles/styles.css HTTP/1.1" 304 272 0.001860
changedetection    | (7) accepted ('192.168.191.57', 53924)
changedetection    | (7) accepted ('192.168.191.57', 53925)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/js/jquery-3.6.0.min.js HTTP/1.1" 304 281 0.001670
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/images/spread-white.svg HTTP/1.1" 200 1238 0.001639
changedetection    | (7) accepted ('192.168.191.57', 53926)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/images/gradient-border.png HTTP/1.1" 200 22322 0.001793
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/images/pause.svg HTTP/1.1" 304 271 0.001921
changedetection    | (7) accepted ('192.168.191.57', 53927)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/images/Generic_Feed-icon.svg HTTP/1.1" 304 283 0.001925
changedetection    | (7) accepted ('192.168.191.57', 53928)
changedetection    | 192.168.191.57 - - [01/Jun/2023 08:08:00] "GET /static/images/Google-Chrome-icon.png HTTP/1.1" 304 284 0.001933

and here's the browser docker log:

browser-chrome_1   | Starting ChromeDriver 94.0.4606.61 (418b78f5838ed0b1c69bb4e51ea0252171854915-refs/branch-heads/4606@{#1204}) on port 17234
browser-chrome_1   | Only local connections are allowed.
browser-chrome_1   | Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
browser-chrome_1   | ChromeDriver was started successfully.
browser-chrome_1   | [1685606580.670][SEVERE]: bind() failed: Cannot assign requested address (99)
browser-chrome_1   | 08:03:00.912 INFO [ProtocolHandshake.createSession] - Detected dialect: W3C
browser-chrome_1   | 08:03:00.914 INFO [RemoteSession$Factory.lambda$performHandshake$0] - Started new session d253f24e425406367d054d2cbd915d77 (org.openqa.selenium.chrome.ChromeDriverService)
browser-chrome_1   | 08:03:08.164 INFO [ActiveSessions$1.onStop] - Removing session d253f24e425406367d054d2cbd915d77 (org.openqa.selenium.chrome.ChromeDriverService)
browser-chrome_1   | 2023-06-01 08:05:51,612 INFO Included extra file "/etc/supervisor/conf.d/selenium-debug.conf" during parsing
browser-chrome_1   | 2023-06-01 08:05:51,612 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
browser-chrome_1   | 2023-06-01 08:05:51,614 INFO supervisord started with pid 8
browser-chrome_1   | 2023-06-01 08:05:52,617 INFO spawned: 'xvfb' with pid 10
browser-chrome_1   | 2023-06-01 08:05:52,618 INFO spawned: 'fluxbox' with pid 11
browser-chrome_1   | 2023-06-01 08:05:52,620 INFO spawned: 'vnc' with pid 12
browser-chrome_1   | 2023-06-01 08:05:52,621 INFO spawned: 'selenium-standalone' with pid 13
browser-chrome_1   | 2023-06-01 08:05:52,629 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:05:52,630 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:05:52,630 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:05:52,631 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:05:52,633 INFO exited: fluxbox (exit status 1; not expected)
browser-chrome_1   | 08:05:52.819 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
browser-chrome_1   | 2023-06-01 08:05:52,821 INFO spawned: 'fluxbox' with pid 48
browser-chrome_1   | 2023-06-01 08:05:52,833 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 08:05:52.906 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444
browser-chrome_1   | 2023-06-01 08:05:52.946:INFO::main: Logging initialized @312ms to org.seleniumhq.jetty9.util.log.StdErrLog
browser-chrome_1   | 08:05:53.161 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
browser-chrome_1   | 08:05:53.239 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
browser-chrome_1   | Trapped SIGTERM/SIGINT/x so shutting down supervisord...
browser-chrome_1   | 2023-06-01 08:07:01,757 WARN received SIGTERM indicating exit request
browser-chrome_1   | 2023-06-01 08:07:01,757 INFO waiting for xvfb, fluxbox, vnc, selenium-standalone to die
browser-chrome_1   | 2023-06-01 08:07:02,759 INFO stopped: selenium-standalone (terminated by SIGTERM)
browser-chrome_1   | 2023-06-01 08:07:03,761 INFO stopped: vnc (terminated by SIGTERM)
browser-chrome_1   | 2023-06-01 08:07:04,763 INFO stopped: fluxbox (terminated by SIGTERM)
browser-chrome_1   | 2023-06-01 08:07:04,763 INFO waiting for xvfb to die
browser-chrome_1   | 2023-06-01 08:07:05,765 INFO stopped: xvfb (terminated by SIGTERM)
browser-chrome_1   | Shutdown complete
browser-chrome_1   | 2023-06-01 08:07:34,407 INFO Included extra file "/etc/supervisor/conf.d/selenium-debug.conf" during parsing
browser-chrome_1   | 2023-06-01 08:07:34,408 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
browser-chrome_1   | 2023-06-01 08:07:34,409 INFO supervisord started with pid 8
browser-chrome_1   | 2023-06-01 08:07:35,412 INFO spawned: 'xvfb' with pid 10
browser-chrome_1   | 2023-06-01 08:07:35,413 INFO spawned: 'fluxbox' with pid 11
browser-chrome_1   | 2023-06-01 08:07:35,414 INFO spawned: 'vnc' with pid 12
browser-chrome_1   | 2023-06-01 08:07:35,415 INFO spawned: 'selenium-standalone' with pid 13
browser-chrome_1   | 2023-06-01 08:07:35,423 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:07:35,423 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:07:35,423 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:07:35,424 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 2023-06-01 08:07:35,425 INFO exited: fluxbox (exit status 1; not expected)
browser-chrome_1   | 08:07:35.608 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
browser-chrome_1   | 2023-06-01 08:07:35,610 INFO spawned: 'fluxbox' with pid 48
browser-chrome_1   | 2023-06-01 08:07:35,630 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
browser-chrome_1   | 08:07:35.678 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444
browser-chrome_1   | 2023-06-01 08:07:35.722:INFO::main: Logging initialized @296ms to org.seleniumhq.jetty9.util.log.StdErrLog
browser-chrome_1   | 08:07:35.944 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
browser-chrome_1   | 08:07:36.015 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444
browser-chrome_1   | 08:13:09.068 INFO [ActiveSessionFactory.apply] - Capabilities are: {
browser-chrome_1   |   "browserName": "chrome"
browser-chrome_1   | }
browser-chrome_1   | 08:13:09.069 INFO [ActiveSessionFactory.lambda$apply$11] - Matched factory org.openqa.selenium.grid.session.remote.ServicedSession$Factory (provider: org.openqa.selenium.chrome.ChromeDriverService)
browser-chrome_1   | Starting ChromeDriver 94.0.4606.61 (418b78f5838ed0b1c69bb4e51ea0252171854915-refs/branch-heads/4606@{#1204}) on port 10433
browser-chrome_1   | Only local connections are allowed.
browser-chrome_1   | Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
browser-chrome_1   | [1685607189.089][SEVERE]: biCnhdr(o)m efDariilveedr:  wCaasn nsotta ratsesdi gsnu crceeqsusefsutleldy .a
browser-chrome_1   | ddress (99)
browser-chrome_1   | 08:13:09.596 INFO [ProtocolHandshake.createSession] - Detected dialect: W3C
browser-chrome_1   | 08:13:09.616 INFO [RemoteSession$Factory.lambda$performHandshake$0] - Started new session 94c5118890fcf06536a0e814113f1caa (org.openqa.selenium.chrome.ChromeDriverService)
browser-chrome_1   | 08:13:57.895 INFO [ActiveSessions$1.onStop] - Removing session 94c5118890fcf06536a0e814113f1caa (org.openqa.selenium.chrome.ChromeDriverService)

Pages on the frontend often don't load, text previews are available and screenshots have never loaded.

I'm looking for advice on what I should try next, diagnostic or setup wise.

Thanks for reading :) 🍪

[dgtlmoon]

You dont give any version info, no information about your setup OS, etc etc

also

"browser-chrome_1 | [1685606580.670][SEVERE]: bind() failed: Cannot assign requested address (99)"

[1337cookie]

I've updated my post with some version details as below.
This was from the latest commit a4e6fd1 running docker-compose, the docker-compose.yml file states version: '3.2'.
This is running on Ubuntu 22.04.1 LTS.

I entered sh in the chrome browser container and ran chromedriver --verbose with the following output:

chromedriver --verbose
Starting ChromeDriver 94.0.4606.61 (418b78f5838ed0b1c69bb4e51ea0252171854915-refs/branch-heads/4606@{#1204}) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
[1685613684.409][SEVERE]: bind() failed: Cannot assign requested address (99)
[1685613684.409][INFO]: listen on IPv6 failed with error ERR_ADDRESS_INVALID
ChromeDriver was started successfully.

Which shouldn't be an issue since I assume we're using IPv4. changedetection.io also successfully scrapes text from pages in WebDriver mode.

[cloudcloudskies]

Can you send me your Discord, cookie?