Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] API cannot be saved correctly when using custom LLM #285

Open
wwjCMP opened this issue May 3, 2024 · 7 comments
Open

[Bug] API cannot be saved correctly when using custom LLM #285

wwjCMP opened this issue May 3, 2024 · 7 comments

Comments

@wwjCMP
Copy link

wwjCMP commented May 3, 2024

The API used is very long, and I'm not sure if that's what's causing the issue.

@nhaouari
Copy link
Owner

nhaouari commented May 4, 2024

more details please to reproduce the issue

@wwjCMP
Copy link
Author

wwjCMP commented May 5, 2024

I believe that only three things are needed to reproduce this issue:

  1. Use a custom LLM provider
  2. Use a long api key
  3. Restart obsidian

@stisa
Copy link

stisa commented May 22, 2024

Same issue here. Even when saving the profile, the key is not there on restart. Re-importing the profile also doesnt import the key.

@calmwaves111
Copy link

+1,i also meet this issue

@fry69
Copy link

fry69 commented May 31, 2024

I can confirm that custom provider API keys do not survive a restart of Obsidian or a plugin reload. (Also tested with 0.7.19-beta)

Update with workaround:

  1. Make sure your key(s) are in place and work.
  2. Under "Text Generator Options" in the settings for Textgenerator there is a toggle for "Keys encryption". Toggle this option on.
  3. After adding or changing a key, toggle above option off and then on again to update the keys on disk.

@fry69
Copy link

fry69 commented Aug 4, 2024

2031843 (included in release 0.7.27+) seems to have fixed this issue, at least for me.

@secastles
Copy link

This just happened to me in 0.7.28.

  1. Using Azure OpenAI Chat with the following parameters filled: Api key, Endpoint, Deployment name, API version.
  2. Confirmed working yesterday.
  3. Computer put to sleep overnight (plugin not reloaded manually and Obsidian was not shutdown).
  4. Today all parameters are gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants