Djoss

Are you using the nouveau driver on the host ? Only open source drivers are supported: https://github.com/jlesage/docker-firefox#gpu-acceleration-support

Sorry for not coming back on this: this was added in version 26.05.1. There is a new variable "QDIRSTAT_STARTUP_SCAN_FOLDER" that can be used to specify a directory to scan on startup.

This should be fixed with the latest image.

I will soon release a new version of the image supporting this.

This container also has a language option: https://github.com/jlesage/docker-qdirstat#environment-variables But if the dockerized application (i.e. QDirStat) doesn't have any translations, it won't help.

To my knowledge, QDirStat doesn't support an automatic scan on start. Same thing for other languages. Maybe these are something you can ask on https://github.com/shundhammer/qdirstat

Unfortunately the messages in red are not indicating any problems.

Please check with the latest image to see if it's better. If not, I would suggest that you open a case with the CrashPlan support team.

The message is confusing, but it doesn't tell that it failed to write to log file. Instead, an error occurred and because of that debug has been saved to the log file.

Did you check letsencrypt.log to get more details about the failure?

Please verify that the problem is fixed with the latest version.

@wmcneil the connection seems to be terminated by your upstream at 10.55.83.191. Get you can more details on the upstream ? Also, does Cloudflare give more details about the problem ?

Can you share the config of the host ? What kind of cert it used ? Letsencrypt or a custom Cloudflare cert ? Can you share the full log (docker logs NginxProxyManager)? Can you also check the nginx log associated to the host ?

What do you see in service.log.0, engine_error.log and engine_output.log?

So it's working with 7.2.3 but not with 7.2.4 ?

Is the container crashing (i.e. restarting) or you just get disconnected from the UI ?

This container will use a VPN if it is placed in a VPN network, so basically VPN functionality is provided by another container. You can look at gluetun, which is a popular option.

The errors you are seeing should not prevent the UI from being displayed. Did you try with another browser, or in an incognito/private window ? You can also try to disable the privileged mode.

Does the problem appeared after a container image update ? Can you share the output of the following commands: docker logs QDirStat docker inspect QDirStat (remove any password from the output if you configured some)

How the problem started ?

The container now has builtin support for dark mode. You should see a field in your container settings for that. If not, just add the variable DARK_MODE with value “1”.

This container is based on Alpine Linux. Currently, 145.0 is the latest version available from the latest Alpine Linux stable repo: https://pkgs.alpinelinux.org/packages?name=firefox&branch=v3.23&repo=&arch=x86_64&origin=&flagged=&maintainer=

So is the engine failure caused by the same problem seen in /config/log/service.log.0 ?

This might be caused by an issue on the host. Did you try to reboot the server ?

You want to install the docker container without internet ?