-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Erorr with latest version V2.5.8-ls252 after updating container - Error included in Current behavior section #144
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
See #143 that was posted just 5 mins before this. TL:DR; It seems this release broke things, use |
Same here |
I see the other ticket now, sorry about that. There wasn't another ticket when i was gathering the information for the ticket i submitted - other wise i would of just commented on it. Additionally - instead of going back to older version of that i was not on 2.5.7 - i just changed latest to the prior tag of V2.5.8-ls251 and it up for the time being. |
Same issue here @extends('layouts.app') @section('content') @include('partials.search') @if($apps->first()) @include('sortable') @else |
a stupid question, how can I go back to version V2.5.8-ls251? I use unraid. |
Same here after overnight update - how do I fix it ?? I use docker on Debian / Portainer @extends('layouts.app') @section('content') @include('partials.search') @if($apps->first()) @include('sortable') @else |
Just change the Repository to "lscr.io/linuxserver/heimdall:2.5.7" or whatever version you like. |
Worked for me Thank You ! |
Same issue here . docker pull linuxserver/heimdall:amd64-V2.5.8-ls250. works no need back to 2.5.7 |
just returned to V2.5.8-ls251 till a fix arrives. thanks. |
Same issue here. Downgrading back to either V2.5.8-ls250 or V2.5.8-ls251 fixed the issue on my system. For anyone confused about how to downgrade, the process is outlined on the docker hub page. In my case, my docker compose file now reads: |
Thank you for the v2.6.0-ls253 update - everything is back up and running properly using the latest tag in the docker-compose.yml file. Marking as closed |
Is there an existing issue for this?
Current Behavior
Heimdall updated to version V2.5.8-ls252 and upon accessing the container it produces the following error below:
@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
Expected Behavior
Open the Heimdall home page without error.
Steps To Reproduce
Updated from Version V2.5.8-ls250
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: