Could not connect to Obsidian

[jonasqin]

Describe the bug

Every time I click the extension, it shows the notes below. I tried to reset my local keys and reinstall certificates, but they didn't work. Please help me

obsidian-local-rest-api.bug_report.json

To Reproduce

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

Expected Behavior

No response

Operating System

windows 10 and mac

Browser

chrome

Browser Version

121.0.6167.185

[coddingtonbear]

It's really very difficult to say what might be going wrong from the information I see here -- does the settings page show any problems with your connection?

[jonasqin]

No, it appears alright

[coddingtonbear]

Glancing at the bug report, it looks like you're a few versions out-of-date. What does that screen look like if you follow the instructions here: https://github.com/coddingtonbear/obsidian-web/wiki/How-do-I-ask-Chrome-to-update-extensions-immediately%3F

[jonasqin]

I have already updated my extension but it seems not work.
I have reset certificates from Local REST API, but it still don't work

[coddingtonbear]

Try to consider how much information I have about your installation and settings from what you have shown or told me and whether that would be enough information for me to help you. I unfortunately only have your screenshot from the beginning and your log from the beginning, and clearly you have changed some variables now. Perhaps you could send a new bug export and maybe screenshots of your Obsidian Local REST API settings?

[jonasqin]

obsidian-local-rest-api.bug_report.json
sorry, here is the bug report file. if you need anything please tell me. I really like your works and appreciate your help

[coddingtonbear]

Here are some general steps that should hopefully clean up your current installation as well as get it back into a working state:

1. First, update your installation of Obsidian Local REST API. It's still out-of-date. You can do that by:
   • Go into Obsidian's settings and find the "Community Plugins" section.
   • Press the "Check for Updates" button.
   • Notice that there's now an "Update" button next to "Obsidian Local REST API".
   • Press that "Update" button.
2. Go into your browser or operating system's certificate store and delete any certificates you've already uploaded for use by Obsidian Web (it will have "Obsidian Local REST API" in its name). This step is very important because otherwise, your browser may be using a now-invalid certificate and getting to a "clean slate" is essential for any of the next steps to get you any interesting insights. That process varies for every operating system; so I cannot offer much help with that, but you may at least get some idea of where to look by going to the same parts of your operating system's settings you would use for uploading those certificates in the first place (https://github.com/coddingtonbear/obsidian-web/wiki/How-do-I-get-my-browser-trust-my-Obsidian-Local-REST-API-certificate%3F).
3. Next, let's prove that the connection works at all by turning off the HTTPs server and reconfiguring Obsidian Web to connect to it:
   • In Obsidian Local REST API's settings and turn on the toggle next to "Enable Unencrypted (HTTP) Server"; then in the "Advanced Settings" section, turn off the "Enable Encrypted (HTTPs) Server",
   • Go into your Obsidian Web settings and remove and re-add your API key. This will trigger the extension to re-try the connection. This time, you should see a blue icon that looks like a "cable" next to the API key field instead of a green "shield" icon. If you see the green "shield" icon, you did not succeed at step 1 above and you should go to the beginning and try again. If you see a red icon and a warning that no connection could be established, make sure your HTTP (not HTTPs) server is enabled in Obsidian Local REST API's settings and try again.
   • You can theoretically stop here if you don't care about HTTPs (and HTTPs really only matters in any meaningful way when you're connecting to a host other than 127.0.0.1), but the following steps are still recommended.
4. Re-generate certificates and re-install the certificate into your browser or operating system's trusted certificate authority store by:
   • In Obsidian Local REST API's settings, find the button labeled "Re-Generate Certificates" and click it. This will cause the plugin to unload itself, so the screen should become blank.
   • Go back into Obsidian Local REST API's settings and find the link for downloading the current certificate. Click the link and download the certificate.
   • Install this certificate as a trusted certificate authority in your browser or operating system's settings (https://github.com/coddingtonbear/obsidian-web/wiki/How-do-I-get-my-browser-trust-my-Obsidian-Local-REST-API-certificate%3F)
5. Re-configure Obsidian Web to connect via HTTPs by:
   • In Obsidian Local REST API's settings and turn off the toggle next to "Enable Unencrypted (HTTP) Server"; then in the "Advanced Settings" section, turn on the "Enable Encrypted (HTTPs) Server". Note that this is the opposite toggle settings as we had in step 3 above.
   • Go into Obsidian Web settings and remove and re-add your API key. This will again trigger the extension to re-try the connection and now you should see the green "shield" icon.
6. Force Obsidian Web's background processes to be restarted by right-clicking on the extension icon, clicking the button labeled "Manage Extension", and then toggling the "On" toggle to "off" then "on" again.

If at any point you cannot figure out one of the steps above or do not get the result I've described, absolutely do not skip that step -- every step is important. If you do struggle at any point or find a step to go differently than described above, make sure you screenshot the steps you took up to that point and upload them here so I can understand exactly what actions you've taken and what you're seeing.

[OrtiMussPrime]

Hi @coddingtonbear thanks for the comprehensive guide.
I followed them step-by-step but none of these seem to work for me.

Any ideas why?
obsidian-local-rest-api.bug_report.json

[jonasqin]

Thanks so much for your patient reply! But my problem is still exists, here is the possible difference when I do as what you suggest:
"Go back into Obsidian Local REST API's settings and find the link for downloading the current certificate. Click the link and download the certificate."
When I enable Unencrypted Server and turn off the "Enable Encrypted(HTTPs) Server", I couldn't download the certificate cause the link is start with "https". So I turn on the button to download certificate and turn it off after download. I don't know if it's making an impact...

[coddingtonbear]

That certificate should be fine.

Are you confirming, then, that you saw the blue icon instead of the green one during step 3? If so -- can you show me a screenshot of that to make sure you're seeing the icon I expect?

[jonasqin]

I did see the blue plugin button first and then the green shield button. But after a reboot, I found that I can use your plugin normally today. I appreciate your detailed explanation!

[coddingtonbear]

Oh, well, it's interesting that you would have to reboot. I wonder if that's something all WIndows users need to do before the certificate will be trusted?

[jonasqin]

I am using your extensions on two PCs and one Mac. I only used one recently, so I guess maybe I will encounter the same problem when using the others. If there is any problem, I will give you feedback.