• Offizieller Beitrag

    Changing the permissions of the pool might not help. Try changing the permissions of the drives in the pool

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I found the problem: a typo...


    It is better not to work on such things if it is too late in the night :whistling:


    But some question about syncthing:


    - do I need to enter my DDNS or will it get the correct IP from an "outsourced server"?
    - traffic is only about my machines?
    - will it work well with VPN?
    - How does versioning (i don't know the word in english?) work? For example if i delete something from a excelsheet, how can I recover it?
    - Is it possible to recover a deleted file after sync?

  • Hi Niemand,
    regarding the concepts and defaults of versioning and recovering deleted files see https://docs.syncthing.net/users/versioning.html

    OpenMediaVault 6.x (most recent stable version) -- 64 bit -- OMV-Extras 6.x (most recent stable version) -- Default Kernel

  • I'm confused by the discussion of how updating Syncthing works.


    It had been working well for me, but I've noticed recently that my Windows clients are complaining that my OMV version of Syncthing is too out of date.


    On my OMV, opening up Syncthing in a browser window it reports version 0.14.0, while my Windows clients are on 0.14.19.


    How do I go about updating the Syncthing version on OMV?

    • Offizieller Beitrag

    So how can I force it to update even though it doesn't see any updates as available?

    omv-extras adds the official syncthing repo. So, if you system is updating correctly, it should have the newest package available that syncthing themselves are putting in the repo. That said, the syncthing repo seems to be having issues right now. This would explain why you aren't getting a newer package. They don't have their .deb packages in the release folder on github either. So, you are kind of stuck where you are at until your machine can update.


    Edit - their https repo isn't working but the http repo. omv-extras was changed to https because I was under the impression the http repo was going away. Maybe I will switch it back to http.

  • omv-extras adds the official syncthing repo. So, if you system is updating correctly, it should have the newest package available that syncthing themselves are putting in the repo. That said, the syncthing repo seems to be having issues right now. This would explain why you aren't getting a newer package. They don't have their .deb packages in the release folder on github either. So, you are kind of stuck where you are at until your machine can update.
    Edit - their https repo isn't working but the http repo. omv-extras was changed to https because I was under the impression the http repo was going away. Maybe I will switch it back to http.

    Did you ever switch this back to http? My omv-extras updated, but I'm still not getting syncthing updates.

    • Offizieller Beitrag

    Did you ever switch this back to http?

    Yes. You can look at the repo address in the repo tab of omv-extras. What does it show?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    found my mistake. I didn't have the repo bt-sync enabled. I must've disabled it at one point when doing housekeeping, not realizing that it was the repo that syncthing is also hosted in.

    I didn't change the repo in the OMV 2.x version. So, it will still be https.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Running OMV 3.0.69 and omv-syncthing 3.9
    Few days ago, I was able to start and stop syncthing by „service syncthing stop“. But that doesn't work anymore. How is synthing started?
    Also is there a syncthing-log-file? Can't find any in /var/log.
    And the enable/disable-switch in the plugin has no effect on synchting.

    • Offizieller Beitrag

    Few days ago, I was able to start and stop syncthing by „service syncthing stop“. But that doesn't work anymore. How is synthing started?
    Also is there a syncthing-log-file? Can't find any in /var/log.
    And the enable/disable-switch in the plugin has no effect on synchting.

    The plugin switched to using systemd unit files (which is proper for Debian Jessie/OMV 3). See the changelog for 3.9.


    You can start and stop each user's syncthing instance with systemctl start syncthing@REPLACE_WITH_USERNAME.service and logs are found in syslog.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Bonjour,


    I use OMV on a RPI with syncthing and I would like to move the directory with the index to another place.
    In the manual you have to add an option -d:<Path> but where in plugin I can add an option


    Regards

    • Offizieller Beitrag

    In the manual you have to add an option -d:<Path> but where in plugin I can add an option

    That is not currently possible from the plugin since it doesn't specify start parameters. Those are in the syncthing provided systemd unit file. You could ask on the syncthing forum. Maybe a systemd override file? Maybe it can be set in the web interface?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hello,


    I use Omv3 and Syncthing 3.11


    I`m trying to set up a folder, but as screenshot say`s i have permission problem.



    Can somebody tell me at least i short steps how to do it?


    Through the forum threads some of user a talking about ACLs,but i`m not willing to do on my own,becouse in the past i messed up Omv with experimentig with ACLs.Or is another way?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!