Sonarqube is stuck on Loading after upgrade to 9.9 LTS (from 9.8)

Make sure to tell us:

  • What version are you upgrading from?
    9.8

  • System information (Operating system, Java version, Database provider/version)
    Docker image (sonarqube:9.9.0-developer)

  • What’s the issue you’re facing?
    After upgrading to 9.9 LTS the interface is stuck on ‘Loading…’

We run Sonarqube on a ‘context’ since this machine hosts multiple Docker images. We use Traefik to route this.

Our docker-compose file

version: "3"

services:

  db:
    image: postgres:12.1
    environment:
      - POSTGRES_USER=*****
      - POSTGRES_PASSWORD=*****
      - POSTGRES_DB=sonarqube
    volumes:
      - sonarqube_db:/var/lib/postgresql/data
    networks:
      - traefik
    labels:
      - traefik.enable=false
    ulimits:
      nofile:
        soft: 65536
        hard: 65536

  sonarqube:
    build: .
    container_name: sonarqube
    stop_grace_period: 5m
    environment:
      - sonar.jdbc.username=*****
      - sonar.jdbc.password=*****
      - sonar.jdbc.url=jdbc:postgresql://db:5432/sonarqube
      - sonar.web.context=/sonar
    volumes:
      - sonarqube_conf:/opt/sonarqube/conf
      - ./extensions:/opt/sonarqube/extensions
      - sonarqube_logs:/opt/sonarqube/logs
      - sonarqube_data:/opt/sonarqube/data
    networks:
      - traefik
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.sonarqube.rule=Host(`ourdomain.com`) && PathPrefix(`/sonar`)"
      - "traefik.http.routers.sonarqube.entrypoints=websecure"

networks:
  traefik:
    external: true

volumes:
  sonarqube_conf:
  sonarqube_extensions:
  sonarqube_logs:
  sonarqube_data:
  sonarqube_db:

The page which shows ‘Loading’ doesn’t seem to correct take the context into account while loading its assets:

<script type="module" src="[/js/outL2Z6DMVA.js](/js/outL2Z6DMVA.js)"></script>
<link rel="stylesheet" href="[/js/outV5A3AQEU.css](/js/outV5A3AQEU.css)" />

The problem seemed to be the JDBC connection env stuff which is no longer picked up. After moving those environment settings into our sonar.properties, it started correctly.

2 Likes