[GH-ISSUE #1951] Orion sync issue #1303

Closed
opened 2026-02-25 22:39:38 +03:00 by kerem · 4 comments
Owner

Originally created by @ehcorn on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1951

Which version of floccus are you using?

5.5.3

How many bookmarks do you have, roughly?

80

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Nextcloud Bookmarks

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

Orion 0.99.133-beta

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

15.1.0

Which version of Nextcloud? (if relevant)

31.0.4

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

also via nextcloud

Describe the Bug

have also tested with webdav to nextcloud, and git sync to gitea and they all give the same error:

E036: Missing permissions to access the sync server

orion does initially request access to websites when the extension is installed, either via chrome or firefox, however no additional permissions are requested once it's insatlled and the profile setup process in orion seems to go fine until I try the initial syncronization. Have also tested sync to a new destination folder inside nextcloud to have a clean slate and no change.

floccus-5.5.3-2025-05-08-full.log

Expected Behavior

Expectation would be to syncronize my bookmarks which it isn't doing at all.

To Reproduce

install the floccus extension for orion via firefox extension store, add a sync profile for nextcloud or other, begin syncronization to see the error.

Debug log provided

  • I have provided a debug log file
Originally created by @ehcorn on GitHub (May 8, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1951 ### Which version of floccus are you using? 5.5.3 ### How many bookmarks do you have, roughly? 80 ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Orion 0.99.133-beta ### Which version of Nextcloud Bookmarks are you using? (if relevant) 15.1.0 ### Which version of Nextcloud? (if relevant) 31.0.4 ### What kind of WebDAV server are you using? (if relevant) also via nextcloud ### Describe the Bug have also tested with webdav to nextcloud, and git sync to gitea and they all give the same error: E036: Missing permissions to access the sync server orion does initially request access to websites when the extension is installed, either via chrome or firefox, however no additional permissions are requested once it's insatlled and the profile setup process in orion seems to go fine until I try the initial syncronization. Have also tested sync to a new destination folder inside nextcloud to have a clean slate and no change. [floccus-5.5.3-2025-05-08-full.log](https://github.com/user-attachments/files/20107190/floccus-5.5.3-2025-05-08-full.log) ### Expected Behavior Expectation would be to syncronize my bookmarks which it isn't doing at all. ### To Reproduce install the floccus extension for orion via firefox extension store, add a sync profile for nextcloud or other, begin syncronization to see the error. ### Debug log provided - [x] I have provided a debug log file
kerem 2026-02-25 22:39:38 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

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 Nextcloud 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.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

<!-- gh-comment-id:2863765777 --> @github-actions[bot] commented on GitHub (May 8, 2025): Hello :wave: 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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! 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 Nextcloud 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. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (May 9, 2025):

Hello Aaron,

thank you for taking the time to give feedback by opening this issue! I really appreciate it!
The Orion browser is known to not support floccus at the moment, because it doesn't seem to properly implement the web extension permissions API, yet. Currently, the state of this issue is being tracked in #1643
I'm thus closing this as a duplicate. I encourage you to subscribe to #1643 to get wind of new developments on this issue.

<!-- gh-comment-id:2866880749 --> @marcelklehr commented on GitHub (May 9, 2025): Hello Aaron, thank you for taking the time to give feedback by opening this issue! I really appreciate it! The Orion browser is known to not support floccus at the moment, because it doesn't seem to properly implement the web extension permissions API, yet. Currently, the state of this issue is being tracked in #1643 I'm thus closing this as a duplicate. I encourage you to subscribe to #1643 to get wind of new developments on this issue.
Author
Owner

@ehcorn commented on GitHub (May 9, 2025):

thank you for your work Marcel, sorry for the duplicate! I thought I had checked thorroughly through the issue tracker before submitting my own.

<!-- gh-comment-id:2866973271 --> @ehcorn commented on GitHub (May 9, 2025): thank you for your work Marcel, sorry for the duplicate! I thought I had checked thorroughly through the issue tracker before submitting my own.
Author
Owner

@marcelklehr commented on GitHub (May 9, 2025):

No worries :)

<!-- gh-comment-id:2866998505 --> @marcelklehr commented on GitHub (May 9, 2025): No worries :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#1303
No description provided.