SIGSEGV with latest dnote client and selfhosted server about dnote

[kimusan]

just tested with cli v0.11.1 and the problem also exists there.

[sungwoncho]

Hi @kimusan, I'll have a look sometime soon, in the meantime:

• does the problem persist with Dnote server v1.0.4?
• could you try to set apiEndpoint to [insert base url to your dnote instance]/api in .config/dnote/dnoterc (instead of simply [insert base url to your dnote instance])

[kimusan]

Seems to happen with both 1. 0.4 and 2.0.1 and both the old and new cli.
I wonder if it is the ngnix I have in front that somehow get it to break. The ssl cert is currently expired so maybe that can get things to explode.
The Web interface works just fine on the server.

Also tried with /api and also with :3000/api but no luck.

BTW: is it on purpose the new cli uses the old location for the dnotesrc file? I thought it was weird that it did not identify my changes when I changed the api url in ~/.config/dnote/dnoterc. Strace showed it tried to open ~/.dnote/dnoterc

[sungwoncho]

The ssl cert is currently expired

I think this is the root cause. I admit that the error handling could be improved, and opened #603 to track the improvement.

Would you be able to try to renew your SSL cert? Or you could use http rather than https to get unblocked in the short term.

is it on purpose the new cli uses the old location for the dnotesrc file?

Yes, it is intentional for v0.12.0. If the old location exists, CLI will use that location for backward compatibility (https://github.com/dnote/dnote/blob/master/CHANGELOG.md#0120---2020-01-03).

[kimusan]

Finally got around to test it with a new ssl cert (the nginx setup was a bit funky so it required a bit of a hack). This is indeed the problem causing the SIGSEGV and now I can login and search my notes again.

[sungwoncho]

Thanks for the update. Closing this and keeping #603 open as an improvement.

More notes on the removal of the web interface: it was removed to lengthen the project's lifespan by simplifying the features and reducing complexity. Since API is stable, maybe a simplified version could be offered as a non-official client in the future. Please let me know about any thoughts.