[BUG] Heimdall page broken

[arces]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

My Heimdall docker image updated to the latest version "Linuxserver.io version:- V2.5.8-ls252 Build-date:- 2024-02-16T18:30:28+00:00" via watchtower.
When I open it, I get the following:

@extends('layouts.app') @section('content') @include('partials.search') @if($apps->first()) @include('sortable') @else
{!! __('app.dash.no_apps', [ 'link1' => '['.__('app.dash.link1').'](https://MY_URL_HERE/'.route('items.create',%20[]).')', 'link2' => '['.__('app.dash.link2').'](https://MY_URL_HERE/)' ]) !!}

@include('add')
@endif @endsection

Tried the page in incognito, hard refresh/empty cache, cleared out browser storage, recreated the image with a freshly pulled image

Expected Behavior

No response

Steps To Reproduce

Update to the latest version
Launch with portainer/docker

Environment

- OS: Ubuntu 20.04
- How docker service was installed:
Portainer stack

Stack:
services:
  heimdall:
    image: lscr.io/linuxserver/heimdall:latest
    container_name: heimdall
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /var/lib/docker/volumes/heimdall/_data:/config
    ports:
      - 8081:80
      - 4443:443
    restart: unless-stopped

CPU architecture

x86-64

Docker creation

I just pulled the latest image and used my existing configs. Using Portainer Stacks, which is just docker compose as far as I know.

Container logs

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1000
───────────────────────────────────────
using keys found in /config/keys
New container detected, installing Heimdall
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│            │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-08-20 │ 2023-08-13 │ /config/nginx/ssl.conf                                                 │
│ 2018-03-06 │ 2023-04-13 │ /config/nginx/site-confs/default.conf                                  │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Neriderc]

Just commenting to say I'm having the same issue!

@extends('layouts.app') @section('content') @include('partials.search') @if($apps->first()) @include('sortable') @else

{!! __('app.dash.no_apps', [ 'link1' => '['.__('app.dash.link1').'](http://192.168.1.10:8080/'.route('items.create',%20[]).')', 'link2' => '['.__('app.dash.link2').'](http://192.168.1.10:8080/)' ]) !!}
@include('add')
@endif @endsection

I have removed the ./config directory and tried it fresh, accessing it directly by port not through the reverse proxy, and it still doesn't work.

[dakink]

+1. New pull and fresh config directory don't seem to help. Reverting to tag 2.5.7 solves the issue for me.

[Neriderc]

+1. New pull and fresh config directory don't seem to help. Reverting to tag 2.5.7 solves the issue for me.

I can confirm this worked for me too.

[grpfl]

Same issue, and reverting to 2.5.7 resolved it

[bb12489]

Same issue here. Reverting helped me as well.

[fullcavediver]

Same issue, back to 2.5.7

[pokrzys]

Same problem. Reverting to V2.5.8-ls251 solves it. No need to go back to 2.5.7.

[dakink]

Same problem. Reverting to V2.5.8-ls251 solves it. No need to go back to 2.5.7.

Jip, this one works as well.

[unixweb]

Same issue here in m Homelab.
docker pull linuxserver/heimdall:amd64-V2.5.8-ls250 works in my case

[arces]

Any thoughts @thespad ?

[j0nnymoe]

Any thoughts @thespad ?

Roll back to the working image mentioned, fixed build should be out within 24 hours.

[KodeStar]

Fixed build has been out for a couple of days

[borracho-mejor]

This issue still exists with the :latest tag, I've been updating my docker-compose.yml each week to repull the latest issue and it consistently breaks until I revert to 2.6.1. Is there going to be a planned fix for this in later versions? I see the exact same text as in the screenshots.

[arces]

This issue still exists with the :latest tag, I've been updating my docker-compose.yml each week to repull the latest issue and it consistently breaks until I revert to 2.6.1. Is there going to be a planned fix for this in later versions? I see the exact same text as in the screenshots.

I had the same issue too. What I did (I use portainer) was redeploy the image and pull a fresh copy of it and it worked! I am not exactly sure, but I used the same old configs and data from my past versions. Just updated my stack (in portainer) and then manually went to the running container and had it pull a fresh image. Hard refreshed on my browser and it was back up and running just like normal

[fjmerc]

I can confirm that @arces recommendation to redeploy the image worked for me. I had to first remove the image(s) by running docker image rm --force <image_id> and then redeploy my stack.