starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #5574] [bug]: Failed to get Collections on Self-Hosted Web App #2153

New issue

Closed

opened 2026-03-16 23:23:02 +03:00 by kerem · 5 comments

kerem commented

2026-03-16 23:23:02 +03:00

Owner

Originally created by @caturbgs on GitHub (Nov 12, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5574

Originally assigned to: @nivedin on GitHub.

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Firefox

Operating System

macOS

Bug Description

Every time i opening the app, the collections is always return empty. Even i'm already logged in on the web app. This happen too on the self-hosted desktop app.

Deployment Type

Self-hosted (on-prem deployment)

Version

2025.10.0

Originally created by @caturbgs on GitHub (Nov 12, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5574 Originally assigned to: @nivedin on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Firefox ### Operating System macOS ### Bug Description <img width="2928" height="1726" alt="Image" src="https://github.com/user-attachments/assets/4e1e2f8c-b52b-4731-a2cb-f5706eabf117" /> Every time i opening the app, the collections is always return empty. Even i'm already logged in on the web app. This happen too on the self-hosted desktop app. <img width="1466" height="859" alt="Image" src="https://github.com/user-attachments/assets/12056185-8a90-4e80-ad41-87f301d92366" /> ### Deployment Type Self-hosted (on-prem deployment) ### Version 2025.10.0

kerem

2026-03-16 23:23:02 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 23:23:18 +03:00

Author

Owner

@nivedin commented on GitHub (Nov 12, 2025):

https://github.com/hoppscotch/hoppscotch/issues/5541#issuecomment-3521248282

Thank you for the information, can you check the response of the graphql call while expanding

@nivedin commented on GitHub (Nov 12, 2025): https://github.com/hoppscotch/hoppscotch/issues/5541#issuecomment-3521248282 Thank you for the information, can you check the response of the graphql call while expanding

kerem commented

2026-03-16 23:23:23 +03:00

Author

Owner

@jimmybrancaccio commented on GitHub (Nov 12, 2025):

tl;dr

Make sure you haven't got any migrations which need to be applied. You can run pnpm dlx prisma migrate deploy to apply migrations.

I was experiencing this issue so I checked the logs of my hoppscotch_backend container. What I saw was:

Backend Server | [Nest] 21  - 11/12/2025, 11:37:38 PM   ERROR [ExceptionsHandler] PrismaClientKnownRequestError:
Backend Server | Invalid `this.prisma.mockServer.findMany()` invocation in
Backend Server | /dist/backend/dist/mock-server/mock-server.service.js:55:58
Backend Server |
Backend Server |   52     };
Backend Server |   53 }
Backend Server |   54 async getUserMockServers(userUid, args) {
Backend Server | → 55     const mockServers = await this.prisma.mockServer.findMany(
Backend Server | The table `public.MockServer` does not exist in the current database.

This made me realize that it sounded like there were some migrations to run. Checking the docs led me to this section. I exec'd into the backend container and ran pnpm dlx prisma migrate deploy:

6e011a7ce952:/dist/backend# pnpm dlx prisma migrate deploy
Downloading prisma@6.19.0: 17.62 MB/17.62 MB, done
Packages: +33
+++++++++++++++++++++++++++++++++
Progress: resolved 33, reused 0, downloaded 33, added 33, done
.cache/pnpm/dlx/19f309233addff80b18bfee071195ffcb7ef7b0e6dc4e37d96fec62dd1da1df6/19a7a72f04c-ec/node_modules/.pnpm/prisma@6.19.0/node_modules/prisma: Running preinstall script.cache/pnpm/dlx/19f309233addff80b18bfee071195ffcb7ef7b0e6dc4e37d96fec62dd1da1df6/19a7a72f04c-ec/node_modules/.pnpm/prisma@6.19.0/node_modules/prisma: Running preinstall script, done in 113ms
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "hoppscotch", schema "public" at "postgres17_postgres17:5432"

16 migrations found in prisma/migrations

Applying migration `20250725154928_timestamp_with_timezone`
Applying migration `20250818154928_fix_order_index`
Applying migration `20250822044741_order_index_unique_constraint`
Applying migration `20251016080714_mock_server`

The following migration(s) have been applied:

migrations/
  └─ 20250725154928_timestamp_with_timezone/
    └─ migration.sql
  └─ 20250818154928_fix_order_index/
    └─ migration.sql
  └─ 20250822044741_order_index_unique_constraint/
    └─ migration.sql
  └─ 20251016080714_mock_server/
    └─ migration.sql
      
All migrations have been successfully applied.

After clearing my web browsers cache and reloading the page I could see all the requests within my various collections again.

@jimmybrancaccio commented on GitHub (Nov 12, 2025): tl;dr Make sure you haven't got any migrations which need to be applied. You can run `pnpm dlx prisma migrate deploy` to apply migrations. -- I was experiencing this issue so I checked the logs of my `hoppscotch_backend` container. What I saw was: ``` Backend Server | [Nest] 21 - 11/12/2025, 11:37:38 PM ERROR [ExceptionsHandler] PrismaClientKnownRequestError: Backend Server | Invalid `this.prisma.mockServer.findMany()` invocation in Backend Server | /dist/backend/dist/mock-server/mock-server.service.js:55:58 Backend Server | Backend Server | 52 }; Backend Server | 53 } Backend Server | 54 async getUserMockServers(userUid, args) { Backend Server | → 55 const mockServers = await this.prisma.mockServer.findMany( Backend Server | The table `public.MockServer` does not exist in the current database. ``` This made me realize that it sounded like there were some migrations to run. Checking the docs led me to [this section](https://docs.hoppscotch.io/documentation/self-host/community-edition/install-and-build#running-migrations). I `exec'd` into the backend container and ran `pnpm dlx prisma migrate deploy`: ``` 6e011a7ce952:/dist/backend# pnpm dlx prisma migrate deploy Downloading prisma@6.19.0: 17.62 MB/17.62 MB, done Packages: +33 +++++++++++++++++++++++++++++++++ Progress: resolved 33, reused 0, downloaded 33, added 33, done .cache/pnpm/dlx/19f309233addff80b18bfee071195ffcb7ef7b0e6dc4e37d96fec62dd1da1df6/19a7a72f04c-ec/node_modules/.pnpm/prisma@6.19.0/node_modules/prisma: Running preinstall script.cache/pnpm/dlx/19f309233addff80b18bfee071195ffcb7ef7b0e6dc4e37d96fec62dd1da1df6/19a7a72f04c-ec/node_modules/.pnpm/prisma@6.19.0/node_modules/prisma: Running preinstall script, done in 113ms Prisma schema loaded from prisma/schema.prisma Datasource "db": PostgreSQL database "hoppscotch", schema "public" at "postgres17_postgres17:5432" 16 migrations found in prisma/migrations Applying migration `20250725154928_timestamp_with_timezone` Applying migration `20250818154928_fix_order_index` Applying migration `20250822044741_order_index_unique_constraint` Applying migration `20251016080714_mock_server` The following migration(s) have been applied: migrations/ └─ 20250725154928_timestamp_with_timezone/ └─ migration.sql └─ 20250818154928_fix_order_index/ └─ migration.sql └─ 20250822044741_order_index_unique_constraint/ └─ migration.sql └─ 20251016080714_mock_server/ └─ migration.sql All migrations have been successfully applied. ``` After clearing my web browsers cache and reloading the page I could see all the requests within my various collections again.

kerem commented

2026-03-16 23:23:28 +03:00

Author

Owner

@Symefa commented on GitHub (Nov 13, 2025):

Hi, I am @caturbgs co-worker, the answer provided by @jimmybrancaccio was spot on, our issue has been resolved.

running the command, we observed 50% memory spike during migrating

Here is the output of the command:

> Downloading Prisma engines for Node-API for linux-musl-openssl-3.0.x []
Prisma schema loaded from prisma/schema.prisma
Datasource "db": PostgreSQL database "hoppscotch", schema "public" at "sql
-proxy-ar-pg:5432"

16 migrations found in prisma/migrations

Applying migration `20250818154928_fix_order_index`
Applying migration `20250822044741_order_index_unique_constraint`
Applying migration `20251016080714_mock_server`

The following migration(s) have been applied:

migrations/
  └─ 20250818154928_fix_order_index/
    └─ migration.sql
  └─ 20250822044741_order_index_unique_constraint/
    └─ migration.sql
  └─ 20251016080714_mock_server/
    └─ migration.sql

All migrations have been successfully applied.

Thank you, the issue has been resolved.

@Symefa commented on GitHub (Nov 13, 2025): Hi, I am @caturbgs co-worker, the answer provided by @jimmybrancaccio was spot on, our issue has been resolved. running the command, we observed 50% memory spike during migrating <img width="385" height="218" alt="Image" src="https://github.com/user-attachments/assets/55eec906-c034-4f6d-98ba-8364bc40a31c" /> Here is the output of the command: ``` > Downloading Prisma engines for Node-API for linux-musl-openssl-3.0.x [] Prisma schema loaded from prisma/schema.prisma Datasource "db": PostgreSQL database "hoppscotch", schema "public" at "sql -proxy-ar-pg:5432" 16 migrations found in prisma/migrations Applying migration `20250818154928_fix_order_index` Applying migration `20250822044741_order_index_unique_constraint` Applying migration `20251016080714_mock_server` The following migration(s) have been applied: migrations/ └─ 20250818154928_fix_order_index/ └─ migration.sql └─ 20250822044741_order_index_unique_constraint/ └─ migration.sql └─ 20251016080714_mock_server/ └─ migration.sql All migrations have been successfully applied. ``` <img width="860" height="543" alt="Image" src="https://github.com/user-attachments/assets/5878b8b7-38a9-407e-b584-c33566c13378" /> Thank you, the issue has been resolved.

kerem commented

2026-03-16 23:23:33 +03:00

Author

Owner

@caturbgs commented on GitHub (Nov 13, 2025):

Turns out this was because the migration, thank you @jimmybrancaccio for the suggestion.

I'll close this issue

@caturbgs commented on GitHub (Nov 13, 2025): Turns out this was because the migration, thank you @jimmybrancaccio for the suggestion. I'll close this issue

kerem commented

2026-03-16 23:23:38 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Nov 13, 2025):

Glad this is resolved!

For future upgrades, we recommend checking the release notes before updating your self-hosted instance. They include important upgrade instructions and breaking changes.

For instance, the v2025.10.0 release notes had a mention about the DB migrations.

@jamesgeorge007 commented on GitHub (Nov 13, 2025): Glad this is resolved! For future upgrades, we recommend checking the [release notes](https://github.com/hoppscotch/hoppscotch/releases) before updating your self-hosted instance. They include important upgrade instructions and breaking changes. For instance, the [v2025.10.0 release notes](https://github.com/hoppscotch/hoppscotch/releases/tag/2025.10.0) had a mention about the DB migrations.

kerem referenced this issue

2026-03-17 01:14:40 +03:00

[PR #2153] [MERGED] refactor: improve the mobile layout. #3649

kerem referenced this issue

2026-03-17 01:18:13 +03:00

[PR #2295] [CLOSED] Update Traditional Chinese translation #3714