mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #198] Error 500. Failed PUT Request. Check your server configuration. #187
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#187
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 @bernd-wechner on GitHub (Nov 20, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/198
Software versions
Steps to reproduce
Expected outcome
It continues working. In fact it is still working fine on:
Actual outcome
On this Firefox 63 on the Linux Mint 19 box it now reports:
The debug log does not show any error in the last few lines.
My inferences
Error 500 is a typically a n internal server error, server side, so a NextCloud issue. But:
So a puzzles me that an error 500 is even possible. Can send debug log through if desired and helpful, but it's full of my many many bookmarks and login details o would redact it a little and prefer to send as PM than on public post.
As an aside the Sync is real fast on Chrome and on Win 10 (Firefox and Chrome) but Firefox on Linux Sync takes a long long long time before it bombs with the Error 500. Also to best of my knowledge no system , or browser changes 2 days ago and it was working brilliantly until then. I cannot of course rule out some underlying change, a new addon or something 2 days ago, life too unclean and busy to be 100% sure, but none spring to mind.
@Tank-Missile commented on GitHub (Nov 21, 2018):
I'm having the same issue on Chromium, but it never worked to begin with. I had to go with XBEL sync, which has its own problem that I should report in a seperate issue.
@bernd-wechner commented on GitHub (Nov 21, 2018):
Probably same symptom, different issue. Floccus has worked fine for ages, is working fine in three listed contexts, got itself in a knot on this one just two days ago. Floccus has an excellent debug log that can either help a willing dev diagnose this and/or which in my experience is readily added to (more logging info written to it0 in order to help diagnose such an issue.
It could be that if Error 500 is accurate too that a look in server side logs helps, but I'd need a clue as to where to look on the NextCloud side. An experienced dev's assessment of my inferences would be good.
XBEL looks like a good standard, I wonder if Floccus uses it to communicate with the Bookmarks app or when storing on WebDAV? A side issue mind you. I'm also not keen to abandon this seriously awesome project for another (like XBELSync) as Floccus has been working awesomely and it does have at least of late some really awesome dev support and is evolving. I'd give it some dev time if only i had some ti give and didn't face a big learning curve on its particular code base to boot.
@marcelklehr commented on GitHub (Nov 21, 2018):
Uh oh.
I think I'll open a separate issue to investigate performance problems with firefox again.
Generally, if you get a 500 Error it's a server-side error. That doesn't mean the server is broken. It probably just means there's a bug in the bookmarks app that triggers an error under specific circumstances. The Specific error message from the nextcloud log plus the last log messages from the floccus debug log are helpful in this case. In case you're concerned about privacy, feel free to drop them via mail (I even have a PGP key somewhere, I think).
@marcelklehr commented on GitHub (Nov 21, 2018):
Floccus stores bookmarks in an XBEL file when using WebDAV (I assume that's what @Tank-Missile was referring to). The bookmarks app currently only has a REST API.
@bernd-wechner commented on GitHub (Nov 22, 2018):
I'll have to look for the "nextcloud log" to see if I can find where that is. Tips appreciated. But I'll take a look ASAP. I have ssh and web access to the nextcloud server, just need the time to poke around. Quick acknowledgment now is all I have time for. Maybe later today.
@marcelklehr commented on GitHub (Nov 22, 2018):
@bernd-wechner see https://docs.nextcloud.com/server/14/admin_manual/issues/general_troubleshooting.html#nextcloud-logfiles ;)
@marcelklehr commented on GitHub (Dec 3, 2018):
@bernd-wechner Any new insights on this?
@SEWADE commented on GitHub (Dec 4, 2018):
@marcelklehr
Hi,
I have the same problem. That is the first time I try to use Floccus. Maybe I can help to forward resolving this issue!?
I've running Nextcloud on my own machine, so I have access to all needed logs.
That is what I see in the log file when I start synchronization with Floccus:
`
Error index Error: Call to undefined method GuzzleHttp\Client::request()
`
Regards
Sebastian
@SEWADE commented on GitHub (Dec 4, 2018):
Hi,
me again.
I figured out that this issue is done after updating Nextcloud to 14.0.4.
Regards
Sebastian
@bernd-wechner commented on GitHub (Dec 5, 2018):
Alas been away and off line for 10 days. No real insights aside the observation that perhaps it affects all my clients and it was an illusion that some worked. The reason I think it seemed it worked was that it's not until you add a bookmark to the client then the PUT fails. More later when I find time. First unpacking and recovering from a trip away and massive backlog of TODOs this one included. I do want to see my bookmark sync working again so I won't forget it ... and will be back as soon as I can with more diagnostics if possible. Only quick observation I have is that unlike Sebastian I'm on Nextcloud
14.0.3.0 for now. But will be checking updates to NextCloud, its apps and Floccus soon, before continuing with diagnostic attempts.
@marcelklehr commented on GitHub (Dec 10, 2018):
@bernd-wechner It could be that this is because of an emoji or some similar high-value UTF8 character (see https://github.com/marcelklehr/floccus/issues/210)
@bernd-wechner commented on GitHub (Dec 13, 2018):
Alas I'm NexCloudPi and as reported on #210 it's already set up with UTF 8.
I just took another look. Here's what I tired. A bookmark Sync Now which reliably reports
Error 500. Failed PUT Request. Check your server configuration.then on the NexCloud server in /varl/log:Notice that the only real candidates here are the ones altered at 21:51.
Nothing in those log files lends any clue alas.
In the floccus debug log there is no mention of the PUT error.
I'm feeling stuck. Can I ask a favour?
If a PUT error is encountered by floccus, log tot he debug log a transcript of the PUT transaction. What where you trying to PUT, and what did the server respond? if these appeared in the debug log it might help immensely. I'm really suffering here, floccus is so so cool! And suddenly stopped working without any clue why? Though likely related to a NexctCloud or Bookmarks app upgrade!
@marcelklehr commented on GitHub (Dec 13, 2018):
@bernd-wechner Before we do that, could you also take a look at
/var/www/nextcloud/data/nextcloud.log(or alternatively in the UI under 'Settings'/'Logging')?EDIT: You also appear to be running firefox 63. I'm curious as to what's going to happen, when you update to v64.
@bernd-wechner commented on GitHub (Dec 14, 2018):
Just updated to 64 (finally appeared in the Mint updates. No change. But the nextcloud.log file contains this as it's last line:
{"reqId":"XBMBUX8AAQEAAEvnVw4AAACU","level":3,"time":"2018-12-14T01:03:14+00:00","remoteAddr":"192.168.0.1","user":"bernd","app":"index","method":"PUT","url":"\/index.php\/apps\/bookmarks\/public\/rest\/v2\/bookmark\/357","message":{"Exception":"Error","Message":"Class 'OCA\\FullTextSearch\\Api\\v1\\FullTextSearch' not found","Code":0,"Trace":[{"file":"\/var\/www\/nextcloud\/3rdparty\/symfony\/event-dispatcher\/EventDispatcher.php","line":212,"function":"OCA\\Bookmarks_FullTextSearch\\AppInfo\\{closure}","class":"OCA\\Bookmarks_FullTextSearch\\AppInfo\\Application","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"\/var\/www\/nextcloud\/3rdparty\/symfony\/event-dispatcher\/EventDispatcher.php","line":44,"function":"doDispatch","class":"Symfony\\Component\\EventDispatcher\\EventDispatcher","type":"->","args":[[{"__class__":"Closure"}],"*** sensitive parameter replaced ***","*** sensitive parameter replaced ***"]},{"file":"\/var\/www\/nextcloud\/apps\/bookmarks\/controller\/lib\/bookmarks.php","line":774,"function":"dispatch","class":"Symfony\\Component\\EventDispatcher\\EventDispatcher","type":"->","args":["*** sensitive parameter replaced ***","*** sensitive parameter replaced ***"]},{"file":"\/var\/www\/nextcloud\/apps\/bookmarks\/controller\/rest\/bookmarkcontroller.php","line":313,"function":"editBookmark","class":"OCA\\Bookmarks\\Controller\\Lib\\Bookmarks","type":"->","args":["bernd","357","https:\/\/www.hobartcity.com.au\/Council\/Council-and-Committee-meetings\/Live-recordings-of-Council-meetings","Live recordings of Council meetings - City of Hobart, Tasmania Australia",["floccus:>Bookmarks Menu>Hobart","floccus:>Bookmarks Bar>Hobart"],"",0,null]},{"file":"\/var\/www\/nextcloud\/lib\/private\/AppFramework\/Http\/Dispatcher.php","line":166,"function":"editBookmark","class":"OCA\\Bookmarks\\Controller\\Rest\\BookmarkController","type":"->","args":[357,"https:\/\/www.hobartcity.com.au\/Council\/Council-and-Committee-meetings\/Live-recordings-of-Council-meetings",{"tags":["floccus:>Bookmarks Menu>Hobart","floccus:>Bookmarks Bar>Hobart"]},"Live recordings of Council meetings - City of Hobart, Tasmania Australia",null,null,null,null,null]},{"file":"\/var\/www\/nextcloud\/lib\/private\/AppFramework\/Http\/Dispatcher.php","line":99,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Bookmarks\\Controller\\Rest\\BookmarkController"},"editBookmark"]},{"file":"\/var\/www\/nextcloud\/lib\/private\/AppFramework\/App.php","line":118,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->","args":[{"__class__":"OCA\\Bookmarks\\Controller\\Rest\\BookmarkController"},"editBookmark"]},{"file":"\/var\/www\/nextcloud\/lib\/private\/AppFramework\/Routing\/RouteActionHandler.php","line":47,"function":"main","class":"OC\\AppFramework\\App","type":"::","args":["BookmarkController","editBookmark",{"__class__":"OC\\AppFramework\\DependencyInjection\\DIContainer"},{"id":"357","_route":"bookmarks.bookmark.edit_bookmark"}]},{"function":"__invoke","class":"OC\\AppFramework\\Routing\\RouteActionHandler","type":"->","args":[{"id":"357","_route":"bookmarks.bookmark.edit_bookmark"}]},{"file":"\/var\/www\/nextcloud\/lib\/private\/Route\/Router.php","line":297,"function":"call_user_func","args":[{"__class__":"OC\\AppFramework\\Routing\\RouteActionHandler"},{"id":"357","_route":"bookmarks.bookmark.edit_bookmark"}]},{"file":"\/var\/www\/nextcloud\/lib\/base.php","line":987,"function":"match","class":"OC\\Route\\Router","type":"->","args":["\/apps\/bookmarks\/public\/rest\/v2\/bookmark\/357"]},{"file":"\/var\/www\/nextcloud\/index.php","line":42,"function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"\/var\/www\/nextcloud\/apps\/bookmarks_fulltextsearch\/lib\/AppInfo\/Application.php","Line":97,"CustomMessage":"--"},"userAgent":"Mozilla\/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko\/20100101 Firefox\/64.0","version":"14.0.3.0"}which may contain a clue as it does reference the PUT and
"Exception":"Error".@marcelklehr commented on GitHub (Dec 14, 2018):
Simple fix: Disable Bookmarks_FullTextSearch.
@bernd-wechner commented on GitHub (Dec 14, 2018):
Stunning, all that pain and so easily fixed. That is, it worked.
But as a good community minded kinda guy, I am rarely content with just a quick fix and perforce must ask
Thanks for your support so far Marcel, cannot say how grateful I am really. it's been a period of uncertainty and confusion in my bookmark syncing in a very distractingly busy phase of life where I struggled to make/find time to do deeper diagnoses. But it seems resolved! Excepting the questions above I guess, which drive to making a wider, more lasting solution than a quick fix of my problem.
@marcelklehr commented on GitHub (Dec 14, 2018):
Aah, I'm relieved then. Thanks for your foresight with those questions, I'll answer as best I can:
The fulltextsearch app does not work well together with the latest versions of the bookmarks app. This bug of apparently causing an error of its own accord when it should just receive a hook about an updated bookmark is a new low, but nothing that surprises me.
You're not the only one already, but hopefully the last if I add a note to the README to avoid the fulltextsearch app.
The fulltextsearch app would need fixing, but alas, I'm currently in no position to donate that much time :/
Floccus is not able to discern this exact situation from other server-side failures, sadly, so there's not much I can do, except add a note to the floccus README, as well, perhaps.
@bernd-wechner commented on GitHub (Jan 13, 2019):
-------- Forwarded Message --------
To: Marcel Klehr mklehr@gmx.net
From: Bernd Wechner bernd.wechner@gmail.com
Subject: Debug Log for Issue 218
Message-ID: b72775de-04e7-af39-a52c-b29383f8bdb8@gmail.com
Date: Thu, 27 Dec 2018 22:09:44 +1100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
Thunderbird/60.2.1
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="------------893843CE5DCA589BD40FEA3B"
Content-Language: en-AU
Marcel,
As per note at:
https://github.com/marcelklehr/floccus/issues/218
Find attached the debug log.
May it be of use.
I suspect it might be nice if floccus writes an error message to screen
say, via it's setting panel, that it write the same message with any
extra details to the log file. Even if it had not extra details, if the
message appeared I'd see where in the timeline of messages it crops up,
the last line or somewhere in between or wherever.
This one looks like it might just be a config issue (change?) not sure.
I'll add more details to the issue that I have too.
Regards,
Bernd.
@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.