[GH-ISSUE #4476] [bug]: Fails to start in isolated environment (without internet access) #1637

New issue

Closed

opened 2026-03-16 21:12:14 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @Tob1as on GitHub (Oct 25, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4476

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I start hoppscotch (AIO, version: 2024.9.3) in an isolated Kubernetes environment (without internet access), I get the following logs:

 WARN  GET https://registry.npmjs.org/prisma error (ENOTFOUND). Will retry in 10 seconds. 2 retries left.
 WARN  GET https://registry.npmjs.org/prisma error (ENOTFOUND). Will retry in 1 minute. 1 retries left.
/root/.cache/pnpm/dlx/b4kwuke4fcm2ppufregi7l7yfi/192c39c0c85-1:
 ERR_PNPM_META_FETCH_FAIL  GET https://registry.npmjs.org/prisma: request to https://registry.npmjs.org/prisma failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org

This error happened while installing a direct dependency of /root/.cache/pnpm/dlx/b4kwuke4fcm2ppufregi7l7yfi/192c39c0c85-1

Issues:

The container tries to access the internet at startup (and possibly reload things?). I consider external dependencies to be fundamentally problematic in this context.
This internet dependency causes the container to enter a restart loop and fails to start correctly.

Suggestion:
It would be beneficial if the application could start in isolated environments (e.g., with restricted internet access) without relying on external dependencies.

Does anyone have an idea for a (temporary) solution?

Steps to reproduce

start hoppscotch in environment without internet access
run pnpx prisma migrate deploy
see logs

Environment

Production

Version

Self-hosted

Originally created by @Tob1as on GitHub (Oct 25, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4476 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I start hoppscotch (AIO, version: 2024.9.3) in an isolated Kubernetes environment (without internet access), I get the following logs: ```log WARN GET https://registry.npmjs.org/prisma error (ENOTFOUND). Will retry in 10 seconds. 2 retries left. WARN GET https://registry.npmjs.org/prisma error (ENOTFOUND). Will retry in 1 minute. 1 retries left. /root/.cache/pnpm/dlx/b4kwuke4fcm2ppufregi7l7yfi/192c39c0c85-1: ERR_PNPM_META_FETCH_FAIL GET https://registry.npmjs.org/prisma: request to https://registry.npmjs.org/prisma failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org This error happened while installing a direct dependency of /root/.cache/pnpm/dlx/b4kwuke4fcm2ppufregi7l7yfi/192c39c0c85-1 ``` Issues: - The container tries to access the internet at startup (and possibly reload things?). I consider external dependencies to be fundamentally problematic in this context. - **This internet dependency causes the container to enter a restart loop and fails to start correctly.** Suggestion: It would be beneficial if the application could start in isolated environments (e.g., with restricted internet access) without relying on external dependencies. Does anyone have an idea for a (temporary) solution? ### Steps to reproduce 1. start hoppscotch in environment without internet access 2. run `pnpx prisma migrate deploy` 3. see logs ### Environment Production ### Version Self-hosted

kerem

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

closed this issue
added the
bug

need testing
labels

kerem commented

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

Author

Owner

@balub commented on GitHub (Dec 7, 2024):

Hey you can run the migration using pnpm prisma migrate deploy and it will still work.

@balub commented on GitHub (Dec 7, 2024): Hey you can run the migration using `pnpm prisma migrate deploy` and it will still work.