Can't get ACCESS_KEYS to restrict page

[thistletea]

I used option #2 to setup, create .env with ACCESS_KEYS="test", and ran docker-compose --env-file .env up. I'm still able to access the page without prompt for password.

[felladrin]

Hi, @thistletea!

I tried to reproduce it, but I couldn't.
I've tested both running docker compose up (which picks up the .env file by default) and the command you mentioned (docker-compose --env-file .env up) and was able to get the password page showing up.

Steps I took:

1. Added ACCESS_KEYS="test" to .env
2. Ran docker-compose --env-file .env up
3. Accessed http://localhost:7860/
   
4. Inserted "test" in the password field and submitted
5. Saw the main screen
   

Note that once you insert the correct password for the first time, it won't ask for the password in subsequent accesses, unless you change the password. But as per your comment, I understand that the password page never appeared even on the first time.

I'm guessing your .env file was not picked up. Here's one quick thing we can do to check if the .env is being used:
can you add DEFAULT_INFERENCE_TYPE="horde" to .env and confirm if when you access MiniSearch in a private window and open the menu it shows "AI Processing Location: AI Horde (Pre-configured)" selected?