Cannot log in - credentials invalid / user not found

[DerDomml]

Hey folks,

I have just tried to run freescout using the example docker-compose.yml file (without proxy). I have adjusted all variables that seemed relevant to me, such as the domain name, admin email and admin password. When I start the compose it all looks fine. I then access the website via the domain which works like a charm, try to log in with the credentials specified in the ADMIN_MAIL and ADMIN_PASS environment variables but freescout tells me "These credentials do not match our records". When I hit "Forgot your password?" and enter my email, it tells me no user with that address has been found.

Am I doing something obviously wrong that I cannot see?

My docker-compose.yml looks like this:

version: '2'

services:
  freescout-app:
    image: tiredofit/freescout
    container_name: freescout-app
    ports:
    - 80:80
    links:
    - freescout-db
    volumes:
    ### If you want to perform customizations to the source and have access to it, then uncomment this line - This includes modules
    #- ./data:/www/html
    ### Or, if you just want to use Stock Freescout and hold onto persistent files like cache and session use this, one or the other.
    - ./data:/data
    ### If you want to just keep the original source and add additional modules uncomment this line
    - ./modules:/www/html/Modules
    - ./logs/:/www/logs
    environment:
    - CONTAINER_NAME=freescout-app
    - DB_HOST=freescout-db
    - DB_NAME=freescout
    - DB_USER=freescout
    - DB_PASS=freescout
    - SITE_URL=http://myfreescoutserver.net/
    - ADMIN_EMAIL=user@maildomain.com
    - ADMIN_PASS=apassword
    - ENABLE_SSL_PROXY=FALSE
    - DISPLAY_ERRORS=TRUE
    - TIMEZONE=Europe/Berlin
    restart: always
  freescout-db:
    image: tiredofit/mariadb
    container_name: freescout-db
    volumes:
      - ./db:/var/lib/mysql
    environment:
      - ROOT_PASS=password
      - DB_NAME=freescout
      - DB_USER=freescout
      - DB_PASS=freescout
      - CONTAINER_NAME=freescout-db
    restart: always
  freescout-db-backup:
    container_name: freescout-db-backup
    image: tiredofit/db-backup
    links:
     - freescout-db
    volumes:
      - ./dbbackup:/backup
    environment:
      - CONTAINER_NAME=freescout-db-backup
      - DB_HOST=freescout-db
      - DB_TYPE=mariadb
      - DB_NAME=freescout
      - DB_USER=freescout
      - DB_PASS=freescout
      - DB_DUMP_FREQ=1440
      - DB_DUMP_BEGIN=0000
      - DB_CLEANUP_TIME=8640
      - COMPRESSION=BZ
      - MD5=TRUE
    restart: always

[tiredofit]

It looks like you are certainly doing all the right things. Do you see a user entry if you performed a SQL query in the database?

Try this:

docker exec -it freescout-db bash
mysql -u$DB_USER -p$DB_PASS $DB_NAME
select * from users;

You should see your username and password that was created. If not, I'll ask for a fresh install with full logs using an environment variable of CONTAINER_LOG_LEVEL=DEBUG and ask a few details like your environment running.

[Chovija]

Hi. i had the same exact problem with a new installation: server: ubuntu 22.04 LTS php: 8.1.2 for instalation i had used ubuntu script: https://raw.githubusercontent.com/freescout-helpdesk/scripts/master/install/ubuntu.sh

Everything looks ok. but after initial setup, looks like no user was really created during GUI setup.

[tiredofit]

Hi. i had the same exact problem with a new installation: server: ubuntu 22.04 LTS php: 8.1.2 for instalation i had used ubuntu script: https://raw.githubusercontent.com/freescout-helpdesk/scripts/master/install/ubuntu.sh

Everything look ok. but after initial setup, looks like no user was realy created during GUI setup.

Please use https://github.com/freescout-helpdesk/freescout/issues for issue reporting for anything related to the install scripts. This is purely for the Docker image.

[mjrascoe]

Has anyone found a solution to this? I am having the same exact issue

[maxXx1]

I have same issue :/

[fatelgit]

I was setting up freescout on a kubernetes cluster and had the same issue because I was messing around with a proper database user and had connection issues to my database first. After fixing that the script was running successfully but there was no user so I just dropped the database again and killed/restarted the according pod and now there has been a user created. I think the issue is related to having some troubles on setup and setup scripts that will not run completely.