We're evolving to serve you better! This current forum has transitioned to read-only mode. For new discussions, support, and engagement, we've moved to GitHub Discussions.

unable to save my server setting even with a new site

June 9, 2020 at 12:15 pm #2995

[anonymous]

Publii: v.0.35.3 (build 12104) Beta

Add a new website

go to Server

I tried with FTP, FTPS, Github, Netlify

the only one working is Manual Deployment

June 9, 2020 at 12:41 pm #2996

[anonymous]

I just updated to Publii
<p class=”about-version” data-v-10417b9b=””>v.0.36.0 (build 13213) beta</p>
<p data-v-10417b9b=””>and the issue remains</p>

June 11, 2020 at 11:44 am #3004

[anonymous]

Hi,

You have no notification that the site settings has been saved. I suppose that you are using a linux version of Publii and you have no libsecret package, which is required by Publii to safely store passwords. Please install the missing package: https://github.com/atom/node-keytar#on-linux and please try again.

I will check what can be a reason of the silent fall back in this case to avoid such no error cases in the future 🙂

June 26, 2020 at 9:41 am #3155

[anonymous]

Hi, i have a similar issue and installed the suggested package but it doesnt seem to resolve the issue , is there anything that needs to be done apart from this ?

i am on debian 10 buster under the 4.19 kernel using publii v.0.36.1 (build 13320) beta

June 26, 2020 at 10:18 am #3156
[anonymous]
Tried starting the app from terminal which helped me identify the issue, these were the errors
```
Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
(node:6205) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files
(node:6205) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
```
I can confirm that `sudo apt install gnome-keyring` solves the problem on KDE. Looks like the problem is with `node-keytar`. Thanks for the support and pointers till now

Note :- problem solved by installing `sudo apt install gnome-keyring` on debian 10 kde