feathersjs-ecosystem / feathers-chat-ts

A Feathers real-time chat application in TypeScript
MIT License
54 stars 25 forks source link

Can`t login, get error: "There was an error: Invalid login" #45

Closed igorgidea closed 4 years ago

igorgidea commented 4 years ago

When i try sign up and login i get error { "name": "NotAuthenticated", "message": "Invalid login", "code": 401, "className": "not-authenticated", "errors": {} }

Steps to reproduce

  1. Clone the chat repository (typescript version) and cd into it
  2. install dependencies, run npm i
  3. run npm start
  4. Enter email and password and press "Sign up and log in" button as result get error

    System configuration

    NodeJS version: v12.18.0 Operating System: Windows 10 x64 Browser Version: Google Chrome version 83.0.4103.97

daffl commented 4 years ago

Try removing the data folder and restarting the application. The process also needs permissions to write to the current folder.

igorgidea commented 4 years ago

I have deleted data directory, restart the application, try again doing sign up and login, but still no luck изображение "data" directory has been created and fulfilled with user data: изображение

igorgidea commented 4 years ago

Additionally, I tried to generate a new project with authorization using feathers cli and I get the same error - I can’t log in. By the way, everything works under Ubuntu.

daffl commented 4 years ago

That's why I said it is probably a file permission issue. The data folder needs to be writeable by the Node process.

igorgidea commented 4 years ago

In my comment above i wrote that "data" directory has been created and fulfilled with user data i suppose its means Node process can write, is it? How can I verify that feathers have a problem with permissions? I hope there are no reason for permission problems, many others nodejs application works just fine on my windows 10 some of them works with files all projects placed inside one root folder.

daffl commented 4 years ago

Or read it. Since this is the first time I'm seeing this, I'm fairly sure it is a permission problem.