# Login Failed With Invalid Request After Clean Installation **URL:** \ **Category:** Pydio Cells\ **Tags:** install\ **Created:** [May 3, 2021, 8:41am UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841 "2021-05-03T08:41:25Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![mrsylerpowers](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/mrsylerpowers/32/1417_2.png) [@mrsylerpowers](https://forum.pydio.com/u/mrsylerpowers)\ **Post date:** [May 3, 2021, 8:41am UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/1 "2021-05-03T08:41:25Z")
I believe I have a similar issue to the one mentioned here. [Login Failed with invalid\_request after clean installation](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3766) My Docker compose setup like this ```auto version: '3.7' services: nginx: image: nginx:latest restart: always ports: - "80:80" - "443:443" container_name: production_nginx volumes: - ./nginx.conf:/etc/nginx/nginx.conf - ./certs:/etc/wwwcerts/ - ./letsencrypt.conf:/etc/nginx/snippets/letsencrypt-acme-challenge.conf - ./letsencrypt/:/etc/letsencrypt/ # Cells image with two named volumes for the static and for the data cells: image: pydio/cells:latest restart: always hostname: cells volumes: - G:\\piyio\\cells\\:/var/cells:rw - G:\\piyio\\extrafiles:/extrafiles extra_hosts: - "HAMJONES-PC:192.168.3.194" environment: - "VIRTUAL_HOST=subdomain.yourdomain.tld" - "LETSENCRYPT_HOST=notafraid.app" - CELLS_BIND=cells:8080 - CELLS_EXTERNAL=web.notafraid.ngrok.io - COMPOSE_CONVERT_WINDOWS_PATHS=true - CELLS_LOG_LEVEL=production # MySQL image with a default database cells and a dedicated user pydio mariadb: image: mariadb:10.3 ports: ["3306:3306"] restart: always environment: MYSQL_ROOT_PASSWORD: 1nLUOGtfhojfyzZPfrsc MYSQL_DATABASE: cells MYSQL_USER: pydio MYSQL_PASSWORD: CxWe86c52htaHWaJjCaH command: [mysqld, --character-set-server=utf8mb4, --collation-server=utf8mb4_unicode_ci] smtp: image: namshi/smtp:latest restart: always ports: - "587:587" environment: - "KEY_PATH=/etc/certs/domain-key.pem" - "MAILNAME=notafraid.app" - "CERTIFICATE_PATH=/etc/certs/domain-crt.pem" - "SMARTHOST_ADDRESS=smtp" - "SMARTHOST_PORT=587" - "SMARTHOST_USER=myuser" - "SMARTHOST_PASSWORD=secret" - "SMARTHOST_ALIASES=smtp" volumes: - ./certs:/etc/certs/ volumes: data: {} ``` And all of my [logs](https://pastebin.com/HFZVqfJR) up until I have that error. This is after a clean install with no files saved on my computer. I have tried almost everything. The only thing that works is using a different version (older) ---
**Author:** ![nrze175](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/nrze175/32/1448_2.png) [@nrze175](https://forum.pydio.com/u/nrze175)\ **Post date:** [May 11, 2021, 9:33pm UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/2 "2021-05-11T21:33:46Z")
I’m having the exact same issue here, clean install with docker-compose, only difference to the demo-file is, that I added “CELLS\_NO\_TLS=1” as environment variable, otherwise 100% the same as [here](https://hub.docker.com/r/pydio/cells/?hsCtaTracking=c2601985-fbba-44a6-8b97-ae6949140b53%7Cf1dac0cb-4a1b-471b-99c8-8c11946ae4bb) I also tried to just docker-compose down and up again, as described in the other post reporting this Issue (OP linked that one), but that didn’t work for me. The Installer worked without problems though. I think this is an issue with the official Docker image, maybe in combination with compose - it seems to simply not work out of the box but it’s also very hard to debug without having deep pydio knowledge, since the error doesn’t provide useful information. Can someone please help here? ---
**Author:** ![nrze175](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/nrze175/32/1448_2.png) [@nrze175](https://forum.pydio.com/u/nrze175)\ **Post date:** [May 16, 2021, 7:19pm UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/3 "2021-05-16T19:19:47Z")
Posted on GitHub now: [Admin login in docker image not possible · Issue #323 · pydio/cells · GitHub](https://github.com/pydio/cells/issues/323) ---
**Author:** ![zayn](https://avatars.discourse-cdn.com/v4/letter/z/a87d85/32.png) [@zayn](https://forum.pydio.com/u/zayn)\ **Post date:** [May 17, 2021, 10:40am UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/4 "2021-05-17T10:40:07Z")
Hello @mrsylerpowers , could you share your nginx configuration (make sure to hide sensitive info). Also could you try to run your setup without a reverse proxy and see if the login request still fails? ---
**Author:** ![mrsylerpowers](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/mrsylerpowers/32/1417_2.png) [@mrsylerpowers](https://forum.pydio.com/u/mrsylerpowers)\ **Post date:** [May 17, 2021, 12:40pm UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/5 "2021-05-17T12:40:44Z")
Hello @zayn, Here is my nginx configuration ``` events { worker_connections 4096; ## Default: 1024 } http { server { server_name web.notafraid.ngrok.io listen 80; listen [::]:80; listen 443 default_server ssl; resolver 127.0.0.11 ipv6=off; ssl_protocols TLSv1.2 TLSv1.3; include /etc/nginx/snippets/letsencrypt-acme-challenge.conf; location / { proxy_buffering off; client_max_body_size 100G; proxy_pass https://cells:8080$request_uri; #proxy_pass_request_headers on; #proxy_set_header Host $host; proxy_set_header Content-Security-Policy upgrade-insecure-requests; proxy_set_header X-Real-IP $remote_addr; # Redirect non-https traffic to https if ($scheme != "https") { return 301 https://$host$request_uri; } # managed by Certbot } location /ws { proxy_buffering off; proxy_pass https://cells:8080; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_read_timeout 86400; } ssl_prefer_server_ciphers on; ssl_ciphers "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH EDH+aRSA RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS"; ssl_certificate /etc/wwwcerts/domain-crt.pem; # managed by Certbot ssl_certificate_key /etc/wwwcerts/domain-key.pem; # managed by Certbot } } ``` ---
**Author:** ![mrsylerpowers](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/mrsylerpowers/32/1417_2.png) [@mrsylerpowers](https://forum.pydio.com/u/mrsylerpowers)\ **Post date:** [May 28, 2021, 2:55am UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/6 "2021-05-28T02:55:31Z")
Hello @zayn Even after removing my remote proxy I am still running into the same problem. With the exact same error. No NGIX ---
**Author:** ![nrze175](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/nrze175/32/1448_2.png) [@nrze175](https://forum.pydio.com/u/nrze175)\ **Post date:** [June 21, 2021, 10:53am UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/7 "2021-06-21T10:53:16Z")
So… I guess it’s building the docker image from scratch then as the provided one is not working and seems to be not maintained/tested ---
**Author:** ![bsinou](https://yyz2.discourse-cdn.com/flex032/user_avatar/forum.pydio.com/bsinou/32/476_2.png) [@bsinou](https://forum.pydio.com/u/bsinou)\ **Post date:** [June 21, 2021, 1:47pm UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/8 "2021-06-21T13:47:03Z")
> [@nrze175](#): > > I guess it’s building the docker image from scratch then Feel free. As a starting point, the code is in the github repo under `tools/docker/images/cells`. We would be glad to hear about your comments / feedback / ideas. > [@nrze175](#): > > the provided one is not working and seems to be not maintained/tested Let’s agree to disagree on this one, we _try our best_ (as in FOSS) to maintain it and massively use the image in internal testing environments. To be sure, I just spinned of a new docker-compose environment on a web facing VM and could launch the env, run the install and login without issue, after accepting the self-signed certificate for [https://example.com:8080](https://example.com:8080) Thus said, a few ideas to further diagnose your issue: - are you behind a reverse proxy (this thread was about nginx at some point) ? - do you have any log in Cells when you unsuccessfully try to login with the admin user after install ? - have you tried to run `docker-compose exec cells cells configure sites` (the 2 “cells” are necessary, one for the name of the image in docker compose, one to call the binary inside it) to check if the Cells’ internal webserver is correctly configured ? - what happens if you do `docker-compose restart cells` while checking the logs ? ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex032/uploads/pydio/original/2X/6/61f19fa52ec15fd4250db51aea351adba0e831fd.png) [@system](https://forum.pydio.com/u/system)\ **Post date:** [July 26, 2021, 1:48pm UTC](https://forum.pydio.com/t/login-failed-with-invalid-request-after-clean-installation/3841/9 "2021-07-26T13:48:02Z")
This topic was automatically closed 35 days after the last reply. New replies are no longer allowed.