saarg

It says connection refused, so your database doesn't let snipe-it connect.

I have checked it here now and running the container with privileged mode, you shouldn't need to add any disks for device pass through. But you have to run the scrutiny-collector-metrics run command if you want to see the data after installation or you have to wait until midnight when the cron job runs. The container is made to be either Web service, metrics collector or both. The default is both and you do not change the API endpoint then. That is only needed if you use this container as a remote collector.

You can start with supplying the docker run command and where the calibre database is located. How to get the dokcer run command is in the docker faq.

Thanks for reporting it.

You need to give the right permission to the snipe-it user in the database. You probably didn't allow any access outside the database container.

Why are you changing the variable? It refers to inside the container and mapping the port to something else on the host side does not effect that setting. The container can be run as a collector or a webgui or both. For most people the default settings running both collector and webgui is fine.

Post your docker run command and container log.

Since we don't bundle any Nvidia drivers in the container, it's plex that is the cause of this I would think. You should report it to plex.

Since it worked after you edited the config file, the settings are good and it should work when your actual IP change some time in the future.

I haven't tried it myself, but might be you have to use an email address. Also don't use a too short password in case it needs a minimum of characters.

Your IP have not changed, so there is nothing for ddclient to do. ddclient only updates namecheap if your IP changes. It's working as it should.

The IP shouldn't change every 5 minutes. It checks if the IP is changed at a set interval that you can customize in the config file. Ddclient doesn't write timestamps to its log, so not much we can do about that.

Which XML file are you talking about? There are variables in the template to set up the superuser. Try to not use any special characters in case unraid have an issue passing those to the run command.

You have added the IP in the wrong place in the proxy-conf. Don't change the resolver, change the upstream app variable to the IP. If you would have used a custom docker bridge this would have been avoided. Then there are minimal things you need to change.

Then it's a reverse proxy issue. Post the docker run command of bothe swag and calibre-web. You need to use a custom docker network bridge if you want to take advantage of using the container names for communication.

Did you check if you can access calibre-web locally? If that doesn't work, this issue should be in the calibre-web thread instead.

That was my bad. It's fixed now.

Our container is not deprecated.

I have it set to the below in the default file of nextcloud. Which is the default value. That is the only place I have it.

As far as I know Pydio is not deprecated.

This is a speedtest server that is selfhosted and is used to test the connection between the user accessing the server and the server.

That is crucial information to add As for fixing the database I don't have any suggestions.

502 means swag can't connect to the container. Are they in the same docker network?

What exactly is needed in your opinion? Telemetry isn't anything we added, so you have to talk to the librespeed devs about that one.

That is a normal message and not an error.