starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3342] [bug]: Have problems for a self hosted installation #1116

New issue

Closed

opened 2026-03-16 18:39:16 +03:00 by kerem · 5 comments

kerem commented

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

Owner

Originally created by @giosueDelgado on GitHub (Sep 12, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3342

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I create a docker compose where I want to run my seld hosted installation.

Here the docker-compose:


hoppscotch:
    image: hoppscotch/hoppscotch:2023.8.0
    environment:
      - DATABASE_URL=postgresql://${LINKDB}
      - JWT_SECRET=
      - TOKEN_SALT_COMPLEXITY=10
      - MAGIC_LINK_TOKEN_VALIDITY=3
      - REFRESH_TOKEN_VALIDITY=604800000
      - ACCESS_TOKEN_VALIDITY=86400000
      - SESSION_SECRET=
      - REDIRECT_URL=https://domain.com/gui-api
      - WHITELISTED_ORIGINS=https://domain.com,https://*.domain.com,https://domain.com
      - VITE_ALLOWED_AUTH_PROVIDERS=EMAIL
      - MAILER_SMTP_URL=smtps://${credentialemail}
      - MAILER_ADDRESS_FROM='"${sendeemail}'
      - RATE_LIMIT_TTL=60
      - RATE_LIMIT_MAX=100
      - VITE_BASE_URL=https://domain.com/gui-api
      - VITE_SHORTCODE_BASE_URL=https://domain.com/gui-api
      - VITE_ADMIN_URL=https://domain.com/gui-api-admin
      - VITE_BACKEND_GQL_URL=https://domain.com/gui-api-backend/graphql
      - VITE_BACKEND_WS_URL=wss://domain.com/gui-api-backend/graphql
      - VITE_BACKEND_API_URL=https://domain.com/gui-api-backend/v1

And I have a nginx that redirect the traffic based on path location to the port of this container "/gui-api" to 3000, "/gui-api-admin" to 3100 and "/gui-api-backend" to 3170

But I have some issue on base path for the GUI application (to make work I have to replace the link in the html and in the css to add the path).

Is it possible to have a full guide documentation to have this solution in the self hosted with a working example that can work also on path managed and not on port managed solution?
Because following the documentation not work.
Thanks

Steps to reproduce

See the description

Environment

Production

Version

Self-hosted

Originally created by @giosueDelgado on GitHub (Sep 12, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3342 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I create a docker compose where I want to run my seld hosted installation. Here the docker-compose: ``` hoppscotch: image: hoppscotch/hoppscotch:2023.8.0 environment: - DATABASE_URL=postgresql://${LINKDB} - JWT_SECRET= - TOKEN_SALT_COMPLEXITY=10 - MAGIC_LINK_TOKEN_VALIDITY=3 - REFRESH_TOKEN_VALIDITY=604800000 - ACCESS_TOKEN_VALIDITY=86400000 - SESSION_SECRET= - REDIRECT_URL=https://domain.com/gui-api - WHITELISTED_ORIGINS=https://domain.com,https://*.domain.com,https://domain.com - VITE_ALLOWED_AUTH_PROVIDERS=EMAIL - MAILER_SMTP_URL=smtps://${credentialemail} - MAILER_ADDRESS_FROM='"${sendeemail}' - RATE_LIMIT_TTL=60 - RATE_LIMIT_MAX=100 - VITE_BASE_URL=https://domain.com/gui-api - VITE_SHORTCODE_BASE_URL=https://domain.com/gui-api - VITE_ADMIN_URL=https://domain.com/gui-api-admin - VITE_BACKEND_GQL_URL=https://domain.com/gui-api-backend/graphql - VITE_BACKEND_WS_URL=wss://domain.com/gui-api-backend/graphql - VITE_BACKEND_API_URL=https://domain.com/gui-api-backend/v1 ``` And I have a nginx that redirect the traffic based on path location to the port of this container "/gui-api" to 3000, "/gui-api-admin" to 3100 and "/gui-api-backend" to 3170 But I have some issue on base path for the GUI application (to make work I have to replace the link in the html and in the css to add the path). Is it possible to have a full guide documentation to have this solution in the self hosted with a working example that can work also on path managed and not on port managed solution? Because following the documentation not work. Thanks ### Steps to reproduce See the description ### Environment Production ### Version Self-hosted

kerem

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

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

2026-03-16 18:39:32 +03:00

Author

Owner

@Zer0S2m commented on GitHub (Sep 22, 2023):

Hello @giosueDelgado!
I have the same problem. The simple solution that I was able to do was to create two subdomains, the first for the application itself, the second for the admin area.

@Zer0S2m commented on GitHub (Sep 22, 2023): Hello @giosueDelgado! I have the same problem. The simple solution that I was able to do was to create two subdomains, the first for the application itself, the second for the admin area.

kerem commented

2026-03-16 18:39:37 +03:00

Author

Owner

@giosueDelgado commented on GitHub (Sep 24, 2023):

Hi @Zer0S2m thank you for your suggestion, yes I think it is a good workaround, I think we can use this issue also to give a configuration option for those who cannot manage many domains but only one and work on subpath..

@giosueDelgado commented on GitHub (Sep 24, 2023): Hi @Zer0S2m thank you for your suggestion, yes I think it is a good workaround, I think we can use this issue also to give a configuration option for those who cannot manage many domains but only one and work on subpath..

kerem commented

2026-03-16 18:39:43 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Nov 22, 2023):

Hi, we're adding the ability to access the services under subpaths. The changes have been merged in #3449 and will be going with the 2023.12.0 release scheduled for December.

@jamesgeorge007 commented on GitHub (Nov 22, 2023): Hi, we're adding the ability to access the services under subpaths. The changes have been merged in #3449 and will be going with the `2023.12.0` release scheduled for December.

kerem commented

2026-03-16 18:39:48 +03:00

Author

Owner

@giosueDelgado commented on GitHub (Nov 22, 2023):

Cool! Thanks! @jamesgeorge007

@giosueDelgado commented on GitHub (Nov 22, 2023): Cool! Thanks! @jamesgeorge007

kerem commented

2026-03-16 18:39:53 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 20, 2023):

Thanks for your patience and valuable feedback. This feature has been implemented in the latest release.

Closing this ticket as this feature is now available in the recent version. Feel free to reach out if you encounter any further concerns.

@liyasthomas commented on GitHub (Dec 20, 2023): Thanks for your patience and valuable feedback. This feature has been implemented in the latest release. Closing this ticket as this feature is now available in the recent version. Feel free to reach out if you encounter any further concerns.