omv-update fails - Failed to fetch http://apt.syncthing.net

    • OMV 2.x
    • Update

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • omv-update fails - Failed to fetch http://apt.syncthing.net

      omv-update fails with the following error.


      Source Code

      1. W: Failed to fetch http://apt.syncthing.net/dists/syncthing/release/binary-amd64/Packages 301 Moved Permanently
      2. E: Some index files failed to download. They have been ignored, or old ones used instead.
      Any help?

      Cheers.
      If you could just go ahead and make a plugin for it, that'd be great.
      N54L/4GB/12TB
    • It isn't the syncthing plugin causing it. It is the repo that omv-extras adds. Syncthing changed their repo from http to https. If you go to it in a browser it works because it redirects to http. But apt doesn't follow the redirect. I fixed omv-extras yesterday. So, disable btsync/sync repo and update omv-extras. This will fix it.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      It isn't the syncthing plugin causing it. It is the repo that omv-extras adds. Syncthing changed their repo from http to https. If you go to it in a browser it works because it redirects to http. But apt doesn't follow the redirect. I fixed omv-extras yesterday. So, disable btsync/sync repo and update omv-extras. This will fix it.
      This post is back from 2016... I am experiencing the same error today.

      Err apt.syncthing.net syncthing/release amd64 Packages 301 Moved Permanently
      ...
      W: Failed to fetch apt.syncthing.net/dists/syncth…ase/binary-amd64/Packages 301 Moved Permanently
      E: Some index files failed to download. They have been ignored, or old ones used instead.
    • z0rk wrote:

      This post is back from 2016... I am experiencing the same error today.
      On what version of OMV? Did you follow my directions in the post you quoted?
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • same prob for me since 3 days

      i am on omv 2

      i switched of sync repo everything was fine without no errors (and no updates)
      swithed in on again and the mistake was there again.

      the message is:

      Failed to execute command 'export LANG=C; apt-get update 2>&1': Ign file: Release.gpgIgn file: ReleaseIgn file: Translation-enIgn file: Translation-de_DEIgn file: Translation-deHit dh2k.omv-extras.org virtualbox-wheezy-mirror Release.gpgHit download.mono-project.com wheezy Release.gpgHit packages.openmediavault.org stoneburner

      The post was edited 1 time, last by joker_75 ().

    • ryecoaaron wrote:

      Try it. It still applies. OMV 2.x has barely changed since 2016.
      Ok, this doesn't work for me... or maybe I missed something in the instructions?

      I select OMV-Extras.org and disable Sync on the Repos tab (Save & Apply); then I select Update Manager and select Check; no updates. Although SyncThing v0.14.46 has been released.

      If I reverse my steps and re-enable Sync on the Repos tab and check updates again, I am getting the same error as before. It appears joker_75 is having the same issue.
    • Hard to say. I haven’t had an OMV 2.x system running a long time. Even if something needed to be changed, I would recommend a fresh install of 3.x or 4.x.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • jchappelle wrote:

      z0rk wrote:

      ryecoaaron wrote:

      Hard to say. I haven’t had an OMV 2.x system running a long time. Even if something needed to be changed, I would recommend a fresh install of 3.x or 4.x.
      That's not an option for me at this time. Thanks for you help.
      This worked for me:
      Edit /etc/apt/sources.list.d/omv-extras-org-stoneburner.list and change the syncthing source from http to https.
      Awesome! Thanks man :thumbsup:
    • ryecoaaron wrote:

      Hard to say. I haven’t had an OMV 2.x system running a long time. Even if something needed to be changed, I would recommend a fresh install of 3.x or 4.x.
      I have an OMV 2.x running as well and the tip worked here also - thanks a lot for that!

      But I agree with z0rk and don't understand why the insufficient/unreliable OMV upgrade mechanism is treated as if it would be an easy 10 min job. I assume that with a re-installation of OMV I will loose my complete current configuration e.g. all the users, all the shares, all the plugin configuration like Syncthing. Everything in my house reads from and writes to this NAS, I don't want to start from scratch with every new version. My OMV NAS runs since 5 years but because of that I got a newer HP Microserver and move to FreeNAS now.
    • STS99 wrote:

      But I agree with z0rk and don't understand why the insufficient/unreliable OMV upgrade mechanism is treated as if it would be an easy 10 min job.
      The 2.x -> 3.x is the only difficult upgrade in my opinion. This upgrade is difficult because OMV made some large changes AND Debian switched from sysvinit to systemd. Upgrading to the latest version of OMV is also an upgrade of Debian. So, basically the upgrade is a release upgrade. OMV didn't invent this mechanism. The 3.x -> 4.x upgrade is an easy 10 min job for me...

      STS99 wrote:

      I assume that with a re-installation of OMV I will loose my complete current configuration e.g. all the users, all the shares, all the plugin configuration like Syncthing.
      Yes. On my systems, I could re-setup everything fairly quickly.

      STS99 wrote:

      Everything in my house reads from and writes to this NAS, I don't want to start from scratch with every new version.
      You don't have to start from scratch with every new version. We just recommend it with the 2.x -> 3.x change for reasons previously mentioned.

      STS99 wrote:

      My OMV NAS runs since 5 years but because of that I got a newer HP Microserver and move to FreeNAS now.
      Good luck. Strange that OMV has been working for you and you don't want to start from scratch but you move to another product...
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!