Error "Your session was probably cancelled on the server!"

[TommasoDb]

Describe the bug Im running Geonetwork in Docker and If I login in with administrator user, Geonetwork displays this error message:

Last activity was tracked 2022-11-09 13:30:27 and your session has probably expired now (max inactivity time is 2100s). You should reload the page and see if your session is still alive or sign in again!

I can close the message and continue my work, but the message comes back again in few seconds.

I already tried deleting all containers and all volumes, than restart the docker engine and than start Geonetwork again, but the error persists.

To Reproduce I don't know what I did to trigger this error. Maybe I have deleted or renamed some volume, maybe the elastic search volume or the database volume.

Screenshots

Log file If applicable, add the server log file to help trace your problem.

Desktop (please complete the following information):

• Firefox
• 4.2.1, but the error persists after downgrade to 3.12.7
• Server Application: Apache Tomcat/8.5.83

Additional context My docker-compose.yml:

version: "3.8"
volumes:
  geonetwork1:
  esdata1:
  pgdata1:

services:
  geonetwork:
    image: geondeleting alletwork
    restart: always
    ports:
      - 8080:8080
    environment:
      DATA_DIR: /catalogue-data
      ES_HOST: elasticsearch
      ES_PROTOCOL: http
      ES_PORT: 9200

      KB_URL: http://kibana:5601

      GEONETWORK_DB_TYPE: postgres
      GEONETWORK_DB_HOST: database
      GEONETWORK_DB_PORT: 5432
      GEONETWORK_DB_NAME: geonetwork
      GEONETWORK_DB_USERNAME: geonetwork
      GEONETWORK_DB_PASSWORD: geonetwork
    volumes:
      - geonetwork1:/catalogue-data
    depends_on:
      - kibana
      - elasticsearch
      - database

  elasticsearch:
    image: elasticsearch:7.9.2
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65536
        hard: 65536
    environment:
      ES_JAVA_OPTS: "-Xms1G -Xmx1G"
      discovery.type: single-node
    volumes:
      - esdata1:/usr/share/elasticsearch/data
    ports:
      - "9200:9200"

  kibana:
    image: kibana:7.9.2
    environment:
      SERVER_NAME: kibana
      ELASTICSEARCH_URL: http://elasticsearch:9200/
      SERVER_BASEPATH: /geonetwork/dashboards
      SERVER_REWRITEBASEPATH: 'false'
      KIBANA_INDEX: .dashboards
      XPACK_MONITORING_UI_CONTAINER_ELASTICSEARCH_ENABLED: 'true'
    ports:
      - "5601:5601"

  database:
    image: mdillon/postgis
    environment:
      POSTGRES_USER: "geonetwork"
      POSTGRES_PASSWORD: "geonetwork"
      POSTGRES_DB: "geonetwork"
    volumes:
      - pgdata1:/var/lib/postgresql/data
    ports:
      - "55432:5432"

[ThomasJunk]

Is this line of your docker-compose.yml correct: image: geondeleting alletwork? Trying to reproduce your error fails with ERROR: invalid reference format.

Using image: geonetwork:4.2.2 instead seems to work.

With said version of geonetwork I could not reproduce your error. Is this error still occuring?

[ThomasJunk]

I think there is an error hidden in your docker-compose.yml?. image: geondeleting alletwork is no correct image name. docker-compose up complains about ERROR: invalid reference format. If I use instead e.g. geonetwork:4.2.2 as an image name it will work. And with this the error you reported seems not reproducible. Does this error still occur on your setup?

[ioulosve]

I have the same error. Did you find a solution?

[archaeogeek]

Have you tried clearing the cookies in your browser?

[ioulosve]

yes and the error is gone, thank you :)