Seemed to happen with the new UI, at least the first time I saw it, it hung up. Perhaps i missed a release note?
Firstly, using bleeding edge?
Application Version: development
Commit Details: c1cdc89 (2026-04-03T04:59:17Z)
Build Time: 2026-04-03T04:59:44Z
Describe the bug
I log on, it attempts to display the timeline and it sits there with the orbiting cursor .. sometimes it comes back and displays, sometimes not.
Expected behavior
Display a map, with or without a timeline mapping
Screenshots
Desktop (please complete the following information):
Windows 10, Windows 11, Android. Pretty much all browsers, Edge, Firefox, Vivaldi, etc
Smartphone (please complete the following information):
Additional context
So, just wondering if i missed something. I captured some logs from tile-cache as perhaps it relates? I double checked, 172.19.0.6 is actually the main retti service/container
127.0.0.1 - - [04/Apr/2026:15:53:16 +0000] "GET /0/0/0.png HTTP/1.1" 200 6924 "-" "Wget"
2026/04/04 15:53:29 [error] 9#9: *9781 connect() to [2a04:4e42:61::347]:443 failed (101: Network unreachable) while connecting to upstream, client: 172.19.0.6, server: , request: "GET /satellite/3/2/2 HTTP/1.1", upstream: "https://[2a04:4e42:61::347]:443/satellite/3/2/2", host: "tile-cache"
172.19.0.6 - - [04/Apr/2026:15:53:30 +0000] "GET /satellite/3/2/2 HTTP/1.1" 400 30 "-" "Java-http-client/25.0.2"
172.19.0.6 - - [04/Apr/2026:15:53:30 +0000] "GET /satellite/3/3/0 HTTP/1.1" 400 30 "-" "Java-http-client/25.0.2"
I figure it is something up related to my docker and network, though I don't recall doing anything to disrupt it. I have reitti and immich sharing a network. Here is the complete compose yaml
services:
reitti:
image: dedicatedcode/reitti:develop
networks:
- default
- reitti-immich
restart: always
ports:
- 8383:8080
depends_on:
rabbitmq:
condition: service_healthy
postgis:
condition: service_healthy
redis:
condition: service_healthy
tile-cache:
condition: service_healthy
environment:
ENABLE_STOP_DETECTION: "true"
DISTANCE_UNITS: Imperial
STOP_DETECTION_DISTANCE_THRESHOLD: "50" # meters (default)
STOP_DETECTION_TIME_THRESHOLD: "300" # seconds (default)
volumes:
- ./data/reitti-data:/data
postgis:
image: postgis/postgis:17-3.5-alpine
restart: always
ports:
- 5483:5432
environment:
POSTGRES_USER: xxx
POSTGRES_PASSWORD: xxx
POSTGRES_DB: xxxx
volumes:
- ./data/postgis-data:/var/lib/postgresql/data
deploy:
resources:
limits:
cpus: "2.0" # GIS math can be heavy; give it 2 cores
memory: 2G # GIS databases love RAM; 2G keeps it snappy
healthcheck:
test:
- CMD-SHELL
- pg_isready -U reitti -d reittidb
interval: 10s
timeout: 5s
retries: 5
rabbitmq:
image: rabbitmq:3-management-alpine
restart: always
environment:
RABBITMQ_DEFAULT_USER: xxx
RABBITMQ_DEFAULT_PASS: xxx
volumes:
- ./data/rabbitmq-data:/var/lib/rabbitmq
deploy:
resources:
limits:
cpus: "1.0" # Prevent the 250% spike from affecting Immich
memory: 512M # RabbitMQ is very lean on memory unless queues are huge
healthcheck:
test:
- CMD
- rabbitmq-diagnostics
- check_port_connectivity
interval: 1m # How often to check during normal operation
timeout: 2m # Give the check 2m to finish (generous for RabbitMQ)
retries: 5 # Must fail 5 times in a row to be "Unhealthy"
start_period: 2m # Failures are IGNORED for the first 2 minutes
start_interval: 10s # OPTIONAL: Check every 10s during boot to start faster
redis:
image: redis:7-alpine
restart: always
volumes:
- ./data/redis-data:/data
healthcheck:
test:
- CMD
- redis-cli
- ping
interval: 10s
timeout: 5s
retries: 5
tile-cache:
image: nginx:alpine
environment:
NGINX_CACHE_SIZE: 1g
command: >
sh -c "
mkdir -p /var/cache/nginx/tiles
cat > /etc/nginx/nginx.conf << 'EOF'
events {
worker_connections 1024;
}
http {
proxy_cache_path /var/cache/nginx/tiles levels=1:2 keys_zone=tiles:10m max_size=1g inactive=30d use_temp_path=off;
server {
listen 80;
location / {
proxy_pass https://tile.openstreetmap.org/;
proxy_set_header Host tile.openstreetmap.org;
proxy_set_header User-Agent "Reitti/1.0";
proxy_cache tiles;
proxy_cache_valid 200 30d;
proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504;
}
}
}
EOF
nginx -g 'daemon off;'"
restart: always
healthcheck:
test:
- CMD
- wget
- --quiet
- --tries=1
- --spider
- http://127.0.0.1/0/0/0.png
interval: 30s
timeout: 10s
retries: 3
networks:
reitti-immich:
external: true
Seemed to happen with the new UI, at least the first time I saw it, it hung up. Perhaps i missed a release note?
Firstly, using bleeding edge?
Application Version: development
Commit Details: c1cdc89 (2026-04-03T04:59:17Z)
Build Time: 2026-04-03T04:59:44Z
Describe the bug
I log on, it attempts to display the timeline and it sits there with the orbiting cursor .. sometimes it comes back and displays, sometimes not.
Expected behavior
Display a map, with or without a timeline mapping
Screenshots
Desktop (please complete the following information):
Windows 10, Windows 11, Android. Pretty much all browsers, Edge, Firefox, Vivaldi, etc
Smartphone (please complete the following information):
Additional context
So, just wondering if i missed something. I captured some logs from tile-cache as perhaps it relates? I double checked, 172.19.0.6 is actually the main retti service/container
I figure it is something up related to my docker and network, though I don't recall doing anything to disrupt it. I have reitti and immich sharing a network. Here is the complete compose yaml