Skip to content

Axios Error while trying to generate a model #204

Closed as not planned
Closed as not planned

Description

@sigmasoldi3r

Describe the bug

I've downloaded the Linux binaries, and downloaded a model from the readme, but upon trying to generate a model from an image yields "Axios Error (400)"

Maybe I'm missing a setup step?

Steps to reproduce

  1. Download latest appimage
  2. Select a folder
  3. Wait for setup to finish
  4. Download model TripoSG
  5. Create a new workflow with image input -> model -> add to scene
  6. Run

Modly version

0.4.0

Operating system

Garuda Linux 7.0.11-zen1-1-zen

Screenshots & logs

AxiosError: Request failed with status code 400
Image

The workflow used is simple:

Image

The model:

Image

Confirmation

  • I have searched existing issues and this has not been reported yet.
  • I can reproduce this on the latest version of Modly.

Activity

  1. cloudling8 commented on Jun 25, 2026

    @cloudling8

    yeah get the same on windows

  2. self-assigned this
    on Jun 26, 2026
  3. Lorchie commented on Jun 26, 2026

    @Lorchie
    Collaborator

    Thanks — this is an extension setup/registration issue, not an inference failure.

    The AxiosError 400 fires immediately on submit, before any 3D work starts. It means the backend can't find the TripoSG generator in its registry — which happens when the extension's bundled environment didn't finish installing. Downloading the model (step 4) only fetches the weights; the extension's runtime (its embedded Python venv with torch / triposg / diso) is built separately when the extension is installed, and if that build failed the model registers as "errored" and the run is rejected with a generic 400.

    Try this first: Models page → TripoSG → Repair (re-runs the extension install). Watch the logs during that step.

    To help us nail the root cause, could you share:

    • The backend/terminal logs from clicking Repair (the [setup] … lines, especially any SSL/downl
    • Your GPU (NVIDIA / AMD / none) and whether you have an NVIDIA card at all.

    One likely Linux culprit on our side: the embedded Python ships without a CA bundle, so the setup downloads (diso wheel + triposg source) can fail over HTTPS. We're also going to fix the misleading 400 — a failed install should say "extension needs Repair", not "unknown model".

  4. iammojogo-sudo commented on Sep 27, 2026

    @iammojogo-sudo
    SponsorContributor

    You likely, like Lorchie said, have to repair to rebuild the venv. Delete the pycache and venv and repair.

  5. lightningpixel commented on Nov 14, 2026

    @lightningpixel
    Owner

    The extension's environment didn't finish installing. Click Repair on the extension to fix it. Reopen if it persists.

  6. moved this from Backlog to Done in Modly Boardon Nov 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions