paperless icon indicating copy to clipboard operation
paperless copied to clipboard

New User Issue: Can't log into web server

Open dan-todd opened this issue 5 years ago • 5 comments

Hi,

Highly likely that I've missed a step, but I've followed the docker installation instructions and successfully got the set up running after creating a superuser. Unfortunately, I can't then use those credentials to log in.

Any assistance will be greatly appreciated!

Dan

dan-todd avatar Oct 31 '19 09:10 dan-todd

I had the same issue after setting it up, but found a workaround First run the createsuperuser Then:

docker exec -it < containerid > bash ./manage.py changepassword < your_user >

After doing this, I was able to login to the web admin with the specified user.

Running ./manage.py createsuperuser left me with the same issue, unable to login to web admin User paperless didn't exist.

veloc1ty avatar Nov 07 '19 10:11 veloc1ty

had the same issue, and the workaround above didn't work either. had to exec into the container and run createsuperuser again.

it seems like the docker compose run command runs in a ephemeral webserver container instead of using the existing one.

You can just use docker exec -it paperless_webserver_1 ./manage.py createsuperuser

sbaier1 avatar Jan 19 '20 10:01 sbaier1

Thanks @sbaier1 , that works. It does not remain after restarting the docker container, though. I see the /data and /media folders inside the container not being used, so there must be something going wrong with the internal paths.

vhaasteren avatar May 13 '20 16:05 vhaasteren

Thanks @sbaier1 , that works. It does not remain after restarting the docker container, though. I see the /data and /media folders inside the container not being used, so there must be something going wrong with the internal paths.

Do you use docker-compose? Could you paste your yml? Especially the volumes: bit

totti4ever avatar May 14 '20 18:05 totti4ever

The issue was that paperless.conf needed to have PAPERLESS_DBDIR=/data/ commented out. I am not sure what it was defaulting to, but it was not something that worked. Once loaded the config file and set the DBDIR it all worked.

vhaasteren avatar May 14 '20 22:05 vhaasteren