Hi All, for the longest time my docker compose has...
# general
p
Hi All, for the longest time my docker compose has had use the ory cli container. I set the API key as an env variable and ran the tunnel, but now it’s saying, “A browser should have opened for you to complete your login to Ory Network.” Why would it be saying this now? On my local terminal, I can tunnel just fine by setting the api key through the environment variable, it seems to just be the docker container. Anyone have any similar issues or have any pointers?
Copy code
ory:
    image: oryd/ory
    ports:
      - 4000:4000
    secrets:
      - ory_tunnel_key
    entrypoint: ''
    command: >
      sh -c "
        export ORY_API_KEY=$(cat /run/secrets/ory_tunnel_key) &&
        ory tunnel --project slug-here --allowed-cors-origins <https://localhost:3000> <https://localhost:3001>"
s
There has been a major release. You should 1. always pin your version 2. take a look at the migration guide https://www.ory.sh/docs/guides/cli/cli-migration-v1
p
Thanks!
Hey @steep-lamp-91158 even after setting the api keys in the new way specified in the docs, It’s saying:
Copy code
unable to list projects: {"error":{"code":401,"status":"Unauthorized","request":"27001e0a-3ef8-9c82-b28c-4ad42c81a8f5","message":"Access credentials are invalid"}}
: 401 Unauthorized
This is the command that’s doing that:
Copy code
ory tunnel <http://localhost:4000> --dev --project my-slug
I’ve tried setting the api keys as both the ORY_WORKSPACE_API_KEY and ORY_PROJECT_API_KEY, but both produce the same result. I’ve looked through the docs but haven’t found any solution
s
seems like you are not using the correct keys? is the project part of a workspaces? make sure to use the workspace key of the one where the project is, and also to include the
--workspace <id>
flag
p
I’ve created the keys via project settings > API keys. The fomat of the key is ory_pat instead of ory_pt like the docs say, but I was hoping that didn’t make a difference
Also the docs indicated that it would work for legacy projects without a workspace, but maybe that was incorrect
s
the
ory_pt
is probably a typo in the docs
when you don't have a workspace, it currently only works with the interactive login (working on a fix though)
but you can move your project to a free workspace under project settings
p
If one of my projects is under the production subscription, and then another is a dev environment under the free, is that going to mess anything if I move both projects to a new workspace?
Looks like i need to reach out to support it says, I’ll get that taken care of. Thanks
s
for now you can just pin your version to v0.3
1