Share Link not working when using Docker image on a user defined bridge network

[BryanWall]

I am running the v0.40.1.1 Docker image. I had an issue with a Price check that I was going to report as an issue, but when I tried to use the share link feature I got the following error.

Could not share, something went wrong while communicating with the share server - HTTPSConnectionPool(host='changedetection.io', port=443): Max retries exceeded with url: /share/share (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x14d7964c7790>: Failed to establish a new connection: [Errno 111] Connection refused'))

When I switch the container network back to the default bridge (rather than a user-defined bridge) the share feature works. I originally put it on a user-defined bridge to get Playwright to work. ChangeDetection and Playwright are on their own custom bridge so they can communicate with each other. I'm not sure if there's a way to make Playwright work on the default bridge. It has been a while since I configured everything this way. Is anyone else running with this type of configuration?

Is there another way I can configure the Docker network and have Playwright continue to work? I am running Docker on Unraid but that doesn't usually behave any differently than standard Docker on Linux, since it is just standard Docker.

[dgtlmoon]

aaah you must have the old docker-compose.yml that had hostname: changedetection.io... it's probably trying to connect to itself.. try removing that line?

[BryanWall]

I tried completely deleting the container and re-creating it but the issue persists. I don't think Unraid uses Docker compose and instead pulls from Docker hub using a template that someone has to maintain like this one for changedetetion.io:

https://github.com/A75G/docker-templates/blob/master/templates/changedetection.io.xml

I don't see anything referring to hostname in the XML so it seems to be pulling the config from your dockerhub repository, but I admittedly don't know how these templates work.

I'm going to ask for suggestions on the Unraid community forums, but let me know if you see any obvious problem with this.

[masterwishx]

aaah you must have the old docker-compose.yml that had hostname: changedetection.io... it's probably trying to connect to itself.. try removing that line?

We dont set hostname in Unraid we use variables and ENV for docker ...

[masterwishx]

@BryanWall did you fixed it ? i also having this problem in Unraid

[masterwishx]

Fixed by changed container name to 'changedetection' from 'changedetection.io'
but not sure if https://changedetection.io/share.... or our base URL should be in the link host ...

[BryanWall]

Fixed by changed container name to 'changedetection' from 'changedetection.io' but not sure if https://changedetection.io/share.... or our base URL should be in the link host ...

This does seem to work around the issue. I'm not sure if this is the real fix or just an accidental workaround, though.

[dgtlmoon]

@BryanWall i can confirm that this is the fix.. its similar to the old issue i mentioned where changedetection.io as a hostname was in the docker-compose.yml