Skip to content
This repository has been archived by the owner on Feb 13, 2022. It is now read-only.

Login 404s #51

Open
galaxor opened this issue Jan 7, 2018 · 0 comments
Open

Login 404s #51

galaxor opened this issue Jan 7, 2018 · 0 comments

Comments

@galaxor
Copy link
Contributor

galaxor commented Jan 7, 2018

So, I got a backend (neutron) running and I got a frontend (the forked WebClient) running. But any attempt to authenticate results in a 404 from the backend.

[Macaron] 2018-01-07 21:26:47: Started OPTIONS /api/auth/info for 172.17.0.1
[Macaron] 2018-01-07 21:26:47: Completed OPTIONS /api/auth/info 404 Not Found in 127.443µs
[Macaron] 2018-01-07 21:26:47: Started OPTIONS /api/bugs/crash for 172.17.0.1
[Macaron] 2018-01-07 21:26:47: Completed OPTIONS /api/bugs/crash 404 Not Found in 112.76µs

That's using a username and password that authenticate just fine in my IMAP client.

Also, I created a gpg public/private keypair neutron/db/keys/<my-domain>.org/<my-username>.{pub,priv}.gpg

Is there something else I have to do to make neutron able to authenticate me?

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

No branches or pull requests

1 participant