[GH-ISSUE #4859] [bug]: Root page fails to load with status code `404` in Desktop App on Windows

kerem commented

2026-03-16 21:57:05 +03:00

Owner

Originally created by @a224327780 on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4859

Is there an existing issue for this?

I have searched the existing issues

Current behavior

Steps to reproduce

Environment

Production

Version

Cloud

Originally created by @a224327780 on GitHub (Mar 8, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4859 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behavior ![Image](https://github.com/user-attachments/assets/92745e85-7bca-4a4e-9b09-2074572f912b) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/b6b2d03e-37c2-4c08-9c72-19efd28d0dc6) ### Environment Production ### Version Cloud

kerem

2026-03-16 21:57:05 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 21:57:22 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Mar 10, 2025):

Hi, thanks for the report, I'm unable to reproduce this on Windows 11 26100.3323.

So it will be very helpful if you could let me know your Windows version and build, if there are any logs in the developer console and how the network calls look like in the networks tab in the same console.

You can open the console like so:

Press F12, or
Press Ctrl+Shift+I, or
Right-click the page and then select Inspect

See Microsoft DevTools for more details, it would look something like this:

Console	Networks Tab

@CuriousCorrelation commented on GitHub (Mar 10, 2025): Hi, thanks for the report, I'm unable to reproduce this on [Windows 11 26100.3323](https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information). So it will be very helpful if you could let me know your Windows version and build, if there are any logs in the developer console and how the network calls look like in the networks tab in the same console. You can open the console like so: - Press F12, or - Press Ctrl+Shift+I, or - Right-click the page and then select Inspect See [Microsoft DevTools](https://learn.microsoft.com/en-us/microsoft-edge/webview2/how-to/debug-devtools?tabs=dotnetcsharp) for more details, it would look something like this: | Console | Networks Tab | | --- | --- | | ![Image](https://github.com/user-attachments/assets/fdece227-2ccc-453b-bf8d-9b11c987017c) | ![Image](https://github.com/user-attachments/assets/ff76f407-c6e2-4c29-be1a-27a4f57c18f7) |

kerem commented

2026-03-16 21:57:28 +03:00

Author

Owner

@a224327780 commented on GitHub (Mar 13, 2025):

win10 22H2

@a224327780 commented on GitHub (Mar 13, 2025): win10 22H2 ![Image](https://github.com/user-attachments/assets/c4646dc8-3657-4713-b4e5-3ad166553f6e)

kerem commented

2026-03-16 21:57:33 +03:00

Author

Owner

@Saintel commented on GitHub (Mar 15, 2025):

I have the same issue on 23H2
Can you please explain how my browser understands what is host app.hoppscotch? I think, he makes nslookup and there’s no such DNS record

@Saintel commented on GitHub (Mar 15, 2025): I have the same issue on 23H2 Can you please explain how my browser understands what is host app.hoppscotch? I think, he makes nslookup and there’s no such DNS record

kerem commented

2026-03-16 21:57:38 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Mar 15, 2025):

We have been unable to reproduce this issue across multiple Windows environments, including both physical machines and virtual machines.

Just for additional context so you would be able to diagnose this further to understand if this is a specific Windows config or setup related oddity or a bug with the app - our desktop app is built with Tauri v2, which handles URI scheme protocols differently depending on the operating system:

On macOS and Linux: Uses the app://hoppscotch schema
On Windows: Uses the http://app.hoppscotch schema

In both cases, requests should properly route to the application's resources. We implement this using the register_uri_scheme_protocol , which you can see in our codebase here: github.com/hoppscotch/hoppscotch@212cd4969d/packages/hoppscotch-desktop/plugin-workspace/tauri-plugin-appload/src/lib.rs (L148)

Under the hood, Tauri implements this using the Windows WebView2 AddWebResourceRequestedFilter API.

The above screenshot is from Windows 10 Pro 22H2 19045.5608 live machine.

@CuriousCorrelation commented on GitHub (Mar 15, 2025): We have been unable to reproduce this issue across multiple Windows environments, including both physical machines and virtual machines. Just for additional context so you would be able to diagnose this further to understand if this is a specific Windows config or setup related oddity or a bug with the app - our desktop app is built with [Tauri v2](https://v2.tauri.app/), which handles URI scheme protocols differently depending on the operating system: - On macOS and Linux: Uses the `app://hoppscotch` schema - On Windows: Uses the `http://app.hoppscotch` schema In both cases, requests should properly route to the application's resources. We implement this using the [register_uri_scheme_protocol ](https://docs.rs/tauri/latest/tauri/struct.Builder.html#method.register_uri_scheme_protocol), which you can see in our codebase here: https://github.com/hoppscotch/hoppscotch/blob/212cd4969d76de131426482a0e387ca53065c961/packages/hoppscotch-desktop/plugin-workspace/tauri-plugin-appload/src/lib.rs#L148 Under the hood, Tauri implements this using the Windows WebView2 [AddWebResourceRequestedFilter](https://learn.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2.addwebresourcerequestedfilter?view=webview2-dotnet-1.0.3124.44) API. ![Image showing the error](https://github.com/user-attachments/assets/45ac179e-2dd2-48eb-82d4-6f0b50a19415) The above screenshot is from Windows 10 Pro 22H2 19045.5608 live machine.

kerem commented

2026-03-16 21:57:43 +03:00

Author

Owner

@Saintel commented on GitHub (Mar 27, 2025):

@CuriousCorrelation thank you for explaining.
I've never seen a registration new custom URI-scheme for existing URI scheme before.
For me it's a little strange, that http://* must handle with another app (not browser).

Everything I've seen before it's new URI, such as app://, rdm://, office-apps A have an expirience for registration custom vnc URI-scheme via registry on Windows, and it's work.

@Saintel commented on GitHub (Mar 27, 2025): @CuriousCorrelation thank you for explaining. I've never seen a registration new custom URI-scheme for existing URI scheme before. For me it's a little strange, that `http://*` must handle with another app (not browser). Everything I've seen before it's new URI, such as `app://`, `rdm://`, [office-apps](https://learn.microsoft.com/en-us/office/client-developer/office-uri-schemes) A have an expirience for registration custom `vnc` URI-scheme via registry on Windows, and it's work.

kerem commented

2026-03-16 21:57:48 +03:00

Author

Owner

@Saintel commented on GitHub (Mar 28, 2025):

i tried to run as administrator, i tried to disable AntiVirus during installation.
Is there any way to collect logs for you?

@Saintel commented on GitHub (Mar 28, 2025): i tried to run as administrator, i tried to disable AntiVirus during installation. Is there any way to collect logs for you?

kerem commented

2026-03-16 21:57:53 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Mar 28, 2025):

Hi @Saintel, http://app.hoppscotch I believe is fully contained in the app context and doesn't globally intercept all HTTP traffic on the system like deep-linking. This is handled through WebView2's resource request filtering, which you can read more about in Tauri's documentation and with the code snippets here.

Regarding logs, the desktop app does have logging capabilities. To access these, you can run the app in dev mode with the RUST_LOG=debug environment variable which should show you the exact logs to the stdout. The app requires multiple steps during the build process as described here (dev vs build modes):

github.com/hoppscotch/hoppscotch@86c0bb619d/packages/hoppscotch-desktop/package.json (L11-L12)

If you encounter any troubles with the above one-line command, you can split them up into parts and run them manually. And simply add or set the env var right before the final command like so RUST_LOG=debug pnpm tauri dev. For Window, setting the env var is slightly different.

@CuriousCorrelation commented on GitHub (Mar 28, 2025): Hi @Saintel, `http://app.hoppscotch` I believe is fully contained in the app context and doesn't globally intercept all HTTP traffic on the system like [deep-linking](https://v2.tauri.app/plugin/deep-linking/). This is handled through WebView2's resource request filtering, which you can read more about in [Tauri's documentation and with the code snippets here](https://docs.rs/tauri/latest/src/tauri/app.rs.html#1918-1939). Regarding logs, the desktop app does have logging capabilities. To access these, you can run the app in `dev` mode with the `RUST_LOG=debug` environment variable which should show you the exact logs to the `stdout`. The app requires multiple steps during the build process as described here (`dev` vs `build` modes): https://github.com/hoppscotch/hoppscotch/blob/86c0bb619d9fc41484de08d2454242f1194d18bd/packages/hoppscotch-desktop/package.json#L11-L12 If you encounter any troubles with the above one-line command, you can split them up into parts and run them manually. And simply add or set the env var right before the final command like so `RUST_LOG=debug pnpm tauri dev`. For Window, setting the env var is [slightly different](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/set_1).

kerem commented

2026-03-16 21:57:58 +03:00

Author

Owner

@amishsthapit commented on GitHub (Mar 28, 2025):

I am also facing same issue. The app works on the first launch. But after that I just get the error message.

@amishsthapit commented on GitHub (Mar 28, 2025): I am also facing same issue. The app works on the first launch. But after that I just get the error message. ![Image](https://github.com/user-attachments/assets/4aed7508-de65-4c05-98a3-8482c9db4719)

kerem commented

2026-03-16 21:58:03 +03:00

Author

Owner

@dhayanands commented on GitHub (Apr 9, 2025):

Hi, The issue still persists. Was anyone able to find a workaround?

@dhayanands commented on GitHub (Apr 9, 2025): Hi, The issue still persists. Was anyone able to find a workaround?

kerem commented

2026-03-16 21:58:08 +03:00

Author

Owner

@sLIDe5 commented on GitHub (Apr 11, 2025):

Having the same issue with fresh v25.3.1-0 install on Windows 11 Pro 24H2 (26100.3775)

@sLIDe5 commented on GitHub (Apr 11, 2025): Having the same issue with fresh `v25.3.1-0` install on Windows 11 Pro 24H2 (26100.3775)

kerem commented

2026-03-16 21:58:13 +03:00

Author

Owner

@AndreKR commented on GitHub (Apr 14, 2025):

I'm also seeing this.

Windows 10 Pro 22H2, Edge 135.0.3179.73

I tried doing the dev mode thing but I am unable to build the app.

Details about the failing build

Part of the pnpm install process is running pnpm run postinstall in packages\hoppscotch-backend. This fails with a lot of errors relating to prisma:

> prisma generate && pnpm run generate-gql-sdl

Prisma schema loaded from prisma\schema.prisma

✔ Generated Prisma Client (v5.20.0) to .\..\..\node_modules\.pnpm\@prisma+client@5.20.0_prisma@5.20.0\node_modules\@prisma\client in 250ms

Start by importing your Prisma Client (See: http://pris.ly/d/importing-client)

Tip: Need your database queries to be 1000x faster? Accelerate offers you that and more: https://pris.ly/tip-2-accelerate


> hoppscotch-backend@2025.3.1 generate-gql-sdl C:\dev\projects\hoppscotch\packages\hoppscotch-backend
> cross-env GQL_SCHEMA_EMIT_LOCATION='../../../gql-gen/backend-schema.gql' GENERATE_GQL_SCHEMA=true WHITELISTED_ORIGINS='' nest start

src/access-token/access-token.service.ts:13:10 - error TS2305: Module '"@prisma/client"' has no exported member 'PersonalAccessToken'.

13 import { PersonalAccessToken } from '@prisma/client';
            ~~~~~~~~~~~~~~~~~~~
src/auth/auth.service.ts:29:10 - error TS2305: Module '"@prisma/client"' has no exported member 'VerificationToken'.

29 import { VerificationToken } from '@prisma/client';
            ~~~~~~~~~~~~~~~~~
src/health/health.controller.ts:21:59 - error TS2345: Argument of type 'PrismaService' is not assignable to parameter of type 'PrismaClient'.
  Property '$queryRawUnsafe' is missing in type 'PrismaService' but required in type 'PrismaClientSQL'.

21       async () => this.prismaHealth.pingCheck('database', this.prisma),
                                                             ~~~~~~~~~~~

  ../../node_modules/.pnpm/@nestjs+terminus@10.2.3_@ne_5056148dfa9f33df69944cc81ad23f6b/node_modules/@nestjs/terminus/dist/health-indicator/database/prisma.health.d.ts:9:5
    9     $queryRawUnsafe: (query: string) => any;
          ~~~~~~~~~~~~~~~
    '$queryRawUnsafe' is declared here.
src/infra-config/helper.ts:11:10 - error TS2305: Module '"@prisma/client"' has no exported member 'InfraConfig'.

11 import { InfraConfig } from '@prisma/client';
            ~~~~~~~~~~~
src/infra-config/infra-config.service.ts:4:10 - error TS2305: Module '"@prisma/client"' has no exported member 'InfraConfig'.

[...]

I googled and fiddled around a bit and decided to copy packages\hoppscotch-backend\node_modules\.prisma to packages\hoppscotch-backend\node_modules\@prisma\client\.prisma because I saw some paths in @prisma\client that seemed to refer to .prisma. (I'm not really familiar with nest and prisma.)

But I'm still getting an error:

> hoppscotch-backend@2025.3.1 generate-gql-sdl C:\dev\projects\hoppscotch\packages\hoppscotch-backend
> cross-env GQL_SCHEMA_EMIT_LOCATION='../../../gql-gen/backend-schema.gql' GENERATE_GQL_SCHEMA=true WHITELISTED_ORIGINS='' nest start

C:\dev\projects\hoppscotch\packages\hoppscotch-backend\dist\user\user.resolver.js:68
    __metadata("design:paramtypes", [typeof (_a = typeof AuthUser_1.AuthUser !== "undefined" && AuthUser_1.AuthUser) === "function" ? _a : Object]),
                                                         ^

ReferenceError: AuthUser_1 is not defined
    at Object.<anonymous> (C:\dev\projects\hoppscotch\packages\hoppscotch-backend\dist\user\user.resolver.js:68:58)
    at Module._compile (node:internal/modules/cjs/loader:1369:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1427:10)
    at Module.load (node:internal/modules/cjs/loader:1206:32)
    at Module._load (node:internal/modules/cjs/loader:1022:12)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:179:18)
    at Object.<anonymous> (C:\dev\projects\hoppscotch\packages\hoppscotch-backend\dist\user\user.module.js:11:25)
    at Module._compile (node:internal/modules/cjs/loader:1369:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1427:10)

Node.js v20.12.1
 ELIFECYCLE  Command failed with exit code 1.
 ELIFECYCLE  Command failed with exit code 1.

Can you think of another way to shed some light on this?

Is there maybe a way to check which filters have been registered using AddWebResourceRequestedFilter?

@AndreKR commented on GitHub (Apr 14, 2025): I'm also seeing this. Windows 10 Pro 22H2, Edge 135.0.3179.73 ![Image](https://github.com/user-attachments/assets/978b5292-73e6-4a64-b3c0-f37a370dc1b4) I tried doing the dev mode thing but I am unable to build the app. <details><summary>Details about the failing build</summary> <p> Part of the `pnpm install` process is running `pnpm run postinstall` in `packages\hoppscotch-backend`. This fails with a lot of errors relating to prisma: ``` > prisma generate && pnpm run generate-gql-sdl Prisma schema loaded from prisma\schema.prisma ✔ Generated Prisma Client (v5.20.0) to .\..\..\node_modules\.pnpm\@prisma+client@5.20.0_prisma@5.20.0\node_modules\@prisma\client in 250ms Start by importing your Prisma Client (See: http://pris.ly/d/importing-client) Tip: Need your database queries to be 1000x faster? Accelerate offers you that and more: https://pris.ly/tip-2-accelerate > hoppscotch-backend@2025.3.1 generate-gql-sdl C:\dev\projects\hoppscotch\packages\hoppscotch-backend > cross-env GQL_SCHEMA_EMIT_LOCATION='../../../gql-gen/backend-schema.gql' GENERATE_GQL_SCHEMA=true WHITELISTED_ORIGINS='' nest start src/access-token/access-token.service.ts:13:10 - error TS2305: Module '"@prisma/client"' has no exported member 'PersonalAccessToken'. 13 import { PersonalAccessToken } from '@prisma/client'; ~~~~~~~~~~~~~~~~~~~ src/auth/auth.service.ts:29:10 - error TS2305: Module '"@prisma/client"' has no exported member 'VerificationToken'. 29 import { VerificationToken } from '@prisma/client'; ~~~~~~~~~~~~~~~~~ src/health/health.controller.ts:21:59 - error TS2345: Argument of type 'PrismaService' is not assignable to parameter of type 'PrismaClient'. Property '$queryRawUnsafe' is missing in type 'PrismaService' but required in type 'PrismaClientSQL'. 21 async () => this.prismaHealth.pingCheck('database', this.prisma), ~~~~~~~~~~~ ../../node_modules/.pnpm/@nestjs+terminus@10.2.3_@ne_5056148dfa9f33df69944cc81ad23f6b/node_modules/@nestjs/terminus/dist/health-indicator/database/prisma.health.d.ts:9:5 9 $queryRawUnsafe: (query: string) => any; ~~~~~~~~~~~~~~~ '$queryRawUnsafe' is declared here. src/infra-config/helper.ts:11:10 - error TS2305: Module '"@prisma/client"' has no exported member 'InfraConfig'. 11 import { InfraConfig } from '@prisma/client'; ~~~~~~~~~~~ src/infra-config/infra-config.service.ts:4:10 - error TS2305: Module '"@prisma/client"' has no exported member 'InfraConfig'. [...] ``` I googled and fiddled around a bit and decided to copy `packages\hoppscotch-backend\node_modules\.prisma` to `packages\hoppscotch-backend\node_modules\@prisma\client\.prisma` because I saw some paths in `@prisma\client` that seemed to refer to `.prisma`. (I'm not really familiar with nest and prisma.) But I'm still getting an error: ``` > hoppscotch-backend@2025.3.1 generate-gql-sdl C:\dev\projects\hoppscotch\packages\hoppscotch-backend > cross-env GQL_SCHEMA_EMIT_LOCATION='../../../gql-gen/backend-schema.gql' GENERATE_GQL_SCHEMA=true WHITELISTED_ORIGINS='' nest start C:\dev\projects\hoppscotch\packages\hoppscotch-backend\dist\user\user.resolver.js:68 __metadata("design:paramtypes", [typeof (_a = typeof AuthUser_1.AuthUser !== "undefined" && AuthUser_1.AuthUser) === "function" ? _a : Object]), ^ ReferenceError: AuthUser_1 is not defined at Object.<anonymous> (C:\dev\projects\hoppscotch\packages\hoppscotch-backend\dist\user\user.resolver.js:68:58) at Module._compile (node:internal/modules/cjs/loader:1369:14) at Module._extensions..js (node:internal/modules/cjs/loader:1427:10) at Module.load (node:internal/modules/cjs/loader:1206:32) at Module._load (node:internal/modules/cjs/loader:1022:12) at Module.require (node:internal/modules/cjs/loader:1231:19) at require (node:internal/modules/helpers:179:18) at Object.<anonymous> (C:\dev\projects\hoppscotch\packages\hoppscotch-backend\dist\user\user.module.js:11:25) at Module._compile (node:internal/modules/cjs/loader:1369:14) at Module._extensions..js (node:internal/modules/cjs/loader:1427:10) Node.js v20.12.1 ELIFECYCLE Command failed with exit code 1. ELIFECYCLE Command failed with exit code 1. ``` </p> </details> Can you think of another way to shed some light on this? Is there maybe a way to check which filters have been registered using `AddWebResourceRequestedFilter`?

kerem commented

2026-03-16 21:58:18 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 14, 2025):

@AndreKR Thanks for trying the build. The Prisma errors you're encountering (missing client exports for PersonalAccessToken, VerificationToken, etc.) are part of some longstanding Prisma issues specifically on Windows platforms due to how Windows handles path resolution.

The most reliable fix I've found is to run pnpm clean (or even git clean -xdf in some cases. It clears every file in the git directory which is NOT part of the monorepo) followed by pnpm install --shamefully-hoist. This flag modifies how dependencies are hoisted in the node_modules.

Regarding the 404 error: I'm working on implementing persistent logging for desktop app prod build/release build, that will create and redirect logs to local storage that will make troubleshooting these types of issues much easier in the future. Aiming to include this in an upcoming release.

In the meantime, if anyone discovers a workaround, please share it here. We're continuing to investigate why this affects some Windows configurations but not others.

@CuriousCorrelation commented on GitHub (Apr 14, 2025): @AndreKR Thanks for trying the build. The Prisma errors you're encountering (missing client exports for `PersonalAccessToken`, `VerificationToken`, etc.) are part of some longstanding Prisma issues specifically on Windows platforms due to how Windows handles path resolution. The most reliable fix I've found is to run `pnpm clean` (or even `git clean -xdf` in some cases. It clears every file in the `git` directory which is NOT part of the monorepo) followed by `pnpm install --shamefully-hoist`. This flag modifies how dependencies are hoisted in the `node_modules`. Regarding the `404` error: I'm working on implementing persistent logging for desktop app prod build/release build, that will create and redirect logs to local storage that will make troubleshooting these types of issues much easier in the future. Aiming to include this in an upcoming release. In the meantime, if anyone discovers a workaround, please share it here. We're continuing to investigate why this affects some Windows configurations but not others.

kerem commented

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

Author

Owner

@dhayanands commented on GitHub (Apr 16, 2025):

Going to %TEMP% on windows explorer and deleting the temporary files solved the 404 error for me.

@dhayanands commented on GitHub (Apr 16, 2025): Going to %TEMP% on windows explorer and deleting the temporary files solved the 404 error for me.

kerem commented

2026-03-16 21:58:29 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 30, 2025):

Hello everyone! The latest update of the desktop app (v25.4.0) now includes file-based rotating logs, a feature specifically implemented to address hard-to-reproduce problems like the one you are experiencing.

As @dhayanands mentioned, clearing your Windows %TEMP% can resolve this issue:

Going to %TEMP% on windows explorer and deleting the temporary files solved the 404 error for me.

If you're still experiencing this 404 error after trying the cleanup solution, please update to the latest version and if the issue persists, you can now share your logs here to help diagnose the problem (be sure to anonymize it if necessary!).

The log files are located at:

Windows: C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log
macOS: ~/Library/Logs/io.hoppscotch.desktop/io.hoppscotch.desktop.log
Linux: ~/.local/share/io.hoppscotch.desktop/logs/io.hoppscotch.desktop.log

For more info see the PR https://github.com/hoppscotch/hoppscotch/pull/5009

The system automatically rotates logs when they reach 10MB, keeping up to 5 files for history (maximum of 50MB total).

@CuriousCorrelation commented on GitHub (Apr 30, 2025): Hello everyone! The latest update of the desktop app ([v25.4.0](https://hoppscotch.com/download)) now includes file-based rotating logs, a feature specifically implemented to address hard-to-reproduce problems like the one you are experiencing. As @dhayanands mentioned, clearing your Windows `%TEMP%` can resolve this issue: > Going to %TEMP% on windows explorer and deleting the temporary files solved the 404 error for me. If you're still experiencing this `404` error after trying the cleanup solution, please update to the latest version and if the issue persists, you can now share your logs here to help diagnose the problem (be sure to anonymize it if necessary!). The log files are located at: - Windows: `C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log` - macOS: `~/Library/Logs/io.hoppscotch.desktop/io.hoppscotch.desktop.log` - Linux: `~/.local/share/io.hoppscotch.desktop/logs/io.hoppscotch.desktop.log` For more info see the PR https://github.com/hoppscotch/hoppscotch/pull/5009 The system automatically rotates logs when they reach 10MB, keeping up to 5 files for history (maximum of 50MB total).

kerem commented

2026-03-16 21:58:34 +03:00

Author

Owner

@Saintel commented on GitHub (Apr 30, 2025):

Thank you for logging!

After clearing TEMP the issue is still reproduced.
logs:

2025-04-30T11:16:14.950865Z  INFO main ThreadId(01) hoppscotch_desktop_lib::logger: Logging initialized with single file log_file=C:\Users\my_user\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log
2025-04-30T11:16:14.950883Z  INFO main ThreadId(01) hoppscotch_desktop_lib: Logger setup complete
2025-04-30T11:16:14.952768Z  INFO main ThreadId(01) hoppscotch_desktop_lib: Selected server port: 24399
2025-04-30T11:16:14.952787Z  INFO main ThreadId(01) hoppscotch_desktop_lib: Initializing server with pre-selected port port=24399
2025-04-30T11:16:14.952806Z  INFO main ThreadId(01) hoppscotch_desktop_lib::server: Beginning server initialization
2025-04-30T11:16:14.952882Z  INFO main ThreadId(01) hoppscotch_desktop_lib: Server initialization complete port=24399
2025-04-30T11:16:14.952887Z  INFO main ThreadId(01) hoppscotch_desktop_lib: Configuring deep link handler app_name=Hoppscotch
2025-04-30T11:16:14.952896Z  INFO main ThreadId(01) hoppscotch_desktop_lib: Starting Hoppscotch Desktop v25.4.0
2025-04-30T11:16:14.952905Z  INFO tokio-runtime-worker ThreadId(14) hoppscotch_desktop_lib::server: Starting HTTP server address=127.0.0.1:24399 port=24399
2025-04-30T11:16:14.953534Z  INFO tokio-runtime-worker ThreadId(14) hoppscotch_desktop_lib::server: Server bound successfully local_addr=127.0.0.1:24399
2025-04-30T11:16:14.953545Z  INFO tokio-runtime-worker ThreadId(14) hoppscotch_desktop_lib::server: Server starting
2025-04-30T11:16:15.082205Z DEBUG tokio-runtime-worker ThreadId(14) reqwest::connect: starting new connection: https://releases.hoppscotch.com/    
2025-04-30T11:16:15.249006Z DEBUG tokio-runtime-worker ThreadId(14) hyper_util::client::legacy::connect::http: connecting to 3.75.10.80:443
2025-04-30T11:16:15.392373Z DEBUG tokio-runtime-worker ThreadId(09) hyper_util::client::legacy::connect::http: connected to 3.75.10.80:443
2025-04-30T11:16:15.853776Z  INFO tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Loading bundle options=LoadOptions { bundle_name: "Hoppscotch", inline: false, window: WindowOptions { title: "Hoppscotch", width: 800.0, height: 600.0, resizable: true } } bundle=Hoppscotch window_label=Hoppscotch-curr
2025-04-30T11:16:15.853813Z DEBUG tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Generated app URL url=app://hoppscotch/
2025-04-30T11:16:15.857730Z  INFO tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Closing main window
2025-04-30T11:16:16.074729Z  INFO tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Bundle loaded successfully response=LoadResponse { success: true, window_label: "Hoppscotch-curr" }
2025-04-30T11:16:16.114689Z  INFO                 main ThreadId(01) tauri_plugin_appload: Incoming URI request
2025-04-30T11:16:16.114709Z DEBUG                 main ThreadId(01) tauri_plugin_appload: Handling app URI scheme request. url=app://hoppscotch/ thread_id=ThreadId(1)
2025-04-30T11:16:16.114721Z  INFO                 main ThreadId(01) tauri_plugin_appload: Got URI handler
2025-04-30T11:16:16.114732Z DEBUG                 main ThreadId(01) tauri_plugin_appload::uri::handler: Handling request host=hoppscotch path=
2025-04-30T11:16:16.114740Z DEBUG                 main ThreadId(01) tauri_plugin_appload::uri::handler: Fetching file content. host=hoppscotch path= resolved_path=index.html
2025-04-30T11:16:16.114752Z  INFO                 main ThreadId(01) tauri_plugin_appload::cache::manager: Retrieving file bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html
2025-04-30T11:16:16.114759Z DEBUG                 main ThreadId(01) tauri_plugin_appload::cache::manager: Cache lookup attempt bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html thread_id=ThreadId(1)
2025-04-30T11:16:16.114766Z  INFO                 main ThreadId(01) tauri_plugin_appload::cache::store: Retrieving file from cache. key="hoppscotch:index.html"
2025-04-30T11:16:16.114779Z DEBUG                 main ThreadId(01) tauri_plugin_appload::cache::store: Cache access attempt details key="hoppscotch:index.html" thread_id=ThreadId(1) hot_cache_len=0 disk_cache_len=0
2025-04-30T11:16:16.114795Z DEBUG                 main ThreadId(01) tauri_plugin_appload::cache::store: File not found in hot cache. Checking disk cache. key="hoppscotch:index.html"
2025-04-30T11:16:16.114806Z  WARN                 main ThreadId(01) tauri_plugin_appload::cache::store: File not found in cache. key="hoppscotch:index.html"
2025-04-30T11:16:16.114814Z ERROR                 main ThreadId(01) tauri_plugin_appload::uri::handler: Failed to retrieve file content error=Cache error: Cache entry not found: hoppscotch:index.html host=hoppscotch path=
2025-04-30T11:16:17.201843Z  INFO                 main ThreadId(01) tauri_plugin_appload: Incoming URI request
2025-04-30T11:16:17.201880Z DEBUG                 main ThreadId(01) tauri_plugin_appload: Handling app URI scheme request. url=app://hoppscotch/ thread_id=ThreadId(1)
2025-04-30T11:16:17.201911Z  INFO                 main ThreadId(01) tauri_plugin_appload: Got URI handler
2025-04-30T11:16:17.201919Z DEBUG                 main ThreadId(01) tauri_plugin_appload::uri::handler: Handling request host=hoppscotch path=
2025-04-30T11:16:17.201927Z DEBUG                 main ThreadId(01) tauri_plugin_appload::uri::handler: Fetching file content. host=hoppscotch path= resolved_path=index.html
2025-04-30T11:16:17.201936Z  INFO                 main ThreadId(01) tauri_plugin_appload::cache::manager: Retrieving file bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html
2025-04-30T11:16:17.201943Z DEBUG                 main ThreadId(01) tauri_plugin_appload::cache::manager: Cache lookup attempt bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html thread_id=ThreadId(1)
2025-04-30T11:16:17.201951Z  INFO                 main ThreadId(01) tauri_plugin_appload::cache::store: Retrieving file from cache. key="hoppscotch:index.html"
2025-04-30T11:16:17.201960Z DEBUG                 main ThreadId(01) tauri_plugin_appload::cache::store: Cache access attempt details key="hoppscotch:index.html" thread_id=ThreadId(1) hot_cache_len=0 disk_cache_len=0
2025-04-30T11:16:17.201970Z DEBUG                 main ThreadId(01) tauri_plugin_appload::cache::store: File not found in hot cache. Checking disk cache. key="hoppscotch:index.html"
2025-04-30T11:16:17.201976Z  WARN                 main ThreadId(01) tauri_plugin_appload::cache::store: File not found in cache. key="hoppscotch:index.html"
2025-04-30T11:16:17.201983Z ERROR                 main ThreadId(01) tauri_plugin_appload::uri::handler: Failed to retrieve file content error=Cache error: Cache entry not found: hoppscotch:index.html host=hoppscotch path=

@Saintel commented on GitHub (Apr 30, 2025): Thank you for logging! After clearing `TEMP` the issue is still reproduced. logs: ``` 2025-04-30T11:16:14.950865Z INFO main ThreadId(01) hoppscotch_desktop_lib::logger: Logging initialized with single file log_file=C:\Users\my_user\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log 2025-04-30T11:16:14.950883Z INFO main ThreadId(01) hoppscotch_desktop_lib: Logger setup complete 2025-04-30T11:16:14.952768Z INFO main ThreadId(01) hoppscotch_desktop_lib: Selected server port: 24399 2025-04-30T11:16:14.952787Z INFO main ThreadId(01) hoppscotch_desktop_lib: Initializing server with pre-selected port port=24399 2025-04-30T11:16:14.952806Z INFO main ThreadId(01) hoppscotch_desktop_lib::server: Beginning server initialization 2025-04-30T11:16:14.952882Z INFO main ThreadId(01) hoppscotch_desktop_lib: Server initialization complete port=24399 2025-04-30T11:16:14.952887Z INFO main ThreadId(01) hoppscotch_desktop_lib: Configuring deep link handler app_name=Hoppscotch 2025-04-30T11:16:14.952896Z INFO main ThreadId(01) hoppscotch_desktop_lib: Starting Hoppscotch Desktop v25.4.0 2025-04-30T11:16:14.952905Z INFO tokio-runtime-worker ThreadId(14) hoppscotch_desktop_lib::server: Starting HTTP server address=127.0.0.1:24399 port=24399 2025-04-30T11:16:14.953534Z INFO tokio-runtime-worker ThreadId(14) hoppscotch_desktop_lib::server: Server bound successfully local_addr=127.0.0.1:24399 2025-04-30T11:16:14.953545Z INFO tokio-runtime-worker ThreadId(14) hoppscotch_desktop_lib::server: Server starting 2025-04-30T11:16:15.082205Z DEBUG tokio-runtime-worker ThreadId(14) reqwest::connect: starting new connection: https://releases.hoppscotch.com/ 2025-04-30T11:16:15.249006Z DEBUG tokio-runtime-worker ThreadId(14) hyper_util::client::legacy::connect::http: connecting to 3.75.10.80:443 2025-04-30T11:16:15.392373Z DEBUG tokio-runtime-worker ThreadId(09) hyper_util::client::legacy::connect::http: connected to 3.75.10.80:443 2025-04-30T11:16:15.853776Z INFO tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Loading bundle options=LoadOptions { bundle_name: "Hoppscotch", inline: false, window: WindowOptions { title: "Hoppscotch", width: 800.0, height: 600.0, resizable: true } } bundle=Hoppscotch window_label=Hoppscotch-curr 2025-04-30T11:16:15.853813Z DEBUG tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Generated app URL url=app://hoppscotch/ 2025-04-30T11:16:15.857730Z INFO tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Closing main window 2025-04-30T11:16:16.074729Z INFO tokio-runtime-worker ThreadId(09) tauri_plugin_appload::commands: Bundle loaded successfully response=LoadResponse { success: true, window_label: "Hoppscotch-curr" } 2025-04-30T11:16:16.114689Z INFO main ThreadId(01) tauri_plugin_appload: Incoming URI request 2025-04-30T11:16:16.114709Z DEBUG main ThreadId(01) tauri_plugin_appload: Handling app URI scheme request. url=app://hoppscotch/ thread_id=ThreadId(1) 2025-04-30T11:16:16.114721Z INFO main ThreadId(01) tauri_plugin_appload: Got URI handler 2025-04-30T11:16:16.114732Z DEBUG main ThreadId(01) tauri_plugin_appload::uri::handler: Handling request host=hoppscotch path= 2025-04-30T11:16:16.114740Z DEBUG main ThreadId(01) tauri_plugin_appload::uri::handler: Fetching file content. host=hoppscotch path= resolved_path=index.html 2025-04-30T11:16:16.114752Z INFO main ThreadId(01) tauri_plugin_appload::cache::manager: Retrieving file bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html 2025-04-30T11:16:16.114759Z DEBUG main ThreadId(01) tauri_plugin_appload::cache::manager: Cache lookup attempt bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html thread_id=ThreadId(1) 2025-04-30T11:16:16.114766Z INFO main ThreadId(01) tauri_plugin_appload::cache::store: Retrieving file from cache. key="hoppscotch:index.html" 2025-04-30T11:16:16.114779Z DEBUG main ThreadId(01) tauri_plugin_appload::cache::store: Cache access attempt details key="hoppscotch:index.html" thread_id=ThreadId(1) hot_cache_len=0 disk_cache_len=0 2025-04-30T11:16:16.114795Z DEBUG main ThreadId(01) tauri_plugin_appload::cache::store: File not found in hot cache. Checking disk cache. key="hoppscotch:index.html" 2025-04-30T11:16:16.114806Z WARN main ThreadId(01) tauri_plugin_appload::cache::store: File not found in cache. key="hoppscotch:index.html" 2025-04-30T11:16:16.114814Z ERROR main ThreadId(01) tauri_plugin_appload::uri::handler: Failed to retrieve file content error=Cache error: Cache entry not found: hoppscotch:index.html host=hoppscotch path= 2025-04-30T11:16:17.201843Z INFO main ThreadId(01) tauri_plugin_appload: Incoming URI request 2025-04-30T11:16:17.201880Z DEBUG main ThreadId(01) tauri_plugin_appload: Handling app URI scheme request. url=app://hoppscotch/ thread_id=ThreadId(1) 2025-04-30T11:16:17.201911Z INFO main ThreadId(01) tauri_plugin_appload: Got URI handler 2025-04-30T11:16:17.201919Z DEBUG main ThreadId(01) tauri_plugin_appload::uri::handler: Handling request host=hoppscotch path= 2025-04-30T11:16:17.201927Z DEBUG main ThreadId(01) tauri_plugin_appload::uri::handler: Fetching file content. host=hoppscotch path= resolved_path=index.html 2025-04-30T11:16:17.201936Z INFO main ThreadId(01) tauri_plugin_appload::cache::manager: Retrieving file bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html 2025-04-30T11:16:17.201943Z DEBUG main ThreadId(01) tauri_plugin_appload::cache::manager: Cache lookup attempt bundle_name=hoppscotch file_path=index.html cache_key=hoppscotch:index.html thread_id=ThreadId(1) 2025-04-30T11:16:17.201951Z INFO main ThreadId(01) tauri_plugin_appload::cache::store: Retrieving file from cache. key="hoppscotch:index.html" 2025-04-30T11:16:17.201960Z DEBUG main ThreadId(01) tauri_plugin_appload::cache::store: Cache access attempt details key="hoppscotch:index.html" thread_id=ThreadId(1) hot_cache_len=0 disk_cache_len=0 2025-04-30T11:16:17.201970Z DEBUG main ThreadId(01) tauri_plugin_appload::cache::store: File not found in hot cache. Checking disk cache. key="hoppscotch:index.html" 2025-04-30T11:16:17.201976Z WARN main ThreadId(01) tauri_plugin_appload::cache::store: File not found in cache. key="hoppscotch:index.html" 2025-04-30T11:16:17.201983Z ERROR main ThreadId(01) tauri_plugin_appload::uri::handler: Failed to retrieve file content error=Cache error: Cache entry not found: hoppscotch:index.html host=hoppscotch path= ```

kerem commented

2026-03-16 21:58:39 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 30, 2025):

Thanks @Saintel for sharing your logs! This is very strange but I think I might know what's happening. The app is failing to initialize the vendored bundle, which explains why the cache is empty (hot_cache_len=0, disk_cache_len=0). Seems like the bundle files aren't being loaded into the cache during startup, usually located in Roaming\io.hoppscotch.desktop\bundles.

While I don't know the exact environment restrictions that might be causing this issue, my educated guess would be that the app starts and tries to initialize the vendored bundle, this initialization then fails because the cache remains empty (this can happen and there are fallbacks for it), but when the app tries to load hoppscotch:index.html, even that fails with "Cache entry not found" (this means the fallback failed as well)

The cache files are (should be) located in AppData\Roaming\io.hoppscotch.desktop\ and the fact that logs are working but the cache isn't suggests there might be permission issues with the Roaming directory. Your user account might not have full access to Roaming?

A few things you can try,

Clearing AppData directory in Roaming if it exists, and
if it doesn't then perhaps running as administrator might grant enough permissions for the app to build it, or
maybe there are some folder redirection on it? Some corporate environments redirect AppData\Roaming to network locations, which is known to cause issues.

@CuriousCorrelation commented on GitHub (Apr 30, 2025): Thanks @Saintel for sharing your logs! This is very strange but I think I might know what's happening. The app is failing to initialize the vendored bundle, which explains why the cache is empty (`hot_cache_len=0`, `disk_cache_len=0`). Seems like the bundle files aren't being loaded into the cache during startup, usually located in `Roaming\io.hoppscotch.desktop\bundles`. While I don't know the exact environment restrictions that might be causing this issue, my educated guess would be that the app starts and tries to initialize the vendored bundle, this initialization then fails because the cache remains empty (this can happen and there are fallbacks for it), but when the app tries to load `hoppscotch:index.html`, even that fails with "Cache entry not found" (this means the fallback failed as well) The cache files are (should be) located in `AppData\Roaming\io.hoppscotch.desktop\` and the fact that logs are working but the cache isn't suggests there might be permission issues with the Roaming directory. Your user account might not have full access to `Roaming`? A few things you can try, 1. Clearing `AppData` directory in `Roaming` if it exists, and 2. if it doesn't then perhaps running as administrator might grant enough permissions for the app to build it, or 3. maybe there are some folder redirection on it? Some corporate environments redirect `AppData\Roaming` to network locations, which is known to cause issues.

kerem commented

2026-03-16 21:58:44 +03:00

Author

Owner

@Saintel commented on GitHub (Apr 30, 2025):

Hi @CuriousCorrelation

I think, you are mention another folder AppData\Roaming\io.hoppscotch.desktop\? All Folders in c:\Users\my_user\AppData\Roaming\io.hoppscotch.desktop\ are realy empty, including bundles, i clean this folder and relaunch app with/without Admin permissions, and the issue is still here. Folder structure was created, but folders are empty.
I tried this several times before, and this time there is no results :(
I don't have redirect too(

@Saintel commented on GitHub (Apr 30, 2025): Hi @CuriousCorrelation 1. I think, you are mention another folder `AppData\Roaming\io.hoppscotch.desktop\`? All Folders in `c:\Users\my_user\AppData\Roaming\io.hoppscotch.desktop\` are realy empty, including `bundles`, i clean this folder and relaunch app with/without Admin permissions, and the issue is still here. Folder structure was created, but folders are empty. 2. I tried this several times before, and this time there is no results :( 3. I don't have redirect too(

kerem commented

2026-03-16 21:58:49 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 30, 2025):

Hi @Saintel, I think you figured out the issue!

See this (on a fresh install of Windows)

as you can see the directory contains information and files required by the app to function, which on your machine is empty. That being empty on you machine is likely a permissions or storage space issue (initial install may require large amount of storage for extractions, it won't use all the space after install). In either cases, the app cannot log any more information since it won't have the ability to introspect.

So essentially it's either a permissions issue or a storage space issue. One thing you can try is deleting io.hoppscotch.desktop entirely to signal the app to try recreating the directory structure. If it's still empty after that, likely a storage issue.

I looked up documentations for Windows and it seems one can check permissions using PowerShell:

Get-Acl "$env:APPDATA\io.hoppscotch.desktop" | Format-List
Get-ItemProperty "$env:APPDATA\io.hoppscotch.desktop" | Select-Object Attributes

Also if you have Process Monitor (from SysInternals), you could try to capture file system operations when launching the app to see exactly where it's failing.

In the meantime, I'm also looking into reproducing the environment to figure out what's exactly the root cause.

Quick edit to share the tests so far - I was able to reproduce albeit inconsistently, although it looks like there's a high likelihood that this is related to low storage capacity where some OS policies are preventing the app from creating and storing the application bundles.

@CuriousCorrelation commented on GitHub (Apr 30, 2025): Hi @Saintel, I think you figured out the issue! See this (on a fresh install of Windows) ![Image](https://github.com/user-attachments/assets/be41e9ed-bc76-475f-b2de-e9cf89f3fc99) as you can see the directory contains information and files required by the app to function, which on your machine is empty. That being empty on you machine is likely a permissions or storage space issue (initial install may require large amount of storage for extractions, it won't use all the space after install). In either cases, the app cannot log any more information since it won't have the ability to introspect. So essentially it's either a permissions issue or a storage space issue. One thing you can try is deleting `io.hoppscotch.desktop` entirely to signal the app to try recreating the directory structure. If it's still empty after that, likely a storage issue. I looked up documentations for Windows and it seems one can check permissions using PowerShell: ```powershell Get-Acl "$env:APPDATA\io.hoppscotch.desktop" | Format-List Get-ItemProperty "$env:APPDATA\io.hoppscotch.desktop" | Select-Object Attributes ``` Also if you have Process Monitor (from SysInternals), you could try to capture file system operations when launching the app to see exactly where it's failing. In the meantime, I'm also looking into reproducing the environment to figure out what's exactly the root cause. --- Quick edit to share the tests so far - I was able to reproduce albeit inconsistently, although it looks like there's a high likelihood that this is related to **low storage capacity** where some OS policies are preventing the app from creating and storing the application bundles.

kerem commented

2026-03-16 21:58:54 +03:00

Author

Owner

@surdaft commented on GitHub (May 23, 2025):

Apologies for jumping in on the thread.

I encountered this error and came across the thread; checking the logs it shows "Bundle loaded successfully" however, as you mentioned above, it should be within the AppData Roaming dir under Bundles, but that was empty. So Bundles were not loaded successfully. I then saw your message about disk space and only had like 11GB remaining, so freeing up space fixed the issue. Potentially warning about the disk space would be handy too.

TLDR; I needed to have more than 11GB remaining disk to fix the issue

@surdaft commented on GitHub (May 23, 2025): Apologies for jumping in on the thread. I encountered this error and came across the thread; checking the logs it shows "Bundle loaded successfully" however, as you mentioned above, it should be within the AppData Roaming dir under Bundles, but that was empty. So Bundles were not loaded successfully. I then saw your message about disk space and only had like 11GB remaining, so freeing up space fixed the issue. Potentially warning about the disk space would be handy too. TLDR; I needed to have more than 11GB remaining disk to fix the issue

kerem commented

2026-03-16 21:58:59 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (May 23, 2025):

@surdaft No worries at all - I actually appreciate you sharing your experience! This helps confirm diagnosis.

You're right that this is disk-space related, though the app itself only needs around 20MB or a bit more depending on how many self-hosted instances are saved.

The actual issue was quite complex and required multiple patches (see the linked PR/commit for more details on the latest) but this should be resolved fully in the upcoming release v25.5.0.

@CuriousCorrelation commented on GitHub (May 23, 2025): @surdaft No worries at all - I actually appreciate you sharing your experience! This helps confirm diagnosis. You're right that this is disk-space related, though the app itself only needs around 20MB or a bit more depending on how many self-hosted instances are saved. The actual issue was quite complex and required multiple patches (see the linked PR/commit for more details on the latest) but this should be resolved fully in the upcoming release `v25.5.0`.

kerem commented

2026-03-16 21:59:04 +03:00

Author

Owner

@Prikalel commented on GitHub (May 26, 2025):

so when v25.5.0 will be released?

btw do we have any temporary workarounds for that?

@Prikalel commented on GitHub (May 26, 2025): so when v25.5.0 will be released? btw do we have any temporary workarounds for that?

kerem commented

2026-03-16 21:59:09 +03:00

Author

Owner

@bad-maths commented on GitHub (May 27, 2025):

I'm having the same issue here. 🙋‍♂️
Windows 10 Pro 22H2 build 19045.2846
with only 4GB free on the C drive, so I think it might be something related to disk space.

@bad-maths commented on GitHub (May 27, 2025): I'm having the same issue here. 🙋‍♂️ Windows 10 Pro 22H2 build 19045.2846 with only 4GB free on the C drive, so I think it might be something related to disk space.

kerem commented

2026-03-16 21:59:14 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (May 28, 2025):

Hey @Prikalel and @bad-maths the latest release v25.5.0-0 is now available with an initial attempt at fully fixing this disk space/bundle loading issue!

The fix addresses the core problem that was identified where the app was failing to properly extract and cache bundles in the AppData directory when disk space was limited or when Windows was handling path resolution in unexpected ways, more of the latter.

For those who've been affected by this 404 error, please update to v25.5.0-0 (download section on official site) and let me know if this resolves the issue for you.

Given that this problem appears to be highly dependent on specific Windows configurations, system policies, and available disk space, I'm cautiously optimistic but would really appreciate your feedback.

@CuriousCorrelation commented on GitHub (May 28, 2025): Hey @Prikalel and @bad-maths the latest release `v25.5.0-0` is now available with an initial attempt at fully fixing this disk space/bundle loading issue! The fix addresses the core problem that was identified where the app was failing to properly extract and cache bundles in the AppData directory when disk space was limited or when Windows was handling path resolution in unexpected ways, more of the latter. For those who've been affected by this 404 error, please update to `v25.5.0-0` ([download section on official site](https://hoppscotch.com/download)) and let me know if this resolves the issue for you. Given that this problem appears to be highly dependent on specific Windows configurations, system policies, and available disk space, I'm cautiously optimistic but would really appreciate your feedback.

kerem commented

2026-03-16 21:59:19 +03:00

Author

Owner

@sLIDe5 commented on GitHub (May 28, 2025):

Update from within Hoppscotch application with ~3GB left on drive didn't work (download stuck on about 10%) but fresh install is now working (even with less space free) and no more 404 error.

@sLIDe5 commented on GitHub (May 28, 2025): Update from within Hoppscotch application with ~3GB left on drive didn't work (download stuck on about 10%) but fresh install is now working (even with less space free) and no more 404 error.

kerem commented

2026-03-16 21:59:25 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (May 28, 2025):

but fresh install is now working (even with less space free) and no more 404 error.

Awesome! Thanks for the confirmation @sLIDe5

Update from within Hoppscotch application with ~3GB left on drive didn't work (download stuck on about 10%)

Ah yes, this tends to happen when the artifact distribution hasn't fully cached across all geo-locations, this is unrelated to disk space, more to do with update distribution, so this should be resolved once artifacts are fully populated, takes a few hours depending on GitHub traffic.

@CuriousCorrelation commented on GitHub (May 28, 2025): > but fresh install is now working (even with less space free) and no more 404 error. Awesome! Thanks for the confirmation @sLIDe5 > Update from within Hoppscotch application with ~3GB left on drive didn't work (download stuck on about 10%) Ah yes, this tends to happen when the artifact distribution hasn't fully cached across all geo-locations, this is unrelated to disk space, more to do with update distribution, so this should be resolved once artifacts are fully populated, takes a few hours depending on GitHub traffic.

kerem commented

2026-03-16 21:59:30 +03:00

Author

Owner

@AndreKR commented on GitHub (May 28, 2025):

Automatic update worked for me. 10 GB of 1.8 TB free.

@AndreKR commented on GitHub (May 28, 2025): Automatic update worked for me. 10 GB of 1.8 TB free.

kerem commented

2026-03-16 21:59:35 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Jun 6, 2025):

I have received several confirmation from different channels that the fix https://github.com/hoppscotch/hoppscotch/pull/5049 has been confirmed working. Thanks to everyone who provided debug info and feedback!

For anyone still experiencing this issue, please update to the latest version at https://hoppscotch.com/download. If updating from within the app fails, try a fresh download and install, all user data will be preserved ✅

If you continue to experience similar errors after updating to the latest version, feel free to reply here with your Windows version/build, available disk space, and the log file contents. The desktop app has persistent logs that can be found at C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log. This will help diagnose any remaining edge cases without fragmenting the discussion across multiple issues.

Thanks for helping tracked down this rather tricky issue! 🎉

@CuriousCorrelation commented on GitHub (Jun 6, 2025): I have received several confirmation from different channels that the fix https://github.com/hoppscotch/hoppscotch/pull/5049 has been confirmed working. Thanks to everyone who provided debug info and feedback! For anyone still experiencing this issue, please update to the latest version at https://hoppscotch.com/download. If updating from within the app fails, try a fresh download and install, all user data will be preserved ✅ If you continue to experience similar errors after updating to the latest version, feel free to reply here with your Windows version/build, available disk space, and the log file contents. The desktop app has persistent logs that can be found at `C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log`. This will help diagnose any remaining edge cases without fragmenting the discussion across multiple issues. Thanks for helping tracked down this rather tricky issue! 🎉

Rows
Columns

[GH-ISSUE #4859] [bug]: Root page fails to load with status code 404 in Desktop App on Windows #1829

Is there an existing issue for this?

Current behavior

Steps to reproduce

Environment

Version

[GH-ISSUE #4859] [bug]: Root page fails to load with status code `404` in Desktop App on Windows #1829