Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Backup failed: Backup endpoint is not active

Backup failed: Backup endpoint is not active

Scheduled Pinned Locked Moved Unsolved Support
cifs
6 Posts 3 Posters 863 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    ByMynix
    wrote on last edited by girish
    #1

    Hey, I get this error message as soon as the automatic backup starts and the backup cancels. Since I run my Cloudron server as a home server, my assumption is that the "forced disconnection by the provider" interrupts the Internet connection and the backup location (Hetzner Storage Box / CIFS) has to be remounted, see here:

    cecb12ee-a0be-4cd1-9e8d-c162fda95c58-image.png

    I have already tried it, after a remount the backup can be started again normally. My question is this: Is there a way to avoid this error message without having to remount manually every day (before each backup)? Possibly via a cron job or something similar?

    1 Reply Last reply
    0
    • nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote on last edited by
      #2

      the mountpoints are setup to be managed by systemd. I guess cifs can't deal with disconnects well in that case. Can you maybe add ,x-systemd.automount to the Options= field in the /etc/systemd/system/mnt-cloudronbackup.mount unit and run systemctl daemon-reload and lets see if this improves things, then we can fix this in the next release.

      B 2 Replies Last reply
      0
      • nebulonN nebulon marked this topic as a question on
      • girishG Do not disturb
        girishG Do not disturb
        girish
        Staff
        wrote on last edited by
        #3

        Incidentially, this is also root cause for the issues @opensourced is facing when copying large amounts of data. The CIFS disconnects sporadically and looks like something on Hetzner side. Maybe some keepalive/timeout .

        B 1 Reply Last reply
        0
        • nebulonN nebulon

          the mountpoints are setup to be managed by systemd. I guess cifs can't deal with disconnects well in that case. Can you maybe add ,x-systemd.automount to the Options= field in the /etc/systemd/system/mnt-cloudronbackup.mount unit and run systemctl daemon-reload and lets see if this improves things, then we can fix this in the next release.

          B Offline
          B Offline
          ByMynix
          wrote on last edited by
          #4

          @nebulon Alright. I have now added it once, let's see if it fixes itself with the next backup tomorrow. I will report then

          1 Reply Last reply
          0
          • girishG girish

            Incidentially, this is also root cause for the issues @opensourced is facing when copying large amounts of data. The CIFS disconnects sporadically and looks like something on Hetzner side. Maybe some keepalive/timeout .

            B Offline
            B Offline
            ByMynix
            wrote on last edited by
            #5

            @girish Possibly something also on the Hetzner side yes, but so far I have not had any connection problems with the Hetzner Storage Box. It only happens after the forced disconnection at night that the CIFS mount is no longer active. The only thing could be an integrated timeout. Although it would be very strange. The forced disconnection until the IPs are reconnected at night is around 10-20 seconds. Maybe Hetzner Storage Box binds itself to the IP while the mount is active? I don't know enough about it, just a vague guess

            1 Reply Last reply
            0
            • nebulonN nebulon

              the mountpoints are setup to be managed by systemd. I guess cifs can't deal with disconnects well in that case. Can you maybe add ,x-systemd.automount to the Options= field in the /etc/systemd/system/mnt-cloudronbackup.mount unit and run systemctl daemon-reload and lets see if this improves things, then we can fix this in the next release.

              B Offline
              B Offline
              ByMynix
              wrote on last edited by
              #6

              @nebulon Unfortunately it didn't work.

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search