-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New instance after creating account fails at environments.single TRPC command #19
Comments
Any luck with this issue. I am facing exactly same issue |
If you look at the error message, the one above is very hard to read, but if you try to get the text terms, you find a call to // This relies on a header set by the client config if
// used within DashboardContext. Will not work elsewhere.
export const organizationMiddleware: MiddlewareFunction<
AuthenticatedContext,
OrganizationContext,
unknown
> = ({ ctx, next }) => {
if (!ctx.organizationId) {
throw new trpc.TRPCError({ code: 'BAD_REQUEST' })
}
... Seem like missing environment variables and user fault? |
Thanks for the response - how should I be setting organization id then? Not sure how that works, and having a hard time figuring it out in the source code. Not seeing any documented environment variables, and it looks like it's retrieved from the database at runtime. |
Currently I'm setting APP_URL, DATABASE_URL, AUTH_COOKIE_SECRET, and WSS_API_SECRET only. |
@ajoslin The issue is probably your reverse proxy setup. I had the same error, and it was due to the the cookies with underscores "_" being in the cookie names. NGINX for instance will strip all cookies with underscores as not valid. I had to add this to my NGINX config then it worked.
|
Hi team, I'm attempting to switch from cloud to the self hosted server.
I'm using the Docker setup on latest version and having trouble getting fully running.
I'm getting a failure after creating a new instance with a fresh account at /api/trpc/environments.single
It just returns a 400 over and over. The response payload is likeso:
It's spitting some stacktrace into the response. Nothing in the logs on the server.
Any idea on this?
The text was updated successfully, but these errors were encountered: