Fixed: My_webdav breaks after migration

Support
, ,
1

tl;dr after migrating, you need to add ‘Visitors’ to the perms for the app or it will break as described below. Big thanks to wbk! :slight_smile:

What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.0.9.2 (stable)
How are you able to access your server: SSH and web ui
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: I don’t think so

Describe your issue

After migration, I thought all was good except for an appearance tweak, but the my_webdav app is no longer syncing with joplin.
Joplin is a note taking app for phone and pc. It syncs using webdav. My same account syncs seamlessly between two pc’s in different towns, my phone and my tablet using webdav on yh.

After I migrated, it stopped working.
Now the Joplin app on phone or pc errors out with:

Last error: SyntaxError: Unexpected token ‘<’, "<!DOCTYPE "… is not valid JSON

Looking deeper, I checked the whole message which reads:

Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was:
PROPFIND : Unknown error 2 (405): 405 Not Allowed 405 Not Allowed

nginx (Code 405)

My credentials are correct. It does log in. In the user web ui I get the message:

“Si vous voyez cette page, c’est que la configuration du Webdav devrait fonctionner”

/home/yunohost.multimedia/gemlog does exist.
It has my files and it is owned by user gemlog and group multimedia as it should be.

I am baffled as to what is broken. The only odd thing I notice is that in the yh backend for the webdav app it says:

NB2: the file myfile, in https://domain-name/my_webdav/myfile
will be stored, on the server, in the path of the connected user: /home/yunoshot.multimedia/user

I see there is a typo. It says ‘yunoSHOT.’ vs ‘yunoHOST’ and I wonder if that typo propagated through the code and it is looking in the wrong place? I am sorry, but that is all I can think of.
I can try again to explain better maybe. Or maybe I have perms set up wrong in yh. I have no idea at this point.

8

no problem
Can you just delete the various posts on this page, and édit the first one in order to explain the problem?

9

Hallo, I did as you asked a while back. I guess I needed to reply the thread as well, sorry.

10

Hi gemlog,

I’m not familiar with Joplin or my_webdav, so excuse me for my perhaps useless addition to the convensation.

Do I understand correctly:

  • Joplin is installed via Yunohost
    • PC in town 1 uses Joplin on Yunohost
    • PC in town 2 uses Joplin on Yunohost
    • tablet uses Joplin on Yunohost
    • telephone uses Joplin on Yunoost
  • My_webdav is installed via Yunohost
    • all devices also use my_webdav to sync files

NB2: the file myfile, in https://domain-name/my_webdav/myfile will be stored, on the server, in the path of the connected user: /home/yunoshot.multimedia/user``

It seems a typo. Searching for yunoshot on Github, there is one result, “Clarification of instructions”. In it is mentioned:

Also, as an additional comment, https://domain-name/my_webdav is only accessible to WebDav clients if visitors have permission to view it in the Yunohost web admin → Users → Manage groups and permissions. Otherwise, clients are denied connections.

As a result of the ensuing discussion, some changes have been made to my_webdav recently. I guess these changes, not the migration, have broken your setup. The conversation may have some hints that apply to your situation.

While typing this message I gave installing Joplin a try. I get the impression, that Joplin provides synchronisation without need for an additional service. If you do not need my_webdav for anything else, maybe you can use Joplin to do the syncing itself.

11

Joplin is an android application as well as a PC application. It has a few sync targets including webdav. I have been using joplin with webdav for years. Formerly, I just configured nginx to have webdav and pointed all my joplin installs at it.
For the past few years I have been using the YUNOhost built-in webdav. This worked perfectly across all devices until I did the recent migration and update.
It is now broken across all devices and shows the error messages I detailed above.
If it’s a permissions problem, I can’t figure it out. I am admin. I am enabled.
Here is a screenshot:

12

Ah, I see; Joplin is not installed on your Yunohost, but Yunohost is only used as a synchronisation clearing house.

Did you have a look at the discussion over at Github? It was too long for me to make sense of without having the actual problem on my server. The conclusion of that conversation may seem that my_webdav is not functional in the way it was before, but perhaps there is a hint there that helps you solve the issue.

Installing Joplin on your Yunohost would be a workaround, but it seems quite heavy if it only provides a WebDAV server (it does not seem to provide online note taking ability, but maybe you can view notes on it).

Another workaround would be to use the custom_webapp, and configure Nginx as you are used to.

13

Oh bless you!!! :slight_smile:
Adding ‘Visitors’ to the perms fixed it!! :slight_smile:
People still need a user name and passwd, so that’s ok really.
I was flashing a phone with /e/OS and flashing is always a bit of a nail biter and I wasn’t paying proper attention to your post. I’m sorry about that, but very grateful now!
My GF uses this too on phone and pc.
I will change my post to fixed.
Thank you so much! :slight_smile:

14

Great! Good to read :slight_smile:

Yeah, that does raise the stakes :wink:

Outspoken atheist here, but don’l let that hold you back (I guess atheists can be blessed as well) :stuck_out_tongue:

Yes, it is. All went right? Have you used it before, and are you happy with /e/?

15

I don’t have any particular blessing power that I’m aware of - just take it as an expression of joy with your existence! :wink:
No, I’ve not used /e/ os before. Today is my zeroeth anniversary! :slight_smile:
There were only two bumps. After OEM unlocking it just sat there locked up with the word ‘Samsung’ on the screen forever. I did a recovery button thing: down vol, bixby + power and then it booted normally as factory and unlocked. Then the usual devops, usb stuff. At some point I had a screen that at once warned me not to interrupt it AND also cancel it :frowning:
Cancel it was the right choice and then a bunch more button pressing and mouth holding in the right shape. In fact, if I had looked in the xterm I’d launched it from, I would have known to go ahead. Mind you, the destructions told me to launch it from the kde/w/e start menu, so I would not have seen it…
Otherwise, great! The ‘app lounge’ combines an aurora-like thing and f-droid in one gui. Sweet! I’ve already put on kde-connect, a pdf thing and joplin.
Joplin is still happily synching - thanks to you! :slight_smile:
It will be a good while, b/c I have many years worth off Nag (Amiga!), zimwiki and joplin all in the one, so… lots.
The joplin in waydroid/lineage has also sync’d just fine already too.
I will let annie know she can sync again too. Whew! :slight_smile:

1 Like