Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with Koofr webdav +floccus android #1531

Closed
1 task
msalini opened this issue Jan 27, 2024 · 3 comments
Closed
1 task

Error with Koofr webdav +floccus android #1531

msalini opened this issue Jan 27, 2024 · 3 comments
Labels

Comments

@msalini
Copy link

msalini commented Jan 27, 2024

Which version of floccus are you using?

5.0.9

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Lineage 18.1 (rooted) on Samsung Galaxy A5

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

Koofr Webdav server

Describe the Bug

When syncing the file, i get the following error message:

E019: HTTP status 404. Failed PUT request. Check your server configuration and log.

steps to mitigate the error but didn't work

  • clean cache
  • change koofr sync folder
  • uninstall / reinstall the app
  • started with an empty folder and sync the entire bookmark again

Expected Behavior

Webdav should work

To Reproduce

Set up a new koofr webdav connection on the app and sync. Either with existing or new ptofile. Sync and error appears.

Debug log provided

  • I have provided a debug log file
@msalini msalini added the bug label Jan 27, 2024
Copy link

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

@msalini
Copy link
Author

msalini commented Feb 5, 2024

My fault, not a bug. A hard-to-detect typo in my folder path. Closing issue.

@msalini msalini closed this as completed Feb 5, 2024
@marcelklehr marcelklehr moved this to Done in Floccus May 19, 2024
Copy link

github-actions bot commented Feb 5, 2025

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Status: Done
Development

No branches or pull requests

1 participant