Trying to register first connect but returns 500 Internal Server Error

[plckr]

Type: Bug Report

• [x] Try to follow the update procedure described in the README and try again before opening this issue.

Your Environment

• Version used:
  • Version (stable release) - latest (4.6.1)
  • Commit ID (development release) git --no-pager log -1 - 3563344dc2e33da69e518e4d222990c616e6079d
• Environment name and version:
  • Node.js version node --version - v14.17.6
  • npm version npm --version - 6.14.15
  • Web browser name and version - Chrome Version 93.0.4577.63 (Official Build) (64-bit)
• Operating system and version: Windows 10
• Torrent client and version: Rtorrent 0.9.8

Summary

First init of the flood installation requires to register, I fill everything:

• User, password, client (rtorrent), socket, socket_path

When I click on submit, it returns Request failed with status code 500 Checking the dev tools, the response is: {"message":""}

On flood process it shows the following line: POST /flood/api/auth/register 500 166.171 ms - 14

Expected Behavior

Should register the account and redirect to next page, or atleast give a more specific error

Current Behavior

Possible Solution

Steps to Reproduce

1. npm run start
2. go to flood url defined
3. insert data
4. submit

Context

EDIT: passing --rtsocket '~/.rtsocket' --auth none works but misses the Login page

[ronilaukkarinen]

I have the same problem. Have to use htpasswd auth.

[ronilaukkarinen]

Because cannot register via user interface, is it possible to add login settings in some file etc.? htpasswd auth is frustrating because it pops up every time after I close the page.

[ronilaukkarinen]

Have tried everything and nothing worked. I even registered successfully on different server, then moved the db folder to the server in question that has this issue, then tried to login and getting 401 or 500... extensively configured nginx separately for /api but no luck there either.

I have no idea what causes this 500 and registrer/auth not to work. With --auth none everything works fine.

Ended up installing Flood to a separate VPS. Very strange issue with empty response: {"message":""}

[humorousnumerous]

same issue here, can't figure it out.