Change Detection LXC Installs but Browserless service cannot start #2262
Replies: 2 comments 5 replies
-
My primary focus revolves around the development of application LXCs, and I'm not specialized in providing support for operational issues that may arise with these applications. Admittedly, I know nothing about how this application works, never used it. It suggests that the browserless service is encountering an error when trying to load the specified route "/content" because it can't find the required browser ("CDPChromium"). I'm going to send this issue to Discussions. Hopefully someone will advise with a solution. The browserless service is running.
|
Beta Was this translation helpful? Give feedback.
-
Hi the problem is they have recently released a new major version of Browserless. Install the old version instead. For an existing install, just run this: Then restart the browserless service with service browserless restart. It works now |
Beta Was this translation helpful? Give feedback.
-
Please verify that you have read and understood the guidelines.
yes
A clear and concise description of the issue.
After an update, my change detection lxc stopped working for all watches that used the Playwright fetch method. I erased the container and started over. When I run
I see:
I installed the browsers manually with
and then I can manually start browerless with the start.sh script in opt/browserless and then changedetection and the watches that rely on the playwright work as they should.
However, even though after the browsers are installed and I can manually start browserless, the service reports the same error on start.
Which Linux distribution are you employing?
Debian 12
If relevant, including screenshots or a code block can be helpful in clarifying the issue.
No response
Please provide detailed steps to reproduce the issue.
Use install script from website:
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/changedetection.sh)"
Setup a new watch with the the playwright fetch method and you should always see this error:
"WebSocket error: connect ECONNREFUSED 127.0.0.1:3000 "
then if you check the browserless service, you should see what I recorded above.
Beta Was this translation helpful? Give feedback.
All reactions