Failed to load resource: the server responded with a status of 401 (Unauthorized)

[fanpero87]

Hello,
I just set it up using Docker. I noticed that if I inspect the Login page, I get Failed to load resource: the server responded with a status of 401 (Unauthorized) for two endpoints:
:8090/api/users/current and :8090/api/frontend/configuration
On both cases, I get this on the browser: "{"message":"Invalid access token"}"

Im running the container using a docker-compose.yml file that looks like this

services:
  nginx-ui:
    image: dillmann/nginx-ignition
    container_name: nginx-ignition
    ports:
      - 8090:8090
      - 80:80
    restart: unless-stopped

I havent done any configuration or anything. I just run the docker compose file and created an account on the browser. Havent make any changes or modifications.

Im not sure if I should be doing something differently to avoid that error.

Thanks.

[lucasdillmann]

Hi @fanpero87.

The backend replying with a 401 means that you need to log in again, either because it is the first time you opened ignition in a new browser or because your previous session expired due to inactivity. The frontend is able to detect when the backend replies with a 401 and automatically:

• Redirect you to the login page if you just opened ignition; or
• Warn you that the session expired when ignition was already open, asking if you want to go to the login page or stay where you are (to avoid losing any unsaved actions)

Although the browser is showing an error just like in your print, there's nothing to worry about. It's just the standardized way of the server telling the browser that it needs to show you the login form.