alexbelgium / hassio-addons

My homeassistant addons
MIT License
1.55k stars 220 forks source link

🐛 [Browserless Chrome] Addon No Longer Working (started) #1217

Closed FabioEight closed 9 months ago

FabioEight commented 9 months ago

Description

I can't get my browserless instance running, it is unresponsive. Version 2.1.0-test2 on amd64. WebGUI report the same error

image

Reproduction steps

1. Run the addons
2. Check the logs

Addon Logs

Starting...
/etc/cont-init.d/00-banner.sh: executing

-----------------------------------------------------------
 Add-on: Browserless Chrome
 Chrome as a service container
-----------------------------------------------------------
 Add-on version: 2.1.0-test2
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.4  (amd64 / qemux86-64)
 Home Assistant Core: 2024.1.5
 Home Assistant Supervisor: 2023.12.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons 
-----------------------------------------------------------
/etc/cont-init.d/00-global_var.sh: executing
Timezone set from Etc/UTC to Europe/Rome
/etc/cont-init.d/01-config_yaml.sh: executing
/etc/cont-init.d/01-custom_script.sh: executing

Starting the upstream container

Please use variable name "DATA_DIR" in place of "DEFAULT_USER_DATA_DIR"
  browserless.io:limiter Concurrency: 10 queue: 10 timeout: 30000ms +0ms
  browserless.io:index 
  browserless.io:index ---------------------------------------------------------
  browserless.io:index | browserless.io
  browserless.io:index | To read documentation and more, load in your browser:
  browserless.io:index |
  browserless.io:index | http://0.0.0.0:3000/docs
  browserless.io:index ---------------------------------------------------------
  browserless.io:index 
  browserless.io:index 
  browserless.io:index █▓▒
  browserless.io:index ████▒
  browserless.io:index ████▒
  browserless.io:index ████▒   ▒██▓▒
  browserless.io:index ████▒   ▒████
  browserless.io:index ████▒   ▒████
  browserless.io:index ████▒   ▒████
  browserless.io:index ████▒   ▒████
  browserless.io:index ████▒   ▒████
  browserless.io:index ████▒   ▒██████▓▒
  browserless.io:index ████▒   ▒██████████▒
  browserless.io:index ████▒   ▒██████▓████
  browserless.io:index ████▒   ▒█▓▓▒  ▒████
  browserless.io:index ████▒          ▒████
  browserless.io:index ████▒       ▒▓██████
  browserless.io:index ████▒   ▒▓████████▓▒
  browserless.io:index ████▓▓████████▓▒
  browserless.io:index ██████████▓▒
  browserless.io:index   ▓███▓▒
  browserless.io:index 
  browserless.io:index  +0ms
  browserless.io:index Running as user "root" +0ms
  browserless.io:index Starting import of HTTP Routes +0ms
  browserless.io:index Starting import of WebSocket Routes +50ms
  browserless.io:index Imported and validated all route files, starting up server. +4ms
  browserless.io:server Server instantiated with host "0.0.0.0" on port "3000" using token "null" +0ms
  browserless.io:server HTTP Server is starting +0ms
  browserless.io:server HTTP Server is listening on http://0.0.0.0:3000
  browserless.io:server Use http://0.0.0.0:3000 for API and connect calls +2ms
  browserless.io:index Starting metrics collection. +3ms
  browserless.io:error No handler or file found for resource / +0ms
  browserless.io:error No handler or file found for resource / +5s
  browserless.io:error No handler or file found for resource / +5s
  browserless.io:error No handler or file found for resource / +5s
  browserless.io:server No matching WebSocket route handler for "http://0.0.0.0:3000/webdriver/session?launch=%7B%7D" +20s
  browserless.io:error No handler or file found for resource / +5s
  browserless.io:error No handler or file found for resource / +5s
  browserless.io:error No handler or file found for resource / +5s

Architecture

amd64

OS

HAos, Virtual Machine

alexbelgium commented 9 months ago

Hi does the latest version work? I'm just starting the latest container from upstream so not sure what would cause the issue ...

FabioEight commented 9 months ago

Now I'm on 2.1.0-2 and it started as expected. Thank you.