[bug]: Provided default application user name and password don't work

[andy47]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current behavior

When I have the application running via docker on my laptop I can't log into the application using the default user name and password provided on https://docs.plane.so/self-hosting

The login fails and I see this pop-up error message;

Steps to reproduce

1. Start the application using docker-compose up
2. Go to the application sign in page (on my machine that is http://localhost:8005/signin )
3. Attempt to login with the default user name and password supplied on https://docs.plane.so/self-hosting
4. Login fails.

Environment

Deploy preview

Version

Self-hosted

[airdogvan]

same here

[sphynxux]

Thanks for reporting this @andy47, @airdogvan. We are working on fix for this with high priority. We'll revert back soon.

[galaris]

same

[pablohashescobar]

We have fixed the above issue in our develop branch we are still aggressively testing it and fixing any bugs.

[vihar]

Related to #477.

[soxrok2212]

Still seeing this bug on develop branch

[tkerr97]

Same issue here, clicking on forgot password shows "Setting up you workspace" forever

[pablohashescobar]

Greetings everyone, I am the maintainer of Plane. I would like to inform you that the error you have encountered has been resolved in our latest development branch. In order to successfully apply this fix, kindly delete all volumes, network, and the container itself. After which, please proceed with rebuilding the images. Thank you.

[tkerr97]

Unless you leave the nginx port at 80, you still get the error (it appears to be CORs related). It would be nice to be able to change the port, since I have another docker container on my machine that I would rather have that port.

[andy47]

Same problem here as @tkerr97 reports.

I already have services running on port 80 and 3000 on the host machine. So I changed nginx to run on port 8005 and plane-web to run on port 3003.

Same error message.

[pablohashescobar]

Hey, can you also please try by updating the Dockerfiles for both backend and frontend Dockerfile.api and Dockerfile.web also the compose as well.

[tkerr97]

On a clean machine I did the following:

1. Cloned the repo
2. Ran setup.sh with my IP
3. Edited the docker-compose.yml to have the port I want
4. Ran docker-compose up
5. Attempted to login with the default username and password and still got the error

[heromiyo]

same

[galaris]

Develop branch solved for me, but I needed to run this to force a rebuild: docker compose up --build

Thanks to n1kh1l!

[ghost]

Still getting this error when changing the nginx port in docker-compose.yml to - 4000:80 as I can't use port 80 on my machine.

[heromiyo]

am still getting this error after doing all the suggested options, this is what i see in the logs nginx | 172.18.0.1 - - [19/Apr/2023:09:34:22 +0000] "POST /api/sign-in/ HTTP/1.1" 502 559 "http://localhost/signin" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36" nginx | 2023/04/19 09:34:22 [error] 23#23: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "POST /api/sign-in/ HTTP/1.1", upstream: "http://172.18.0.2:8000/api/sign-in/", host: "localhost", referrer: "http://localhost/signin"

[pablohashescobar]

Hi @heromiyo are you running this on cloud server or local system and also can you please specify which branch are you in.

[heromiyo]

for error above it was locally on windows but i have deployed the same app on the cloud VM and the branch is develop for both and for the cloud VM one i just cloned the repo just now and did the README step by step https://80-port-c649136594064ade.labs.kodekloud.com/signin

[heromiyo]

please use https://80-port-c649136594064ade.labs.kodekloud.com/signin to test login using default credentials @pablohashescobar

[pablohashescobar]

Hey @heromiyo can you check if the backend container is running

[heromiyo]

it is, here is a terminal you can use to check aswel @pablohashescobar
https://terminal-c649136594064ade.labs.kodekloud.com/

[pablohashescobar]

Hey @heromiyo all the containers are running. The problem is the frontend container is trying to access localhost for API.

Can you please run the setup script again ./setup.sh https://80-port-c649136594064ade.labs.kodekloud.com again. Then please rebuild all the containers using docker compose up --build. Please let us know if the problem still persist

[heromiyo]

@pablohashescobar still there but the api url is updated https://80-port-c649136594064ade.labs.kodekloud.com/signin

[heromiyo]

and also fails on localhost

[pablohashescobar]

Hi @heromiyo it would be awesome if you could send your envs at apiserver/.env and apps/app/.env and also the nginx configuration.

[pablohashescobar]

Hello everyone,

We have updated our docker setup and now have pushed pre-built images to DockerHub as well which can be used by using docker-compose -f docker-compose-hub.yml up. Detailed docs can be found here https://docs.plane.so/self-hosting

[HearthCore]

Wonder if a comment will reopen this.

I've cloned the lasted -dev branch, clean setup, still incorrect password for default admin user.

[pablohashescobar]

Hey @HearthCore it would be awesome if you could share browser network logs and docker logs as well.

[Alcatraz077]

I've ran into this as well. Brand new Ubuntu 22.04 box. I'll gladly provide docker logs, but which containers? All of them?

As for network logs, when I attempt to login with the default creds, it sends the following headers:

OPTIONS /api/sign-in/ undefined
Host: localhost
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/113.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Access-Control-Request-Method: POST
Access-Control-Request-Headers: content-type
Referer: http://plane:3000/
Origin: http://plane:3000
DNT: 1
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site

With the response of:

Response body is not available to scripts (Reason: CORS Failed)

[shadowjig]

When will this fix be deployed to the docker images on hub.docker.com