Skip to content

Can't add link on fresh docker deployment. #156

Description

@xsnoopy

Fresh docker installation throws the following error, when clicking on add a link.

`Error
HTTP 500 Internal Server Error
Class "Symfony\Component\Yaml\Yaml" not found

Exception Stack Trace 

Error
in /htdocs/app/Models/LinkType.php (line 44)

LinkType::get() in /htdocs/app/Http/Controllers/UserController.php (line 192)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Controller.php -> AddUpdateLink (line 54)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php -> callAction (line 43)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Route.php -> dispatch (line 259)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Route.php -> runController (line 205)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Router.php -> run (line 798)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> Illuminate\Routing{closure} (line 141)
Pipeline->Illuminate\Pipeline{closure}() in /htdocs/app/Http/Middleware/Impersonate.php (line 159)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
Pipeline->Illuminate\Pipeline{closure}() in /htdocs/app/Http/Middleware/CheckBlockedUser.php (line 27)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Middleware/SubstituteBindings.php -> Illuminate\Pipeline{closure} (line 50)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Auth/Middleware/Authenticate.php -> Illuminate\Pipeline{closure} (line 44)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/VerifyCsrfToken.php -> Illuminate\Pipeline{closure} (line 78)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/View/Middleware/ShareErrorsFromSession.php -> Illuminate\Pipeline{closure} (line 49)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php -> Illuminate\Pipeline{closure} (line 121)
in /htdocs/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php -> handleStatefulRequest (line 64)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/AddQueuedCookiesToResponse.php -> Illuminate\Pipeline{closure} (line 37)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Cookie/Middleware/EncryptCookies.php -> Illuminate\Pipeline{closure} (line 67)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> Illuminate\Pipeline{closure} (line 116)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Router.php -> then (line 797)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Router.php -> runRouteWithinStack (line 776)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Router.php -> runRoute (line 740)
in /htdocs/vendor/laravel/framework/src/Illuminate/Routing/Router.php -> dispatchToRoute (line 729)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php -> dispatch (line 190)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> Illuminate\Foundation\Http{closure} (line 141)
in /htdocs/vendor/livewire/livewire/src/DisableBrowserCache.php -> Illuminate\Pipeline{closure} (line 19)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
Pipeline->Illuminate\Pipeline{closure}() in /htdocs/app/Http/Middleware/Headers.php (line 25)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php -> Illuminate\Pipeline{closure} (line 21)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ConvertEmptyStringsToNull.php -> handle (line 31)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php -> Illuminate\Pipeline{closure} (line 21)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TrimStrings.php -> handle (line 40)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php -> Illuminate\Pipeline{closure} (line 27)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/PreventRequestsDuringMaintenance.php -> Illuminate\Pipeline{closure} (line 86)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Http/Middleware/HandleCors.php -> Illuminate\Pipeline{closure} (line 49)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/fideloper/proxy/src/TrustProxies.php -> Illuminate\Pipeline{closure} (line 57)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Http/Middleware/TrustHosts.php -> Illuminate\Pipeline{closure} (line 48)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> handle (line 180)
in /htdocs/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php -> Illuminate\Pipeline{closure} (line 116)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php -> then (line 165)
in /htdocs/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php -> sendRequestThroughRouter (line 134)
Kernel->handle() in /htdocs/index.php (line 63)
`

Activity

  1. lastsamurai26 commented on Jan 28, 2026

    @lastsamurai26
    Member

    Unfortunately, I cannot reproduce this with a fresh installation and a Docker volume.

    Can you provide me with the Docker YML?
    And, if necessary, the .env from the Linkstack installation.

  2. xsnoopy commented on Jan 29, 2026

    @xsnoopy
    Author

    Yes here it is.

    services:

    linkstack:
    hostname: 'linkstack'
    container_name: linkstack
    image: 'linkstackorg/linkstack:latest'
    environment:
    TZ: 'Europe/Berlin'
    SERVER_ADMIN: 'myemail@mydomain.com'
    HTTP_SERVER_NAME: 'links.mydomain.com'
    HTTPS_SERVER_NAME: 'links.mydomain.com'
    LOG_LEVEL: 'info'
    PHP_MEMORY_LIMIT: '256M'
    UPLOAD_MAX_FILESIZE: '8M'
    volumes:
    - /home/user/container/linkstack/data:/htdocs'
    expose:
    - "443"
    restart: unless-stopped

    networks:
    default:
    name: nginx-proxy
    external: true`

  3. xsnoopy commented on Jan 29, 2026

    @xsnoopy
    Author

    Just FYI, I saw that I had a typo at the end of the volumnes file and corrected that. I saw in the documentation, that the setup I used is not putting in the right data in the folder and required manual copying of the files.

    I went back to a regular docker volume. But still get the same error when adding a link.

  4. andrewzung commented on Jan 30, 2026

    @andrewzung

    use image: alexbabel/linkstack:latest (v4.8.0) for now

  5. xsnoopy commented on Jan 30, 2026

    @xsnoopy
    Author

    That worked!

  6. Nubinator commented on Feb 5, 2026

    @Nubinator

    This issue still exists, my original deployment started having this issue so i made a fresh install while using both mysql database and the sqlite one and the issue exists on both. The docker yml is same as the in the readme and no settings changed.

    Using the dockerhub image gives me the following error:-

    Image

    I tried using the ghcr image and that works with no issue Until I update it to the latest version via the web installer after which i get basically the same error:-

    Image
  7. Seblor commented on Feb 7, 2026

    @Seblor

    @xsnoopy Please don't mark the issue as closed since you used a fork. The issue is still here in the latest docker image.

  8. reopened this on Feb 7, 2026
  9. electricsteve commented on Feb 8, 2026

    @electricsteve

    This is linked to #959 on the main repo.

  10. Seblor commented on Feb 8, 2026

    @Seblor

    Thanks for the link.

    I hope there will be better versioning of the images to not depend on the latest tag only. I wanted to try LinkStack out, but I'll have to find something else...

  11. lastsamurai26 commented on Feb 9, 2026

    @lastsamurai26
    Member

    We are aware of this bug and ask for your patience. At this time, it is only possible to downgrade to 4.8.4.
    This can be done manually by placing the update package for version 4.8.4 in the httpdocs folder.

    This is not a Docker bug.
    The Docker images only provide the version at the time of build once; all other versions are provided via the internal Linkstack Updater, so downgrading via tags is not possible.

  12. Seblor commented on Feb 9, 2026

    @Seblor

    I understand that this is an upstream bug, but since there is no versioning of the Docker image, it means that for now, there is no way to install any version of LinkStack through Docker, except via in-container file manipulation.

    By the way is there some documentation on the downgrading process you described ? I'd like to avoid doing mistakes.

    Thanks for the work you're doing though. I really appreciate that you are taking the time to handle this.

  13. electricsteve commented on Feb 9, 2026

    @electricsteve

    I understand that this is an upstream bug, but since there is no versioning of the Docker image, it means that for now, there is no way to install any version of LinkStack through Docker, except via in-container file manipulation.

    By the way is there some documentation on the downgrading process you described ? I'd like to avoid doing mistakes.

    Thanks for the work you're doing though. I really appreciate that you are taking the time to handle this.

    (I think) Download this update file from v4.8.4 and folow the instructions in HOW TO UPDATE.md. https://github.com/LinkStackOrg/LinkStack/releases/download/v4.8.4/update.zip

  14. lastsamurai26 commented on Feb 9, 2026

    @lastsamurai26
    Member

    I understand that this is an upstream bug, but since there is no versioning of the Docker image, it means that for now, there is no way to install any version of LinkStack through Docker, except via in-container file manipulation.
    By the way is there some documentation on the downgrading process you described ? I'd like to avoid doing mistakes.
    Thanks for the work you're doing though. I really appreciate that you are taking the time to handle this.

    (I think) Download this update file from v4.8.4 and folow the instructions in HOW TO UPDATE.md. https://github.com/LinkStackOrg/LinkStack/releases/download/v4.8.4/update.zip

    correct :-) this is all

  15. lastsamurai26 commented on Apr 20, 2026

    @lastsamurai26
    Member

    New Version should work again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions