mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5846] [bug]: Cannot create collections or requests in Team Workspaces (Hoppscotch 2026.1.x) #2291
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#2291
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 @roopepaajanen on GitHub (Feb 6, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5846
Originally assigned to: @mirarifhasan on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
Windows
Bug Description
Version: Hoppscotch 2026.1.x
Deployment: Distributed Kubernetes (self-hosted)
Database: PostgreSQL
Severity: Blocking — team workspaces unusable
❌Problem
In Hoppscotch 2026.1.x, we cannot create collections or requests in any team workspace.
Only the personal workspace works. All team workspace operations fail.
We can access old requests, send them, modify and save them. Creation of new is only failing
✅ Expected Behavior
Users should be able to create collections and requests in team workspaces.
❌ Actual Behavior
Backend returns errors when creating team collections:
Backend logs
DB migration
The DB migration is executed succesfully
Deployment Type
Self-hosted (on-prem deployment)
Version
2026.1.x
@roopepaajanen commented on GitHub (Feb 6, 2026):
We are running on a light soft fork. Here is the changes we have applied, if it makes a difference in this case.
We authenticate users through proxy (proxyscotch), for the service to be able to access our Microsoft auth process:
microsoft.strategy.js
Also, we add the following packages to support our custom config
Here is the paths we use to add these custom modifications
@roopepaajanen commented on GitHub (Feb 6, 2026):
We were able to solve the issue internally by adding more detailed db configurations to our cluster/pod.