mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5680] [bug]: Error: TypeError: Cannot read properties of undefined (reading 'searchParams') #2205
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2205
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @xddai1201 on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5680
Originally assigned to: @mirarifhasan on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
Linux
Bug Description
Description
when install hoppscotch by AIO docker image:hoppscotch/hoppscotch:2025.11.0, it failing with
Error: TypeError: Cannot read properties of undefined (reading 'searchParams').
Deployment Type
Self-hosted (on-prem deployment)
Version
2025.11.0
@mirarifhasan commented on GitHub (Dec 10, 2025):
@xddai1201
Thanks for the bug report. Would you mind to provide
DATABASE_URLvalue you're using in the.envfile? Feel free to mask the credentials from the URL string.Also, thanks for the screenshot — Actually, the first part isn’t fully visible in the screenshot. Could you share the complete stack trace from the beginning?
@mirarifhasan commented on GitHub (Jan 28, 2026):
Closing this issue due to inactivity.
If you’re still experiencing this issue on the latest version of the app, feel free to reopen it and share any additional details. We’ll be happy to take another look.