Manager UI logo fails to load — broken external URL
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
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:
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
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evolution-foundation/evolution-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-api#2700 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
All issues in evolution-foundation/evolution-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·