App upgrade in an invalid state, app image upgraded and shows it is running new version under Info but under Updates it still believes an update is needed

[ChristopherMag]

@girish We can close this for now, I don't think I am going to have the time in the near future to recreate this by doing the following:

• Install an older version of an app that is 1 version behind the most current version
• Create a volume on cloudron that is accessible
• Add that volume to the app
• Take some action so the volume not accessible any longer, (like a cifs/sshfs/nfs volume where the host has been shutdown
  • Confirm the volume still has a green status in Cloudron
• Update the app
• After the app fails to start up after the update remove the volume from the app
• Start up the app
• Confirm the app is running the updated package version
• Confirm that the updates tab still lists the same package version the app is running as an available version to install and that clicking update again fails with the downgrades not permitted error.

[ChristopherMag]

A new version of paperless was released and I started up the copy of the app that was unable to update as it kept trying to update to the version it was already on and when I did check updates it found the newest one and was able to install it.

Basically if an app gets in the weird state where it is already running the current version and it keeps trying to update to that same version it is already running and failing you can disable automatic updates until the next real update and the next real update will replace the one that was there and then it will be able to update normally again without backing up and restoring the app like I did to work around the issue sooner.

Separate from that, for or anyone coming later, the surfer solution is not working out as the password has to be reentered for the mapped drive each day.

I can see that the credential is saved in Windows Credential Manager but for whatever reason each new day it prompts for the credential with the remember my credentials box unchecked. Entering the password and checking the box will work for a day but then roughly by the next day it will prompt again.

If the user doesn't proactively navigate to this drive letter than scanning with the scanner just fails as it cannot write to that drive letter and it isn't obvious what is wrong.

It appears the issue is that windows won't resupply the authentication when the webdav server is using basic authentication.

This means that likely switching to the sftpgo app on cloudron that also offers webdav won't fix the issue as there is no shared authentication scheme, like kerberos, that both windows and cloudron can use that would allow this to work without resupplying the credential every day.

Microsoft's stated work around is a scheduled task that maps the drive new each time the computer boots and has the password hard coded in the task which is not good.

Going back to the drawing board of how to have access to a place save files from a windows host that can be accessed via standard windows file access libraries (drive letters, UNC paths).

Cloudron documentation does have a process for setting up an NFS share which I wouldn't have thought would be supported given that it installs packages and changes configuration on the host os but I am going to try that with the windows based nfs client and see if that works any better.

[nebulon]

If I read this correctly the issue that windows is not persisting the webdav password is not related to the update issue? Wherever you add the webdav mount in windows, maybe there is some "remember password" option or so? There is otherwise likely nothing we can do as that is a client side issue

[ChristopherMag]

@nebulon Aboslutely nothing you can do on your side about that, limitation of windows.

I tried to use NFS shares from the cloudron server but windows only supports NFSv3 not NFSv4 and that results in dynamic ports having to be opened on the firewall or a host of services have to be assigned static ports.

Even after all that the NFS mounts on windows also don't consistently remember their passwords (even when checking the boxes that indicates remember password).

I have given up and done what I didn't want to do which is install samba on the cloudron host and serve the directory via CIFS from there.

All the clients are connected via a samba user and it will persist accross reboots without issue.

The biggest downside is that I am now running something extra on the cloudron server that isn't intended to be there but until there is some way to host samba as an app or some other app on cloudron that supports cifs I don't see any way to work around the issue of needing windows clients to be able to write to a location via native filesystem apis that apps running on cloudron can also access without depending on a server other than cloudron itself to host those files.