starred/hoppscotch

Fork 0

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

[GH-ISSUE #3326] [bug]: Error: test: does not get device identifier Login.vue:266 #1105

New issue

Closed

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

kerem commented

2026-03-16 18:35:49 +03:00

Owner

Originally created by @Overbuiltx on GitHub (Sep 7, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3326

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I run hoppscotch (aio + postgres) via prebuilt docker images.

The container stack is restricted with an outbound corporate firewall and is accessable by a httpd reverse proxy.
I did modify the aio Caddyfile, so one port exposes all the services - like so:

:80 {
        handle_path /api/* {
                reverse_proxy localhost:3170
        }

        redir /admin /admin/
        handle /admin/* {
                try_files {path} /
                root * /site/sh-admin
                file_server
        }

        handle {
                try_files {path} /
                root * /site/selfhost-web
                file_server
        }

        log {
                output stdout
                level ERROR
        }
}

(I also tried the built in Caddyfile, same result)

Hoppscotch loads without errors, except for /admin, which gives me a 404.

If I login via Email I get the following error in the web console:

VITE_ADMIN_URL=https://hoppscotch.<company>/admin
VITE_ALLOWED_AUTH_PROVIDERS=EMAIL
# Mailer config
MAILER_SMTP_URL=smtps://hoppscotch@<company>:<pass>@smtp.<company>
MAILER_ADDRESS_FROM='"Hoppscotch" <hoppscotch@<company>>'

version: "3.7"

services:
  hoppscotch-aio:
    build: ./app
    env_file:
      - ./.env
    depends_on:
      hoppscotch-db:
        condition: service_healthy
    ports:
      - "80:80"

  hoppscotch-db:
    image: postgres:15-alpine
    user: postgres
    environment:
      # The default user defined by the docker image
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: pass
      POSTGRES_DB: hoppscotch
    volumes:
      - ./db:/var/lib/postgresql/data
    healthcheck:
      test:
        [
          "CMD-SHELL",
          "sh -c 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'"
        ]
      interval: 5s
      timeout: 5s
      retries: 10

networks:
  default:
    name: hoppscotch

FROM hoppscotch/hoppscotch:2023.8.0

COPY Caddyfile /etc/caddy/Caddyfile

ENTRYPOINT [ "tini", "--" ]
HEALTHCHECK --interval=2s CMD /bin/sh ./healthcheck.sh
CMD ["node" "/usr/src/app/aio_run.mjs"]
EXPOSE 80

Steps to reproduce

docker-compose build
docker-compose up -d
try to login via email on website
Login.vue error

Environment

Production

Version

Self-hosted

Originally created by @Overbuiltx on GitHub (Sep 7, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3326 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I run hoppscotch (aio + postgres) via prebuilt docker images. The container stack is restricted with an outbound corporate firewall and is accessable by a httpd reverse proxy. I did modify the aio Caddyfile, so one port exposes all the services - like so: ``` :80 { handle_path /api/* { reverse_proxy localhost:3170 } redir /admin /admin/ handle /admin/* { try_files {path} / root * /site/sh-admin file_server } handle { try_files {path} / root * /site/selfhost-web file_server } log { output stdout level ERROR } } ``` (I also tried the built in Caddyfile, same result) Hoppscotch loads without errors, except for /admin, which gives me a 404. If I login via Email I get the following error in the web console: ![image](https://github.com/hoppscotch/hoppscotch/assets/144319516/4fa81f28-129f-4d07-a90d-22053670fcf9) ``` VITE_ADMIN_URL=https://hoppscotch.<company>/admin VITE_ALLOWED_AUTH_PROVIDERS=EMAIL # Mailer config MAILER_SMTP_URL=smtps://hoppscotch@<company>:<pass>@smtp.<company> MAILER_ADDRESS_FROM='"Hoppscotch" <hoppscotch@<company>>' ``` ``` version: "3.7" services: hoppscotch-aio: build: ./app env_file: - ./.env depends_on: hoppscotch-db: condition: service_healthy ports: - "80:80" hoppscotch-db: image: postgres:15-alpine user: postgres environment: # The default user defined by the docker image POSTGRES_USER: postgres POSTGRES_PASSWORD: pass POSTGRES_DB: hoppscotch volumes: - ./db:/var/lib/postgresql/data healthcheck: test: [ "CMD-SHELL", "sh -c 'pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}'" ] interval: 5s timeout: 5s retries: 10 networks: default: name: hoppscotch ``` ``` FROM hoppscotch/hoppscotch:2023.8.0 COPY Caddyfile /etc/caddy/Caddyfile ENTRYPOINT [ "tini", "--" ] HEALTHCHECK --interval=2s CMD /bin/sh ./healthcheck.sh CMD ["node" "/usr/src/app/aio_run.mjs"] EXPOSE 80 ``` ### Steps to reproduce 1. docker-compose build 2. docker-compose up -d 3. try to login via email on website 4. Login.vue error ### Environment Production ### Version Self-hosted

kerem

2026-03-16 18:35:49 +03:00

closed this issue
added the
bug

need testing

self-host
labels

kerem commented

2026-03-16 18:36:05 +03:00

Author

Owner

@lin-moeller commented on GitHub (Sep 7, 2023):

https://github.com/hoppscotch/hoppscotch/issues/3257
I don't know if this is exactly the same case here, but maybe if you read through and subscribe to this issue, you could get a solution that could be helpful for this bug as well.

@lin-moeller commented on GitHub (Sep 7, 2023): https://github.com/hoppscotch/hoppscotch/issues/3257 I don't know if this is exactly the same case here, but maybe if you read through and subscribe to this issue, you could get a solution that could be helpful for this bug as well.

kerem commented

2026-03-16 18:36:11 +03:00

Author

Owner

@a-camacho commented on GitHub (Sep 10, 2023):

Same problem for me.

@a-camacho commented on GitHub (Sep 10, 2023): Same problem for me.

kerem commented

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

Author

Owner

@LucaLHIND commented on GitHub (Sep 14, 2023):

Same problem for me.

@LucaLHIND commented on GitHub (Sep 14, 2023): Same problem for me.

kerem commented

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

Author

Owner

@Francesko90 commented on GitHub (Oct 26, 2023):

I had same problem but I solved adding following env variable

VITE_BACKEND_API_URL=http://localhost:3170/v1

@Francesko90 commented on GitHub (Oct 26, 2023): I had same problem but I solved adding following env variable VITE_BACKEND_API_URL=http://localhost:3170/v1

kerem commented

2026-03-16 18:36:26 +03:00

Author

Owner

@balub commented on GitHub (Jan 11, 2024):

Subpath Access to services added in release 2023.12.0.

@balub commented on GitHub (Jan 11, 2024): Subpath Access to services added in release `2023.12.0`.