Manager UI logo fails to load — broken external URL

Open Beginner friendly
#2,702 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start at the Manager UI entry point for /manager and search the frontend source for the hardcoded URL https://evolution-api.com/files/evo/evolution-logo-white.svg. Replace the broken logo reference with a working project asset or reference, then verify that the logo renders in the header without a failed external request.

Written by the indexing model from the issue text.

Description

bug
Welcome!
  • Yes, I have searched for similar issues on GitHub and found none.
What did you do?

Deployed Evolution API via Docker Compose (self-hosted) and opened the Manager UI at /manager in a browser.

What did you expect?

What did you expect?
The Evolution API logo to render in the top-left header of the Manager UI.

What did you observe instead of what you expected?

No logo is displayed — just broken alt text ("Logo"). Inspecting the DOM shows the element points to a hardcoded external URL:

Logo

Opening this URL directly in the browser returns a plain not found response, confirming the asset itself is missing/removed from the external host, rather than a local network/CORS issue.

Screenshots/Videos
Image Image

DevTools showing the broken pointing to the dead URL
Direct navigation to the URL showing not found

Which version of the API are you using?

2.3.7

What is your environment?

Docker

Other environment specifications

Evolution API version: v2.3.0 (also occurs on latest tag — please update if the image differs)
Deployment: Docker Compose, self-hosted
Database: PostgreSQL
Browser: Chrome (desktop)

If applicable, paste the log output

No response

Additional Notes

No response

Dominant language
TypeScript
Stars
9.6k
Forks
7.3k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evolution-foundation/evolution-api

All issues in evolution-foundation/evolution-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.