Posts by nasty_vibrations

    I did the recommended backup via clonezilla --> worked very well including testing of the image
    Did the upgrade --> worked well
    First thing I encountered was the MySQL Database could not be accessed. After resetting the root/omvadmin password this worked as well. Actually, I don´t really know what happened exactly or what made it work in the end.
    I also had the "rrdcached plugin could not connect to..." error in syslog. After enabling and disabling the Monitoring this error disappeared.

    So far, I'm really happy with the upgrade.

    Hello everybody,

    I am considering an upgrade of my omv 3.0.96 to omv 4, Debian 8 to Debian 9.

    I´ve got the following plugins installed:

    • ClamAV
    • Backup
    • Apple Filing
    • Docker (CE-Repo)
    • Fail2Ban
    • LetsEncrypt
    • MySQL

      • Debian 9 has MariaDB as default. Will the upgrade result in a smooth transition from MySQL to MariaDB?
    • Nginx
    • RSnapshot
    • FlashMemory

    I believe the Fail2Ban plugin hasn't been ported to omv4 yet, so I'll have to uninstall it. LetsEncrypt, MySQL, Nginx and FlashMemory are really important for me.
    Emby is installed via custom repository. Do I have to change the repo from Debian8 to Debian9 before or after upgrading omv?

    Will it be safe for me to upgrade?

    And another very important question: How do I upgrade? Simply execute "omv-release-upgrade"? Will this command also upgrade the OS from jessie to stretch? Do I first have to change sources from jessie to stretch and Upgrade the OS?

    Thank you all for you help. Much appreciated.

    Hello everybody,

    there is something weird going on with my firewall.
    I've got several servers set up to the public internet and from time to time (pretty much regularly) I'm not able to reach any of them. I also set up the firewall to be as safe as possible.
    Now the mysterious part is: as soon as I make any trivial change to the settings and immediately revert it (so that changes are written to the config file) I can reach my server again.
    So, I end up changing the position (or anything else) of my rules, change it back, safe again: I'm back up.
    What the hell is this?? I'm really getting tired of doing this.

    Here are my rules:

    Hello everybody,

    I just ran into an issue when creating a shared folder including a subfolder, i.e. in the shared folder dialog I put in the path "folder/subfolder" at once. After assigning privileges to my user account and adding this to my samba shares I was not able to connect with an external client. So I checked the folder permissions and "folder" was owned by root:root, whereas "subfolder" was owned by root:users (the correct setting, I guess). I circumvented this by first creating a (single) shared folder "folder" and deleted the share again. Now the ownership for "folder" were root:users. Then I created the shared (sub-)folder "subfolder" by putting "folder/subfolder" in the shared folder dialog. Voila, now I can connect.

    This seems to me like a bug. I remember creating this kind of folder/subfolder setup in one step before (for my Time Machine backups) and it was working correctly.

    Is anybody able to reproduce this?

    Thanks a lot.

    What about a native installation? Docker seems to further complicate stuff as I don´t have a clue about docker and how to pass things through etc...

    Hello everybody,

    I am very interested in Kolab and would really like to install it on my (very well running) omv3 machine. However, Kolab ships with apache as the standard webserver. So I'm a little afraid of the installation as it might break my present installation due to conflicts between apache and nginx.
    Is there anybody here who managed to install Kolab successfully and might give me some guidance? Or is it a bad idea in general to install Kolab?


    Seafile installation was successful. I changed port of omv to 81. Everything seems to be working.

    Just one thing, if I try to run the "omv-letsencrypt" command via scheduled jobs I get the following error message:
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; export SHELL=/bin/sh; sudo --shell --non-interactive --user=root -- omv-letsencrypt 2>&1': [b]Existing certificate uuid is invalid[/b] Use the Generate Certificate button in the plugin view at least once before using this script.
    Any idea why my certificate uuid is invalid?


    Thanks for your answers @luxflow,

    anyone can access your seafile regardless of your listening port(80,81..82)

    I'm not quite sure if I understand you correctly. I have a public IP, yes. My ISP doesn't block my port 80. At the moment my router is set to forward incoming requests on port 80 to port 80 of my omv-installation. And I assume that's the prerequisit for getting a valid lets-encrypt certificate. But if I disable this port-forwarding-rule no one can access my server. At least that's my understanding.
    And currently this is also my problem. Because omv is also running on port 80 I am now able to access my omv-installation via internet, which is what I want to disable!

    why are you blocking 80 port?

    I am not blocking port 80, at the moment it is open. It's just that I don't want my omv to be reachable via internet, i.e. I would disable the port forwarding to port 80 completely, but then I couldn't certificate (once each 3 months).

    if I were you, I only open /.well-know/acme-challenge for 80 port
    and make anything else redirect to 443(https)

    That's what my plan is, and I actually have already set the servers in nginx plugin this way (see my first post, the two spoilers).

    Ok, so right now seafile isn't installed at all, but the server-settings in the plugin are already activated. If I now go to xxx.mydomain.tld I land on my omv login screen. That's what I don't want. So, the only way that came into my mind, was to change the port of omv, so that it isn't running on port 80 anymore.

    I hope you guys get what I want.

    Thanks a lot for your help.