Works intermittently on chrome on Linux Mint

[BjornFJohansson]

Describe the bug

All the settings are correct afaik, see screenshots below. Stops working after browser restart. First screenshots to prove that the settings are correct to the best of my understanding, symptoms of the problem at the end as well as log in json format. When it works, this is a great tool and time saver. Thanks for your effort. /bjorn

obsidian-local-rest-api.bug_report.json

To Reproduce

1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error

Expected Behavior

Works sometimes.

Operating System

Linux Mint 21.3 Cinnamon

Browser

chrome

Browser Version

122.0.6261.69

[coddingtonbear]

You've given a lot of data up there -- thanks for that! But, it's a little difficult for me to tell exactly what you're finding difficulty with from the context above. Is it:

• The dialog doesn't appear when you click the button.
• The dialog appears, but when you press the send button, nothing happens.
• The dialog appears, and when you press the send button, the dialog disappears, but the content doesn't appear in your notes.

I kind of wonder if the thing you're commenting on is that you see an "ERR" message on the extension icon, but have to say that I'm sort of surprised you see that message at all since your configuration shows that background search is disabled, and I'm fairly sure without background searches being on, we don't even try to do anything that might cause the extension icon to be decorated (and when we fail to do that, display such an error). And, even in such a case, everything will still work, it just won't be able to let you know when it has found a match (but you have that disabled; so that's not surprising!).

Could you elaborate a bit on what exactly you're doing and what part of it isn't working?

[coddingtonbear]

Actually, I bet it is that last bit that you're referring to. As it turns out, there is a bug that will cause us to always do background searches, even when they're disabled. I've put together a patch that (see 33aa462) that'll go out with the next release.

That being said, if this is truly the error you're referring to, things should still work; we just might show an erroneous error message on the icon.

Could you confirm that this is actually the problem you were referring to?

[BjornFJohansson]

Thank you for your reply and sorry for not including that last bit. Clicking on obsidian web would give me "Could not connect..." see below:

Going to the "Local REST API for Obsidian" and inserting my key would work perfectly.

What happened next surprised me, I left it alone, waiting for a response here, tried it and it worked again, without any intervention. Maybe there is a lag somewhere or some restart that I did not do?

Now it is working as intended and I can capture notes to obsidian. I cant really say if this was a bug or why it took the time it took, but maybe this could help others experiencing the same problem.

Thanks for your help!

[coddingtonbear]

That's... interesting. I'm surprised that there would ever be any substantial lag around that. I'm curious -- if you had to guess, how many files were in your notes vault?

[ffdumont]

Uploading obsidian-local-rest-api.bug_report.json…
Hi @coddingtonbear ! I'm facing the same issue on MacOS 14.2.1 and Chrome 122.0.6261.94 : get "Could not connect to Obsidian" message while setup is correct (green shield). I also observed it working intermittently this morning, but most of time it's not. Thank you !

[coddingtonbear]

Hrm, well, I don't test things directly on Mac OS, but I can maybe give you some things to check on if you upload a bug report export from the extension options page's upper-right corner. It looks like you tried to upload one to your original comment, but it doesn't appear that one is there.

[ffdumont]

obsidian-local-rest-api.bug_report.json
Here it is @coddingtonbear

[coddingtonbear]

Just at a glance, I can tell you that your version of Obsidian Local REST API is many, many versions out-of-date; I'm surprised you haven't seen the yellow banner on the extension's options page instructing you to update it. More than likely, your certificate needs to be re-generated and re-imported, and once you do that update, you'll be instructed to do so in Obsidian Local REST API's settings. From there, what I'd recommend is following these troubleshooting instructions I recently gave somebody: #174 (comment)

[ffdumont]

Thank you ! I did not get this update banner, but I followed you procedure and everything's fine again.

[coddingtonbear]

I'm fairly sure just updating the extension won't be sufficient, but if that works for now, good for you! I'd imagine it'll start failing again once you've closed the options page for a while. If I remember correctly, the root problem is the way earlier versions of Obsidian Local REST API were generating the certificate would make a certificate that would be accepted only in narrow situations (maybe only when the options page is open or was recently?). I assume you'll have to follow the subsequent steps in the comment I linked to you to get things back to a clean slate.

[BjornFJohansson]

Still working after a few days...