Can't login to Community Edition

[drumwhizz]

I have successfully followed the setup instructions for deploying the self hosted shellhub service (v0.10.9) locally on my Ubuntu desktop. I have created my first user and namespace, but every time I try and login to the service (with my credentials) I get a small dialog popping up saying "The request has failed. Please try again". It does this even if I type in rubbish into the username and password.

I have had a look in the logs but are none the wiser as to what to look for.

[drumwhizz]

phil@phil-desktop:~/shellhub$ cat docker-compose.override.yml
version: '3.7'
services:
mongo:
volumes:
- /usr/local/mongo/data:/data/db

[henrybarreto]

Hello, Phil!

Thank you for reporting it. I'm working on this issue now.

Could you check your user on MongoDB database?

 ./bin/docker-compose exec mongo mongo main --eval "db.users.find()"

If it's okay, could you share the request logs what have happened?

[henrybarreto]

Could you stop everything and start again instead of restart? I believe it will load the env variables and fix it.

./bin/docker-compose stop && ./bin/docker-compose up

[drumwhizz]

Here is the log..
shellhub-log.txt

[henrybarreto]

Okay, it is a bit strange...

Could you post here the API container envs?

./bin/docker-compose exec api env

[drumwhizz]

phil@phil-desktop:~/shellhub$ ./bin/docker-compose exec api env
INFO: Loading ./.env.override
Error response from daemon: Container b31e3965f1ae4f66b8d5657fea26c77ecf546aa98a4ca5ad6530cdbf89ae6ce4 is restarting, wait until the container is running

[drumwhizz]

The api is stuck in a restart cycle

api_1 | time="2023-01-06T08:01:03Z" level=info msg="Setting log level" log_level=info
api_1 | time="2023-01-06T08:01:03Z" level=info msg="Starting Sentry"
api_1 | time="2023-01-06T08:01:03Z" level=fatal msg="Failed to initialize Sentry" error="[Sentry] DsnParseError: invalid scheme"
api_1 | time="2023-01-06T08:01:29Z" level=info msg="Setting log level" log_level=info
api_1 | time="2023-01-06T08:01:29Z" level=info msg="Starting Sentry"
api_1 | time="2023-01-06T08:01:29Z" level=fatal msg="Failed to initialize Sentry" error="[Sentry] DsnParseError: invalid scheme"
api_1 | time="2023-01-06T08:02:21Z" level=info msg="Setting log level" log_level=info
api_1 | time="2023-01-06T08:02:21Z" level=info msg="Starting Sentry"
api_1 | time="2023-01-06T08:02:21Z" level=fatal msg="Failed to initialize Sentry" error="[Sentry] DsnParseError: invalid scheme"
api_1 | time="2023-01-06T08:03:21Z" level=info msg="Setting log level" log_level=info
api_1 | time="2023-01-06T08:03:21Z" level=info msg="Starting Sentry"
api_1 | time="2023-01-06T08:03:21Z" level=fatal msg="Failed to initialize Sentry" error="[Sentry] DsnParseError: invalid scheme"

[drumwhizz]

phil@phil-desktop:/shellhub$ ./bin/docker-compose exec mongo mongo main --eval "db.users.find()"
MongoDB shell version v4.4.8
connecting to: mongodb://127.0.0.1:27017/main?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("99ca9ef1-ece9-41af-a714-4b89d3e3a4ef") }
MongoDB server version: 4.4.8
{ "_id" : ObjectId("63b69fee386663b53c645f10"), "max_namespaces" : -1, "confirmed" : true, "created_at" : ISODate("2023-01-05T10:01:18.058Z"), "last_login" : ISODate("0001-01-01T00:00:00Z"), "name" : "phil", "email" : "[email protected]", "username" : "phil", "password" : "2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b", "namespaces" : 3 }
{ "_id" : ObjectId("63b6afbf053bdac67f8cf236"), "max_namespaces" : -1, "confirmed" : true, "created_at" : ISODate("2023-01-05T11:08:47.364Z"), "last_login" : ISODate("0001-01-01T00:00:00Z"), "name" : "phil", "email" : "[email protected]", "username" : "phil", "password" : "2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b" }
{ "_id" : ObjectId("63b6b51fa1dc220626a2a9f4"), "max_namespaces" : -1, "confirmed" : true, "created_at" : ISODate("2023-01-05T11:31:43.669Z"), "last_login" : ISODate("0001-01-01T00:00:00Z"), "name" : "phil", "email" : "[email protected]", "username" : "phil", "password" : "2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b" }
phil@phil-desktop:~/shellhub$

[otavio]

@henrybarreto and I are looking at this, and we are wondering how you ended with three users with the same email. Below is a snippet of your response:

{ ..."created_at" : ISODate("2023-01-05T10:01:18.058Z"), ..., "namespaces" : 3 }
{ ..."created_at" : ISODate("2023-01-05T11:08:47.364Z"), ... }
{ ..."created_at" : ISODate("2023-01-05T11:31:43.669Z"), ... }

So we'd like to know how you did the installation in detail. You are using MongoDB with an external storage directory for persistence. Have you reused an existing database from an older tag, or did you start the installation directly inside the 0.10.9 tag?

[drumwhizz]

I restarted the container and repeated the processes of configuring the database 3 times. I could not see any files in the host DB directory and assumed that mongo writes were not working.

[drumwhizz]

WRT, the database, my recollection is that I pulled the tip of the repo and attempted to build it but it failed due to the fact you have made breaking changes with the new_ui. I then checked out the v0.10.9 tag and restarted the service successfully.

[henrybarreto]

@drumwhizz, I have reproduced that problem locally. I'm working directly on it now.

[henrybarreto]

@drumwhizz, the problem seems to be with the docker-compose version what you are using.

I'm assuming you are using the Ubuntu 20.04, sorry.

Looking for the docker-compose package on your distro, I've checked that this version, 1.25.0, doesn't support empty ("") strings as null on .env.

To work around that issue, you can run that script. It'll remove all "" from the .env, allowing the API server to run normally.

sed -i 's,"",,g' .env

[drumwhizz]

I have just tried this and it has made no difference to the behaviour.

[henrybarreto]

@drumwhizz, could you access our gitter for a better conversation?

https://gitter.im/shellhub-io/community