Error trying to sync on Firefox 58. about floccus

[marcelklehr]

Hello! :)

mmmh. I haven't used 2FA in nextcloud yet, so I haven't been testing it with floccus either. It seems very likely that's the problem. In any case:

In order to aid in debugging, please provide client-side logs. ;)

Firefox

• Go to about:debugging
• click on debug button next to floccus entry
• go to floccus options and make sure the account of your choice is connected
• trigger a sync by clicking on force Sync for the account of your choice.
• go back to the inspector window and copy the logs after waiting approx. 2mins
• paste the logs somewhere else removing any sensbile info and link to the site here (e.g. use https://pastebin.com)

Chrome

• Go to chrome://extensions
• enable Developer mode
• click on dist/html/background.html button in floccus' entry next to "Inspect views: "
• go to floccus options and make sure the account of your choice is connected
• trigger a sync by clicking on force Sync for the account of your choice
• go back to the inspector window and copy the logs after waiting approx. 2mins
• paste the logs somewhere else removing any sensbile info and link to the site here (e.g. use https://pastebin.com)

[githubtefo]

Now I can sync!
It was a problem related with the address: I should enter https://www.example.server.com/nextcloud/ instead of https://www.example.server.com/nextcloud
I could figure out thanks to the debugging tool.
Thank you!

[marcelklehr]

mmmh. Which version do you have installed? This should be fixed in v1.3.3 :(

[githubtefo]

V1.3.3 from Mozilla repositories. Don't worry, may be the showed example in the plugin should contain the "/" at the end.
BTW, the nextcloud application password works!

[marcelklehr]

Awesome!

I've just released a new version which now has the fix for the trailing slash problem (which was supposed to land in the last version, grmbl).

Thanks for reporting and happy syncing!

[github-actions]

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.