If not. Is there any documentation explaining to do so
@loan-laux These is what I found in my logs
INFO[39m Reaction: [36m Initializing MongoDB replica set...
INFO[39m Reaction: [36m Connecting to MongoDB...
INFO[39m Reaction: [36m Connected to MongoDB. Database name: reaction
WARN[39m Reaction: [36m Failed to initialize a MongoDB replica set. This may result in errors or some things not working. Error: Error initializing replica set: not authorized on admin to execute command { replSetInitiate: { _id: "123", version: 3, protocolVersion: 1, members: [ { _id: 0, host: "cluster.something.mongodb.net", priority: 100 } ] }, lsid: { id: UUID("12345678") }, $clusterTime: { clusterTime: Timestamp(1590779116, 1), signature: { hash: BinData(0, 12345ABCDE), keyId: 123456789 } }, $db: "admin" } (Unauthorized)
While trying to deploy from the ansible playbook. I changed readction's repos to my custom repos by creating new config.local.mk
Has anyone facing this problem before ?
@javierdaza Can you try and pass the env variable
REACTION_SHOULD_INIT_REPLICA_SET=false to your reaction API container?
I don't understand that at some point the API looks like is waiting ok
The target group protocol is HTTP, path is /graphql, port is 3000 and success codes is 400.
Is there anything wrong with my target group configuration or health check?
GraphQL subscriptions ready at wss://api.mydomain.com/graphql (port 3000) and then a couple of minutes later it kills the task SIGTERM.The target group protocol is HTTP, path is /graphql, port is 3000 and success codes is 400.
Is there anything wrong with my target group configuration or health check?
@loan-laux thanks. It was fine. A couple of things I realized of the tutorial so far(RC 3):
- In the section Creating your cluster, the content is duplicated
- For my tbs-hydra-admin task to work I had to enable port 4445 in the security groups of the EC2ContainerService-<your-cluster-name> instance
Hi
Have you ever received an error
From firefox I get a CORS related warning
Have you ever received an error
net::ERR_CERT_COMMON_NAME_INVALID when trying to deploy tbs-admin??From firefox I get a CORS related warning
Cross origin request blocked: The same origin policy does not allow remote resources to be read
It is https://hydra.mydomain.com/.well-known/openid-configuration. (Reason: CORS request unsuccessful)
On the other hand, Chrome is telling me a different story
DEBUG [react-context-oidc] : overriddenConfiguration
{client_id: "reaction-admin", redirect_uri: "https://admin.mydomain.com/authentication/callback", response_type: "code", post_logout_redirect_uri: "https://admin.mydomain.com", scope: "openid", …}
authority: "https://hydra.mydomain.com"
automaticSilentRenew: true
client_id: "reaction-admin"
loadUserInfo: true
post_logout_redirect_uri: "https://admin.mydomain.com"
redirect_uri: "https://admin.mydomain.com/authentication/callback"
response_type: "code"
scope: "openid"
silent_redirect_uri: "https://admin.mydomain.com/authentication/silent_callback"
triggerAuthFlow: true
__proto__: Object
INFO [react-context-oidc] : Protection : true
INFO [react-context-oidc] : Protected component mounted
[Violation] 'setInterval' handler took 228ms
I'm having trouble loading the admin on a prod environment of the reaction admin. I've noticed in the websocket messages that I'm able to authenticate, but then I get this response:
a["{\"msg\":\"updated\",\"methods\":[\"3\"]}"]
a["{\"msg\":\"result\",\"id\":\"3\",\"error\":{\"isClientSafe\":true,\"error\":400,\"reason\":\"Match failed\",\"message\":\"Match failed [400]\",\"errorType\":\"Meteor.Error\"}}"]and then shows a blank admin area with only the Reaction logo and a logout buttun. From what I understand, "match failed" is an unhandled Meteor error. Has anyone experienced this before? Why might that be happening?
i also see this warning in the backend browser console:
name: "reaction-client",
hostname: "backend-prod.examplestore.com",
pid: undefined,
level: 40,
msg: "Missing storefront home URL. Please set this from the shop settings panel so that customer users can be redirected to your storefront.",
time: Date Sat Jun 06 2020 17:43:42 GMT-0700 (Pacific Daylight Time),
v: 0i wonder if the pid being undefined is an issue
@javierdaza I had this issue once but I don’t remember how I handled it… Sorry, I know that’s not useful to you. Can you manually reach https://hydra.mydomain.com/.well-known/openid-configuration?
@loan-laux
yeah actually, looking through the logs, i'm getting this:
yeah actually, looking through the logs, i'm getting this:
Exception while invoking method 'oauth/login' { Error: Match error: Expected string, got undefined
at check (packages/check/match.js:36:17)
at MethodInvocation.oauthLogin (imports/plugins/core/hydra-oauth/server/oauthMethods.js:18:3)
at currentArgumentChecker.withValue (packages/check/match.js:118:15)
at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)
at Object._failIfArgumentsAreNotAllChecked (packages/check/match.js:116:43)
at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1764:18)
at DDP._CurrentMethodInvocation.withValue (packages/ddp-server/livedata_server.js:719:19)
at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)
at DDPServer._CurrentWriteFence.withValue (packages/ddp-server/livedata_server.js:717:46)
at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)
at Promise (packages/ddp-server/livedata_server.js:715:46)
at new Promise (<anonymous>)
at Session.method (packages/ddp-server/livedata_server.js:689:23)
at packages/ddp-server/livedata_server.js:559:43
message: 'Match error: Expected string, got undefined',
path: '',
sanitizedError:
{ Error: Match failed [400]
at errorClass.<anonymous> (packages/check/match.js:91:27)
at new errorClass (packages/meteor.js:725:17)
at check (packages/check/match.js:36:17)
at MethodInvocation.oauthLogin (imports/plugins/core/hydra-oauth/server/oauthMethods.js:18:3)
at currentArgumentChecker.withValue (packages/check/match.js:118:15)
at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)
at Object._failIfArgumentsAreNotAllChecked (packages/check/match.js:116:43)
at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1764:18)
at DDP._CurrentMethodInvocation.withValue (packages/ddp-server/livedata_server.js:719:19)
at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)
at DDPServer._CurrentWriteFence.withValue (packages/ddp-server/livedata_server.js:717:46)
at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1304:12)
at Promise (packages/ddp-server/livedata_server.js:715:46)
at new Promise (<anonymous>)
at Session.method (packages/ddp-server/livedata_server.js:689:23)
at packages/ddp-server/livedata_server.js:559:43
isClientSafe: true,
error: 400,
reason: 'Match failed',
details: undefined,
message: 'Match failed [400]',
errorType: 'Meteor.Error' },
Hi, how can I obtain the user ID of a created user account when running locally in Docker. The doc says: "Substitute a real user ID, which is the internal user ID you see in the _id field in the MongoDB users collection." but how can I see this collection when Mongo is running in Docker locally ? Reference: https://docs.reactioncommerce.com/docs/developer-authentication
@loan-laux I am redirected to this login https://hydra.mydomain.com/login?nextUrl=%2F.well-known%2Fopenid-configuration
another issue i'm running into is that my example storefront instance tries to open a websocket connection to the backend, but is receiving a 502 bad gateway error, even though i can connect to it through a firefox websocket client. i would also think that setting DISABLE_WEBSOCKETS=1 in the .env file would make it fall back to http(s), though that doesn't seem to work either.
have you run into any issues with the frontend websocket connections in prod?