Admin CLI is broken #13
Comments
|
Same problem for me also.. I noticed that at this point - nsecBunker generated an admin password for you: So think maybe it bugged out somewhere there |
|
yeah, I think when I added the web admin stuff I destroyed the CLI admin stuff. Need to revisit this. |
|
can confirm that the admin CLI not working for me either. I get that same message with the red x when I try to set it up to get into highlighter.com. I'm running it on an uberspace.de asteroid which is some flavor of linux and node js 18 |
|
I had to manually add the admin npub to config/nsecbunker.json, even though I had already added it to the .env. When I start up the CLI, I get: But then: |
|
@jeremycady Does it work then, when you have added it? 🤔 You have added it in .env and other file.. would you mind to show us which fields did you fill? Thanks |
|
My steps to, what appears to be, working CLI: Update DATABASE_URL to correct "nsecbunkerd/prisma/nsecbunker.db" npm install Add npub to admin.npubs npm run lfg --admin npub This yields this error at first: Gives me a connection string. Provides a signing. Then the following output: I can now log into app.nsecbunker.com and unlock my key, create a policy and a token. I haven't been able to log into anything using this though. For example, at coracle.social, when you but in the bunker URL to login, it will give me the following error in the console: I get no feedback from Nostrudel. I have noticed, in the CLI, every event has "sig: undefined". I'm not sure if that's in an issue or not. |
|
I forgot to add, I do get a DM when the bunker starts that states: |
|
Also, I just downloaded and ran the UI locally. I've logged into and posted at nostrudel.ninja |
After I entered my nsec the process ends and doesn't provide me an admin password.
When I run
$ npm run nsecbunkerd startI get this:The text was updated successfully, but these errors were encountered: