Such services are started via systemd, so you can customize the unit file to your needs, see
Beiträge von votdev
-
-
Which browser are you using? Try to refresh your browser cache.
-
Does that mean, you could copy the config.xml and then run omv-mkconf for each service and you are done?
Sadly not. The config is generated, but the service is not started or stopped based on the config. You need to do that manually. And again, in OMV5 this will be one command: 'omv-salt stage run deploy' :-). But it takes some time until OMV5 is done. But this shows me i'm on the right way.
-
OMV does not support the import/export of config settings. But if you use the config file of the same OMV version you could simply copy the /etc/openmediavault/config.xml file. Note that no servive is started/stopped or service configuration is generated automatically. You have to do that all manually (that feature comes with OMV5).
-
OMV only supports the version that is shipped with the Debian system it is based on. You can check that version on https://packages.debian.org. For OMV4 you can check it here: https://packages.debian.org/stretch/python3
-
It seems you're the only one having this problem. I do not have any more ideas how this could happen, i can't reproduce this. I think you have to reinstall to fix it.
-
Please write in english.
-
How did you have installed your system? ISO or image or manually?
-
Schau Dir mal das folgende Plugin an: https://github.com/OpenMediaVa…penmediavault-remoteshare
-
Does this mean OMV 3 globally does not work with SSL anymore?
This is possible. I can't confirm that because this version is not tested or maintained anymore because it is EOL since 9 july 2018.
-
The problem seems that the SSL ciphers configuration in nginx is not correct anymore or does not match with the requirements of the latest web browsers.
You may give this a try:Because i do not have a running OMV3 system anymore we need to find out which nginx and openssl versions are used there:
https://packages.debian.org/jessie/openssl
https://packages.debian.org/jessie/nginxWith this info we can generate the suggested ciphers config: https://mozilla.github.io/serv…t&hsts=yes&profile=modern
Now open /etc/default/openmediavault and add the following line
CodeOMV_NGINX_SITE_WEBGUI_SSL_CIPHERS="ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256"
Now rebuild the config and restart nginx
Please consider to upgrade your system. Debian nor OMV will provide security updates for this systems anymore. -
-
The read only file system message is really important because this means no files can be created. Can you post the output?
-
-
Welches Dateisystem verwendest Du?
-
Try to install the package php-bcmath which should be installed by the package manager automatically because it is a dependency of the openmediavault package.
-
Sorry, can't reproduce this error and it seems you're the only one having this issue. The problem is that based on your information all files are copied to the correct directories during the package update, so i'm really out of ideas what happens here.
The last idea coming into mind is this:
-
-
If you are using rsync then make sure that no data has been copied to the root filesystem. This is the main error that happens to most users. This has sometimes multiple reasons, e.g. if the target shared folder or the volume which contains this folder is not mounted.
-
The working one is done by OMV via Avahi, but i don't know where and how the second one is created.