Does not work anymore.

[JFPCreations]

Not sure what happen, it was working great for months, but now it shows this:

From nginx reverse proxy:

@extends('layouts.app') @section('content') @include('partials.search') @if($apps->first()) @include('sortable') @else
{!! __('app.dash.no_apps', [ 'link1' => ''.__('app.dash.link1').'', 'link2' => ''.__('app.dash.link2').'' ]) !!}
@include('add')
@endif @endsection

From ip.port: Login page give this:

@extends('layouts.app') @section('content')
{{ csrf_field() }}
@if($user->avatar) @else @endif {{ $user->username }}
Login
@endsection

Latest docker version of heimdall installed.

Can you help me fix this, please?

[JFPCreations]

I can still login and it show:

@extends('errors::minimal') @section('title', __('Not Found')) @section('code', '404') @section('message', __('Not Found'))

[grpfl]

Same Issue

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

{!! __('app.dash.no_apps', [ 'link1' => ''.__('app.dash.link1').'', 'link2' => ''.__('app.dash.link2').'' ]) !!}
@include('add')
@endif @endsection

[moreje]

same for me... 2.5.8 and dev tags get the same error

[victorgrund]

Similar issues with the latest tag.

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

{!! __('app.dash.no_apps', [ 'link1' => ''.__('app.dash.link1').'', 'link2' => ''.__('app.dash.link2').'' ]) !!}
@include('add')
@endif @endsection

[SighmanSays]

Same behavior running docker from Synology.

Can work around it by using tag V2.5.8-ls251

[victorgrund]

@Callahan78, here's the top part of my docker compose file that's temporarily edited to pull a working version:

---
version: "2.1"
services:
  heimdall:
    #image: lscr.io/linuxserver/heimdall:latest
    image: lscr.io/linuxserver/heimdall:V2.5.8-ls251
    container_name: heimdall

[Callahan78]

@Callahan78, here's the top part of my docker compose file that's temporarily edited to pull a working version:

---
version: "2.1"
services:
  heimdall:
    #image: lscr.io/linuxserver/heimdall:latest
    image: lscr.io/linuxserver/heimdall:V2.5.8-ls251
    container_name: heimdall

Ah . . . I missed the "V" in "V2.5.8-ls251" . . . . now it is working :-)
Thank you very much! 👍

[JFPCreations]

Thank you.

[TheLinx79]

Also broken for me. Reverting to the previous image as mentioned still give ipv6 related errors.

[ppfeufer]

If you are affected by this issue, please just "upvote" the opening post. Posting here "Same issue" all the time is just spamming various mailboxes of people who follow this issue. I'm pretty sure the devs got the message by now.

This is also resulting in this, which is indeed not helpful:

If you want to get updates on this issue, you can subscribe to it.

Thank you.

[WildStar2022]

I run Heimdall on Kubernetes (MicroK8s on Ubuntu) in a VM and manage applications using Portainer CE.

Make sure to backup first or make a snapshot if running Heimdall in a VM!
Consult Portainer docs if using Helm, Docker, or want to use the command line.

• Login to Portainer
• Select the Kubernetes environment
• From the Dashboard, select Applications
• From the Applications list, select heimdall (or whatever you called it)
• From the Applications details, select YAML
• Select Copy to clipboard
• Paste to an editor like Notepad
• From your editor:
  - Comment out: #image: linuxserver/heimdall:latest
  - Replace with: image: linuxserver/heimdall:V2.5.8-ls251
  - Edit/Select All then Copy
• From your browser Portainer window, go back one page
• Select Create from manifest
• Toggle User namespace(s) specified from manifest
• I left Namespace to default
• Enter heimdall (or whatever you called it) in the Name field
• Select Web Editor and Paste the contents of your clipboard
• Finally at the bottom under Action, select Deploy

[elax46]

I have the same problem on my instance too

[j0nnymoe]

Pinned the issue and I'm just going to lock the conversation for now. We are aware of the issue, as mentioned by @ppfeufer - this is getting spammy right now. We are working on a fix, just roll back to the previous tag that's been mentioned already.

[KodeStar]

This should be fixed. Additionally I'll be dropping a new release v2.6.0 tomorrow, if anyone has a chance please test it using the :development tag. The new release updates the underlying framework from Laravel 8 to Laravel 10, which increases the minimum php version to 8.1 as well as requiring the DOM PHP extension and adds in Search support on the application dropdown list.