13
submitted 4 months ago* (last edited 4 months ago) by Xirup@yiffit.net to c/selfhosted@lemmy.world

I used Docker Compose to install and run changedetection.io and everything's working nice, but I want to enable Playwright content fetcher so I can specify when I want to be notified, and not just to be notified when there are even changes in the code of the site.

I can toggle an option in the changedetection settings to use WebDriver Chrome/Javascript instead of the default Basic fast Plaintext/HTTP Client, but when I tried to use the Visual Filter Selection within a watched item it tells me that:

Sorry, this functionality only works with Playwright/Chrome enabled watches. Enable the Playwright Chrome fetcher, or alternatively try our very affordable subscription based service. This is because Selenium/WebDriver can not extract full page screenshots reliably.

And honestly I want to try this to myself, not to just pay a subscription and that's it. So, I keep up and read through their wiki and according to their own wiki while using a docker compose based Change Detection service (as I am) to enable Playwright content fetcher it's as simple as:

In docker-compose.yml uncomment PLAYWRIGHT_DRIVER_URL under environment, and the playwright-chrome section under services.

I already tried that and toggle the fetching method to WebDriver Chrome/Javascript, but now instead of just not letting me using the Visual Filter Selection because of while trying to fetch any site it gives me this error:

Exception: HTTPConnectionPool(host='browser-chrome', port=4444): Max retries exceeded with url: /wd/hub/session (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fa4d42417e0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

But before of doing these changes I didn't receive any error message and everything works nice, so possibly I'm doing something wrong... Here is the pastebin of the docker-compose file that I edited, I won't share it here because the format fucked the whole code.

top 7 comments
sorted by: hot top controversial new old
[-] just_another_person@lemmy.world 1 points 4 months ago

The chrome instance is commented out...

[-] Xirup@yiffit.net 1 points 4 months ago

Ups, you're right although I think I had already uncommented it without success, in a couple of hours I'll let you know if that solves it.

[-] Xirup@yiffit.net 1 points 4 months ago

I tried to uncomment it and now I get this message when I try to start the service:

service "changedetection" refers to undefined volume WEBDRIVER_URL=http: invalid compose project

[-] Hansie211@lemmy.world 1 points 4 months ago

Did you ever find a solution? I'm on mobile, and the Pastebin formatting is a bit off, so I can't read the compose file very well. However, I suspect the error is related to this line:

24 # - WEBDRIVER_URL=http://browser-chrome:4444/wd/hub

Since a colon (':') is used to indicate a volume, it makes sense that the error is about a missing volume. Try wrapping the line in double quotes like this:

24 # - "WEBDRIVER_URL=http://browser-chrome:4444/wd/hub"

to see if that fixes the error.

[-] just_another_person@lemmy.world 0 points 4 months ago* (last edited 4 months ago)

Bud, if you don't know how to read and understand your own logs, I can't step through this entire thing with you. It's literally telling you exactly what is wrong.

[-] Xirup@yiffit.net 1 points 4 months ago

Sorry, I just started selfhosting and even reading that I don't understand.

[-] just_another_person@lemmy.world 2 points 4 months ago* (last edited 4 months ago)

Search for the word "changedetection" in your compose file, then find out why it thinks you have a volume named WEB_DRIVER

I'd assume your formatting is off.

this post was submitted on 30 Jun 2024
13 points (93.3% liked)

Selfhosted

40330 readers
353 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS