UI will not load, always in loading state, unable to configure or navigate

[ropelletier]

Describe the bug
UI just spins and spins and does not load. Seems better in safari than chrome, but even then I can click on Settings and then if I click Groups it just refuses to load again. I have tried three different servers, therefore it is not an issue with the hardware. Frankly, it is painful and impossible to use. I can't even delete the two sample websites in the install.

Version
0.45.3

To Reproduce

Steps to reproduce the behavior:
Any navigation of UI

! ALWAYS INCLUDE AN EXAMPLE URL WHERE IT IS POSSIBLE TO RE-CREATE THE ISSUE - USE THE 'SHARE WATCH' FEATURE AND PASTE IN THE SHARE-LINK!

Expected behavior
Be able do some simple configuration and setup.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Mac Venture
• Browser: Chrome / Safari
• Version: 118.0.5993.88. / 16.6

Here is my docker-compose file. Tried with and without webdriver

version: '3.2'
services:
    changedetection:
      image: ghcr.io/dgtlmoon/changedetection.io
      container_name: changedetection
      hostname: changedetection

      environment:
        - WEBDRIVER_URL=http://browser-chrome:4444/wd/hub
        - FETCH_WORKERS=10  
      depends_on:
        browser-chrome:
            condition: service_started
      volumes:
        - ./data:/datastore
      ports:
        - 5009:5000
      restart: unless-stopped
    browser-chrome:
        hostname: browser-chrome
        image: selenium/standalone-chrome-debug:3.141.59
        environment:
            - VNC_NO_PASSWORD=1
            - SCREEN_WIDTH=1920
            - SCREEN_HEIGHT=1080
            - SCREEN_DEPTH=24
        volumes:
            # Workaround to avoid the browser crashing inside a docker container
            # See https://github.com/SeleniumHQ/docker-selenium#quick-start
            - /dev/shm:/dev/shm
        restart: unless-stopped

[dgtlmoon]

Hey yes - #1830 this is why

[ropelletier]

I had read that discussion before I submitted the bug. If I am understanding correctly, are you saying there is no fix to this? And furthermore, that there is nothing in my config that can be changed to mitigate the issue or work-around?