Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    kamaljaiswal
    @kamaljaiswal
    Ya u guys rocks !!
    Mine store front is failing primaryShop query result was null
    primaryShop query result was null
    InternalOAuthError: Failed to obtain access token
    at OAuth2Strategy._createOAuthError (/usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:379:17)
    at /usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:166:45
    at /usr/local/src/app/node_modules/oauth/lib/oauth2.js:191:18
    at ClientRequest.<anonymous> (/usr/local/src/app/node_modules/oauth/lib/oauth2.js:162:5)
    at ClientRequest.emit (events.js:198:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:198:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    Loan Laux
    @loan-laux
    Have you created a shop yet, @kamaljaiswal?
    kamaljaiswal
    @kamaljaiswal
    yes using using admin
    Loan Laux
    @loan-laux
    Can you check your API Docker logs?
    kamaljaiswal
    @kamaljaiswal
    primaryShop query result was null
    primaryShop query result was null
    InternalOAuthError: Failed to obtain access token
    at OAuth2Strategy._createOAuthError (/usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:379:17)
    at /usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:166:45
    at /usr/local/src/app/node_modules/oauth/lib/oauth2.js:191:18
    at ClientRequest.<anonymous> (/usr/local/src/app/node_modules/oauth/lib/oauth2.js:162:5)
    at ClientRequest.emit (events.js:198:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:198:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    InternalOAuthError: Failed to obtain access token
    at OAuth2Strategy._createOAuthError (/usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:379:17)
    at /usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:166:45
    at /usr/local/src/app/node_modules/oauth/lib/oauth2.js:191:18
    at ClientRequest.<anonymous> (/usr/local/src/app/node_modules/oauth/lib/oauth2.js:162:5)
    at ClientRequest.emit (events.js:198:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:198:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    InternalOAuthError: Failed to obtain access token
    at OAuth2Strategy._createOAuthError (/usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:379:17)
    at /usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:166:45
    at /usr/local/src/app/node_modules/oauth/lib/oauth2.js:191:18
    at ClientRequest.<anonymous> (/usr/local/src/app/node_modules/oauth/lib/oauth2.js:162:5)
    at ClientRequest.emit (events.js:198:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:198:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    InternalOAuthError: Failed to obtain access token
    at OAuth2Strategy._createOAuthError (/usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:379:17)
    at /usr/local/src/app/node_modules/passport-oauth2/lib/strategy.js:166:45
    at /usr/local/src/app/node_modules/oauth/lib/oauth2.js:191:18
    at ClientRequest.<anonymous> (/usr/local/src/app/node_modules/oauth/lib/oauth2.js:162:5)
    at ClientRequest.emit (events.js:198:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:198:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    Loan Laux
    @loan-laux
    Isn’t this the logs of the storefront container?
    kamaljaiswal
    @kamaljaiswal
    yes this is for storefront
    kamaljaiswal
    @kamaljaiswal
    Make platform is give lots of errors TASK [Build the Reaction Platform] *
    fatal: [reaction.server]: FAILED! => {"changed": true, "cmd": ["make"], "delta": "0:00:49.224161", "end": "2020-07-17 04:56:34.802751", "msg": "non-zero return code", "rc": 2, "start": "2020-07-17 04:55:45.578590", "stderr": "Cloning into 'reaction-hydra'...\nNote: checking out 'v3.0.0'.\n\nYou are in 'detached HEAD' state. You can look around, make experimental\nchanges and commit them, and you can discard any commits you make in this\nstate without impacting any branches by performing another checkout.\n\nIf you want to create a new branch to retain commits you create, you may\ndo so (now or later) by using -b with the checkout command again. Example:\n\n git checkout -b <new-branch-name>\n\nHEAD is now at eee6dd1 Merge pull request #48 from reactioncommerce/release-v3.0.0\nError response from daemon: network with name reaction.localhost already exists\npostgres uses an image, skipping\nhydra-migrate uses an image, skipping\nhydra uses an image, skipping\nPulling postgres ... \r\nPulling hydra-migrate ... \r\nPulling hydra ... \r\n\u001b[3A\u001b[2K\rPulling postgres ... pulling from library/postgres\r\u001b[3B\u001b[2A\u001b[2K\rPulling hydra-migrate ... pulling from oryd/hydra\r\u001b[2B\u001b[2A\u001b[2K\rPulling hydra-migrate ... digest: sha256:7f5cfc37198c68dde7...\r\u001b[2B\u001b[2A\u001b[2K\rPulling hydra-migrate ... status: image is up to date for o...\r\u001b[2B\u001b[2A\u001b[2K\rPulling hydra-migrate ... \u001b[32mdone\u001b[0m\r\u001b[2B\u001b[1A\u001b[2K\rPulling hydra ... pulling from oryd/hydra\r\u001b[1B\u001b[1A\u001b[2K\rPulling hydra ... digest: sha256:7f5cfc37198c68dde7...\r\u001b[1B\u001b[1A\u001b[2K\rPulling hydra ... status: image is up to date for o...\r\u001b[1B\u001b[1A\u001b[2K\rPulling hydra ... \u001b[32mdone\u001b[0m\r\u001b[1B\u001b[3A\u001b[2K\rPulling postgres ... digest: sha256:23c92d48934b254c00...\r\u001b[3B\u001b[3A\u001b[2K\rPulling postgres ... status: image is up to date for p...\r\u001b[3B\u001b[3A\u001b[2K\rPulling postgres ... \u001b[32mdone\u001b[0m\r\u001b[3BStarting reaction-hydra_postgres_1 ... \r\n\u001b[1A\u001b[2K\rStarting reaction-hydra_postgres_1 ... \u001b[32mdone\u001b[0m\r\u001b[1BStarting reaction-hydra_hydra-migrate_1 ... \r\n\u001b[1A\u001b[2K\rStarting reaction-hydra_hydra-migrate_1 ... \u001b[32mdone\u001b[0m\r\u001b[1BStarting reaction-hydra_hydra_1 ... \r\n\u001b[1A\u001b[2K\rStarting reaction-hydra_hydra_1 ... \u001b[32mdone\u001b[0m\r\u001b[1BCloning into 'reaction'...\nNote: checking out 'v3.8.0'.\n\nYou are in 'detached HEAD' state. You can look around, make experimental\nchanges and commit them, and you can discard any commits you make in this\nstate without impacting any branches by performing another checkout.\n\nIf you want to create a new branch to retain commits you create, you may\ndo so (now or later) by using -b with the checkout command again. Example:\n\n git checkout -b <new-branch-name>\n\nHEAD is now at a13ac6576 Merge pull request #6253 from reactioncommerce/release-next-v3.8.0\nmongo uses an image, skipping\napi uses an image, skipping\nPulling mongo ... \r\nPulling api ... \r\n\u001b[1A\u001b[2K\rPulling api ... pulling from reactioncommerce/rea...\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling fs layer\r\u001b[1B\u001b[1A\u001b[2K\rPulling api ... pulling f
    kamaljaiswal
    @kamaljaiswal
    tried hard reset the /home/reaction ..will update .
    any help ..as same ansible-playbook playbooks/reaction.yml -l reaction.server was working . And tried deleting /home/reaction completely
    kamaljaiswal
    @kamaljaiswal
    systemctl stop mongodb did the trick ...will confirm in case
    seday72
    @seday72
    hi everyone
    i am going to deploy reaction commerce platform on aws ec2
    I tried to configure .env but backend not working
    please help me how to config this
    Pulkit Garg
    @wittycodes
    @seday72 https://github.com/reactioncommerce/proxy-traefik
    refer the above git repo, it's for an automated & workable production deployment of reaction.
    seday72
    @seday72
    This message was deleted
    hi @wittycodes
    is that possible to deploy on aws too?
    Loan Laux
    @loan-laux
    Hey @seday72, we’ve got a tutorial for deploying on AWS ECS on https://university.outgrow.io
    ihalton
    @ihalton

    @ihalton
    Running command: meteor run --port 4080 --no-lint --no-release-check --raw-logs
    [[[[[ /usr/local/src/app ]]]]]

    => Started proxy.
    Killed
    Error: Command failed: REACTION_METEOR_APP_COMMAND_START_TIME=1597467210450 meteor run --port 4080 --no-lint --no-release-check --raw-logs
    at checkExecSyncError (child_process.js:630:11)
    at Object.execSync (child_process.js:666:15)
    at run (file:///usr/local/src/app/.reaction/scripts/run.mjs:21:18)
    at file:///usr/local/src/app/.reaction/scripts/run.mjs:29:1
    at ModuleJob.run (internal/modules/esm/module_job.js:110:37)
    at async Loader.import (internal/modules/esm/loader.js:164:24) {
    status: 137,
    signal: null,
    output: [ null, null, null ],
    pid: 39,
    stdout: null,
    stderr: null
    }

    Error: App failed to start
    hello, get crashed when running reaction_admin from code. why?

    balibebas
    @balibebas
    Hi folks. Has anyone looked at deploying with Rio? https://rio.io
    I'd like to take advantage of the canary deployments and GitOps. Rio is a MicroPaaS by Rancher and is designed to work well with k3s. I've done some initial research here for anyone interested who hasn't worked with Rio yet: https://habd.as/post/git-based-continuous-delivery-rio/
    ihalton
    @ihalton
    Hello, have anyone know what reason about the error? Thanks
    Running command: meteor run --port 4080 --no-lint --no-release-check --raw-logs
    [[[[[ /usr/local/src/app ]]]]]
    => Started proxy.
    Killed
    Error: Command failed: REACTION_METEOR_APP_COMMAND_START_TIME=1597467210450 meteor run --port 4080 --no-lint --no-release-check --raw-logs
    at checkExecSyncError (child_process.js:630:11)
    at Object.execSync (child_process.js:666:15)
    at run (file:///usr/local/src/app/.reaction/scripts/run.mjs:21:18)
    at file:///usr/local/src/app/.reaction/scripts/run.mjs:29:1
    at ModuleJob.run (internal/modules/esm/module_job.js:110:37)
    at async Loader.import (internal/modules/esm/loader.js:164:24) {
    status: 137,
    signal: null,
    output: [ null, null, null ],
    pid: 39,
    stdout: null,
    stderr: null
    }
    Error: App failed to start
    balibebas
    @balibebas
    @ihalton I see you asked the same question in the main Reaction channel just an hour before here. Could you please try waiting there for an answer instead of double-posting? My understanding is this channel is not intended for general debugging.
    ihalton
    @ihalton
    @balibebas I am sorry for any inconvenience, I will waiting answer in that channel.
    balibebas
    @balibebas
    thanks, bos. you may wish to try the forums too for visibility
    ihalton
    @ihalton
    @balibebas this maybe it is a bug. Nobody answer me in that channel. :)
    Ankur Pata
    @ankurpata
    image.png
    Hi @loan-laux
    The Reaction-Hydra repo says ' its 💥 Not safe for production.'
    What does this exactly mean? Do we need to use our custom authentication service instead of Hydra for production or we need to customize based on our needs ?
    balibebas
    @balibebas
    Food for thought... Coinbase: Why Kubernetes is not part of our stack https://blog.coinbase.com/container-technologies-at-coinbase-d4ae118dcb6c
    S Tunji Turner
    @stunjiturner
    Reaction + Vercel anybody?
    Loan Laux
    @loan-laux
    Yep. Works. I can confirm.
    Q_Q
    @mfaster
    Do anyone still works on Heroku?
    I'd like to take advantage of the canary deployments and GitOps. Rio is a MicroPaaS by Rancher and is designed to work well with k3s. I've done some initial research here for anyone interested who hasn't worked with Rio yet: https://habd.as/post/git-based-continuous-delivery-rio/
    Good one tho
    Q_Q
    @mfaster
    Thanks for sharing
    Karim Abuzaid
    @Vercryger
    Hey everyone! I've switched to kubernetes for both production and staging enviroments and currently working on setup SSL, which I've found it so hard btw. So far I've secured all services but within the admin the socket connection fails since I changed ws to wss. At first I thought some configurations were wrong on the backend but, storefront successfully connects to the web socket server. I'm not really sure what's going on, this is the error I get failed: Error during WebSocket handshake: Unexpected response code: 400. Any help would be much appreciated
    Also, identity server also get this error, so probably meteor related?
    Sebastian Franco
    @jhonsfran1165
    Yeah, It seems some configuration is missing. What API gateway are you using?
    Karim Abuzaid
    @Vercryger
    I'm using EKS and this started to happen when I configured ELB to make use of ssl certificates
    For the record I'm not using ingress controllers for such setup
    Sebastian Franco
    @jhonsfran1165
    Okay I can help with this but I need some details about your infra, I also need logs of your services. Did you configure a ingress? Could you share the yaml file? What I do in that situation is configure a node port directly to the service that I need to test and then test the connection. If everything goes well it means that the problems is in the ingress configuration. So you can check that part specifically.
    igor romanovsky
    @igorromanovsky_twitter
    Hey. Is there any guide for deploying to GCP
    Karim Abuzaid
    @Vercryger
    @jhonsfran1165 Thank you. This is the current yaml for our reaction admin, the rest of services are just more of the same
    apiVersion: v1
    kind: Service
    metadata:
      labels:
        reaction: admin
      name: reaction-admin
      annotations:
        service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
        service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:us-east-2:<accountno>:certificate/<cid>
        service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
        service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
    spec:
      ports:
      - name: http
        port: 80
        targetPort: 4080
      - name: https
        port: 443
        targetPort: 4080
      selector:
        reaction: admin
      type: LoadBalancer
    status:
      loadBalancer: {}
    4 replies
    Like I mentioned before, we're not using ingress controllers of any kind, we've achieved SSL for all services using just ELB
    igor romanovsky
    @igorromanovsky_twitter
    Hey all...
    I'm trying to deploy reaction-admin, reaction and reaction-hydra to GCP. I've deployed reaction-admin and reaction, but now I'm struggling with the deployment of the reaction-hydra.
    unfortunately I don't have experience with "hydra" so if someone can give me a smal direction to how it could be done, I would be very grateful.
    2 replies