The fix from PR #537 was lost from master

[gl0balw0rk]

Issue Type

• Bug Report

Faraday version

Faraday v5.23.0 (Docker image faradaysec/faraday:latest, published 2026-07-23)

Component Name

WebGui / Docker deployment

Steps to reproduce

1. Fresh installation following the official guide:

   curl -O https://raw.githubusercontent.com/infobyte/faraday/master/docker-compose.yaml
   docker compose up -d

2. Wait until all containers report healthy.

3. Open http://localhost:5985/

Expected results

The web UI loads (HTTP 200) on first access.

Debugging tracebacks (current results)

HTTP 500 on GET /. From docker compose logs faraday-server:

TypeError: create_app.<locals>.index() got an unexpected keyword argument 'text'
  File "/src/.venv/lib/python3.11/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)

Root cause: In faraday/server/app.py (current master, commit b6a06c56d), the routes declare a text parameter but the view signature doesn't accept it:

@app.route('/', defaults={'text': ''})
@app.route('/<path:text>')
def index(ex):   # <- should be def index(ex=None, text=None):

This bug was already fixed by PR #537 (merged 2026-06-23 by @nahwar, merge commit af423823c), which resolved #536. However, the merge commit is no longer reachable from master — it appears a later regeneration of master from the internal white/dev branch silently dropped it:

$ git merge-base --is-ancestor af423823c origin/master && echo yes || echo no
no

$ git log origin/master --oneline | grep -c "Merge pull request #537"
0

$ grep -n "def index" faraday/server/app.py   # at origin/master HEAD
447:    def index(ex):

Because GitHub keeps showing PR #537 as "MERGED" (a historical PR event, not a property of the current branch), the regression went unnoticed. As a result, every published Docker image since at least 5.18.0 ships the bug, and #541 (same traceback on v5.22.0) was closed with a workaround that no longer works (rebuilding from master does not help — master itself is broken).

Proposed fix: re-apply the one-line change from PR #537 (def index(ex=None, text=None)) to the internal white/dev branch so it survives the next sync to master, republish the Docker image, and consider reopening #536 until the fix reaches a released artifact.

Verified locally: applying this single-line patch and rebuilding the image (docker compose build faraday-server) makes GET / return HTTP 200 and the UI fully loads.

Screenshots

N/A — traceback above is from the server logs.

Environment information

Configuration files

Default docker-compose.yaml from master, unmodified.

Reports/Extra data

N/A

OS

Arch Linux

[ignaciosoto93]

Thanks for the very detailed report. I checked this against the current default branch and also reproduced it locally from a fresh Docker Compose install.

This is still a real bug in the current branch.

What I confirmed:

• faraday/server/app.py currently still defines the route as:
  • @app.route('/', defaults={'text': ''})
  • @app.route('/<path:text>')
  • def index(ex)
• with that code, a fresh install returns HTTP 500 on /
• the traceback is exactly:
  • TypeError: create_app.<locals>.index() got an unexpected keyword argument 'text'

I also checked PR #537, and the original fix is exactly the one you pointed out:

• def index(ex) -> def index(ex=None, text=None)

So at this point the problem is not just an old image artifact. The current branch itself still contains the broken handler signature, which means the fix from #537 is effectively not present in today’s master.

I also reviewed the related context:

• #536 was the original issue
• #541 reported the same symptom, but rebuilding is no longer a reliable workaround if the current branch still has the broken code

So this should be treated as an active regression in the current branch.

Thanks again for documenting the root cause so clearly. That made this one straightforward to verify.

[ignaciosoto93]

Re-verified today against the current documented Docker installation flow.

What I confirmed:

• This is a real bug in the current default branch, not a user misconfiguration.
• faraday/server/app.py still has the catch-all routes with a text parameter but the handler is still defined as def index(ex).
• With that code, GET / still fails with TypeError: create_app..index() got an unexpected keyword argument text.

I also re-tested both documented community Docker flows:

1. git clone https://github.com/infobyte/faraday.git && cd faraday && docker compose up -d
2. curl -O https://raw.githubusercontent.com/infobyte/faraday/master/docker-compose.yaml && docker compose up -d

In both cases:

• the stack starts successfully
• faraday-server becomes healthy
• GET / returns HTTP 500
• the server logs show the same traceback reported here

So this issue is still valid and should remain open as the canonical tracker.

Related context:

• Bug: Fresh Docker installation fails on first access with unexpected keyword argument 'text' #536 was the original report
• Fix: resolve TypeError in index route on fresh install (#536) #537 introduced the earlier fix
• fix(server): accept the routed path in the index view #545 is the currently open PR restoring that fix
• Web UI rompe con 500 en / — TypeError en index() por conflicto entre @errorhandler(404) y las rutas catch-all #548 was a duplicate confirmation and has already been closed in favor of this issue

One note: I did not independently verify the exact version range mentioned in the issue body, but I did confirm the bug on the current documented install path and current master.

[Eljees]

This looks fixed on master now, a couple of days after the last confirmation here.

faraday/server/app.py currently reads:

    @app.errorhandler(404)
    @app.route('/', defaults={'text': ''})
    @app.route('/<path:text>')
    def index(ex=None, text=None):
        """
        Handles 404 errors of paths.
        :param ex: Exception to return.
        :param text: Path captured by the route rules.

so the handler accepts the text keyword the catch-all routes pass to it, and the TypeError: create_app.<locals>.index() got an unexpected keyword argument 'text' from the report should no longer be reachable.

It arrived with the merge 153937f (2026-09-02). Of that merge's two parents, 8a7077c already had def index(ex=None, text=None) and fdeffcb still had def index(ex), which fits @ignaciosoto93's 2026-08-31 re-check finding the old signature.

Worth a fresh run of the documented Docker Compose flow against a build of current master before closing, since the last report was against the published image rather than the branch. I have closed my own PR for this (#545) as it is now a no-op.

[Eljees]

This looks fixed on master now, a couple of days after the last confirmation here.

faraday/server/app.py currently reads:

    @app.errorhandler(404)
    @app.route('/', defaults={'text': ''})
    @app.route('/<path:text>')
    def index(ex=None, text=None):
        """
        Handles 404 errors of paths.
        :param ex: Exception to return.
        :param text: Path captured by the route rules.

so the handler accepts the text keyword the catch-all routes pass to it, and the TypeError: create_app.<locals>.index() got an unexpected keyword argument 'text' from the report should no longer be reachable.

It arrived with the merge 153937f (2026-09-02). Of that merge's two parents, 8a7077c already had def index(ex=None, text=None) and fdeffcb still had def index(ex), which fits @ignaciosoto93's 2026-08-31 re-check finding the old signature.

Worth a fresh run of the documented Docker Compose flow against a build of current master before closing, since the last report was against the published image rather than the branch. I have closed my own PR for this (#545) as it is now a no-op.

[ignaciosoto93]

Thanks for the detailed report.

This has now been fixed.

We re-verified the documented Docker Compose flow against current master: the stack starts successfully and GET / returns HTTP 200 without the index() got an unexpected keyword argument text error.

The fix is included in Faraday v5.24.0, which updates the catch-all route handler to accept the routed path parameter.

Please upgrade to v5.24.0 or a newer release. Closing this issue as fixed.