mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #31] Nextcloud 10.0.3 with ssl -> Chromium-> Floccus not synching #28
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Oct 9, 2017).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/31
I have installed Floccus to
Chromium : Version 61.0.3163.100 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)
Firefox : Version 56 running on Ubuntu 16.04 (64-bit)
Nextcloud 10.0.5 with official ssl certificate (eg. https://mync.work.gr:port) and the app is not working. The bookmarks never get synched nothing happens -> It says synching... and never ending or at least give an error.
I am the admin of the installation and i know that everytning else working fine.
@marcelklehr commented on GitHub (Oct 9, 2017):
Hi @SISolutions,
which version of floccus did you install? Can you see an Owncloud/Nextcloud bookmarks folder somewhere in your bookmarks? What doo you see if you close and reopen the floccus pop-up?
In any case: Could you follow the debugging steps provided over here: https://github.com/marcelklehr/floccus/issues/27 You may also want to check out the network tab in the debugger to see what is happening to the network request on sync.
@ghost commented on GitHub (Oct 11, 2017):
version 1.3.0
No i cant see any folder
see pic below says synching but nothing happens (i have deleted the url and username for obvious security reasons) but i will give you example. url: https://mync.work.gr:11011 username: me
close and reopen floccus i see the same like in the attachment
force sync is disabled
@ghost commented on GitHub (Oct 11, 2017):
Sorry but could FIND HOW TO copy the damn thing
@marcelklehr commented on GitHub (Oct 11, 2017):
Ok, I think I know what the problem is, even though I'd have needed the 'console' tab's content, rather than the 'inspector' tab's... My bad on that part. :)
@marcelklehr commented on GitHub (Oct 11, 2017):
Should be fixed in v1.3.0-beta.4. Reopen, or shout if it isn't :)
@marcelklehr commented on GitHub (Oct 11, 2017):
(Note, you'll probably need to delete the account you created in floccus, and create a new one, so that force sync becomes clickable again. This will not be necessary for future connection failures, though, as I fixed this as well.)
@ghost commented on GitHub (Oct 12, 2017):
Good morning.
Thank you my friend. Will try it immediately and reply to you the results.
QUESTION:
If i will use it at two different browsers (firefox,chromium) will the bookmarks be saved to two separate folders? or they all be merged in one?
Thank you for the quick response and keep up your good project.
@ghost commented on GitHub (Oct 12, 2017):
Removed previous Floccus and Installed the beta4 to chromium but still no connection. Force sync still grayed.
Console
extensions.js:2725 [Deprecation] /deep/ combinator is no longer supported in CSS dynamic profile. It is now effectively no-op, acting as if it were a descendant combinator. You should consider to remove it. See https://www.chromestatus.com/features/4964279606312960 for more details.
scrollToWrapper_ @ extensions.js:2725
@ghost commented on GitHub (Oct 12, 2017):
Still have issue
@marcelklehr commented on GitHub (Oct 12, 2017):
Aha. But we're getting somewhere. Apparently, there's a parse error happening :/ Could you go to the network tab in the inspector and inspect the last request to the bookmark endpoint? There should be a tab displaying the response data. Also make sure that the URL of the request is correct.
@ghost commented on GitHub (Oct 12, 2017):
Trying to connect and floccus says couldnt connect. Yes the URL is surely the correct.
@marcelklehr commented on GitHub (Oct 12, 2017):
ok, my bad again. You ended up in the wrong inspector, it seems. Sorry.
Here are the updated steps you can follow:
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "force Syncfor the account of your choicebookmarks, then click onresponsein the panel that opens and copy the data, paste it here after once again making sure that there is no more sensitive information in there@ghost commented on GitHub (Oct 13, 2017):
@marcelklehr commented on GitHub (Oct 13, 2017):
;)
@ghost commented on GitHub (Oct 13, 2017):
@ghost commented on GitHub (Oct 13, 2017):
floccus couldn't connect
waited for some minutes but console doesnt show anything
@ghost commented on GitHub (Oct 15, 2017):
To show you that my MC instance is working with no problems and floccus error. There is no movement as i see in the network or console.
@marcelklehr commented on GitHub (Oct 15, 2017):
Just to make sure: if force sync is greyed out, there'll likely be no movement in the network monitor -- Did you delete the account and set up a new one?
@ghost commented on GitHub (Oct 16, 2017):
Yes deleted and created many times. And from different browsers and places too (home & office).
A reminder. The installation uses a valid ssl cert.
@ghost commented on GitHub (Oct 17, 2017):
any news?
@marcelklehr commented on GitHub (Oct 17, 2017):
Mh. very strange. Would you perhaps be able to provide me with a test account on your instance? Then I could try some more explorative testing on my machine. Just drop me a mail. :)
@marcelklehr commented on GitHub (Oct 18, 2017):
Thanks, this was very helpful. It seems, the request to the bookmark endpoint is redirected to the nextcloud login page, on your instance. This could indicate that you're using an older version of the nc bookmarks app. Or nextcloud 10 doesn't allow basic auth, but that would be very weird. You could try checking the apps section in the nextcloud admin panel and making sure bookmarks is up to date. Also, have a look at the nextcloud logs, perhaps paste a relevant portion, while making sure there's no sensitive data in there. Look for failed authentication / login attempts.
@ghost commented on GitHub (Oct 18, 2017):
NC 10.0.6
Bookmarks 0.9.0 there is no any new update available.
NC log : Info - core - Bruteforce attempt from "my ip" detected for action
"login".
John P
On Wed, Oct 18, 2017 at 7:31 PM, Marcel Klehr notifications@github.com
wrote:
@marcelklehr commented on GitHub (Oct 18, 2017):
That's it, floccus requires nextcloud bookmarks app with at least version 0.10. See https://apps.nextcloud.com/apps/bookmarks
@marcelklehr commented on GitHub (Oct 30, 2017):
Closing due to lack of activity. I hope it works for you, now :)
@ghost commented on GitHub (Oct 31, 2017):
Nop its not working. Except that why you close an issue while still exists?
Friendly speaking.
On Oct 31, 2017 01:58, "Marcel Klehr" notifications@github.com wrote:
@marcelklehr commented on GitHub (Oct 31, 2017):
I'm sorry, John. I closed the issue, because I thought I had found its cause: an outdated version of the bookmarks app. You definitely need v0.10. I take it you have installed v0.10 now and it still doesn't work? Then lets reopen and investigate some more.
@ghost commented on GitHub (Nov 1, 2017):
NC 12.0.3
Ubuntu 14.04 lts
Firefox 56
Its installed but nothing happens
@marcelklehr commented on GitHub (Nov 1, 2017):
Thanks for the update! This is the old version, which doesn't have any status indicator, yet, so there won't be happening anything even if it worked. I suggest you install the latest beta (see #27) I will hopefully get around to releasing the next version soon, if the beta works for you (this issue is the last blocker ;) )
@ghost commented on GitHub (Nov 2, 2017):
Good morning Marcel,
Ok i will install the beta and will try it.
Yep lets home its our last blocker ;)
Thank you for your quick responce.
JP
On Thu, Nov 2, 2017 at 1:01 AM, Marcel Klehr notifications@github.com
wrote:
@ghost commented on GitHub (Nov 10, 2017):
Installed what you see in the attachment and again nothing is working.
NC 12.0.3 - Ubuntu 14.04 LTS
@marcelklehr commented on GitHub (Nov 10, 2017):
if the floccus options are unstyled as they are in your screenshot that means that you have not installed the latest beta, I'm afraid. (Note that you probably cannot permanently install the latest beta on firefox, but you need to load it temporarily as pointed out in #27).
Update: to be clear: You cannot install the latest beta from addons.mozilla.org!
@marcelklehr commented on GitHub (Dec 2, 2017):
Hey there, have you been able to try the beta?
@ghost commented on GitHub (Dec 9, 2017):
no i havent.
Most of the NC apps are very buggy and half working or not working at all. At this time i need apps that work so i can have a productive day. So i use NC only for upload/download files and some times sharing and even that its not stable or fast enough but no time to migrate at the moment somewhere else.
Unfortunately i dont have time to test your solution. Maybe i will try some day again but thats not gona happen now.
Keep up the good work.
@marcelklehr commented on GitHub (Jan 30, 2018):
Hey John,
I've updated floccus on addons.mozilla.com, so you could test it now without installing any beta version. From what I've gathered it works pretty well and hopefully won't cause you more headache :)
I'm closing this again for now. You're always welcome to drop a note here or open a new issue if you happen to give it another try and still hit problems.
Cheers!
@github-actions[bot] commented on GitHub (Mar 21, 2023):
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.