Right, For testing purpose I was just trying the reaction-dev-platform. I thought , I'll redeploy my repo once this was working.
Shouldn't it work properly ideally ?
Even if I create images of my sub projects and deploy containers from them. I should be facing the same issue -
Shouldn't it work properly ideally ?
Even if I create images of my sub projects and deploy containers from them. I should be facing the same issue -
Redirect URL is using an insecure protocol, http is only allowed for hosts with suffix `localhost`, for example: http://myapp.localhost/.
By the way, if you want a simple reverse proxy that doesn’t have all the fluff of Traefik, I would recommend setting up a simple nginx instance. It gets the job done.
Btw, I am not using traefik right now. I do not have a domain name. I am just trying to run it on a cloud with an ip.
And particularily Hydra + the IDP. The rest you can perhaps skip, but Hydra will complain if it doesn’t have a real URL with HTTPS.
@ankurpata You can’t if you don’t have an OAuth server set up, like Hydra. But you can get a free .tk domain or something like this, right?
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?