---
title: "Comment by phil on \"The ultimate Supabase self-hosting Guide\" | Hashnode"
description: "Great blog. Although I still run into an issue where I cannot fully use the authentication panel inside supabase. For example, I cannot use create new user feat"
url: "https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933"
---

[Discussion](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd)

Comment [The ultimate Supabase self-hosting Guide](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd)

[phil](https://hashnode.com/@phil383)

[Sep 3, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933)

Great blog. Although I still run into an issue where I cannot fully use the authentication panel inside supabase. For example, I cannot use `create new user` feature. Do you perhaps have a git repository of this project?

[David Lorenz](https://hashnode.com/@activenode)

[Sep 3, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-64f4a029b2147985ab4ede99)

I gave my last comment too early. I am seeing that the auth API is called properly so I'd love to get more information about how you create a user and which error message you face.

[David Lorenz](https://hashnode.com/@activenode)

[Sep 3, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-64f4a0f6b2147985ab4edeac)

Checking the Calls it seemed to call `/auth` directly without `api....` . That means in addition to `/storage` you also need to do the same config for `/auth` location. I changed the post. Tell me if it helps please

[phil](https://hashnode.com/@phil383)

[Sep 3, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-64f4a25cb2147985ab4edebf)

[David Lorenz](https://hashnode.com/@activenode) Thank you for being so quick. Yes that solved the issue indeed.

[David Lorenz](https://hashnode.com/@activenode)

[Sep 3, 2023](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-64f4ac83b2147985ab4edf6a)

Awesome [phil](https://hashnode.com/@phil383) . Appreciate the Feedback. Tested all functionalities but user creation.

[phil](https://hashnode.com/@phil383)

[Jan 1, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-6592c95bbb9e53e89c9fb632)

[David Lorenz](https://hashnode.com/@activenode)

Hey david, I seem to run into an issue and I thought why not ask you. Everything works except for the auth creation of users. I think it has to do with my nginx/authelia settings but perhaps you know more.

I obtain the following error:

```
Access to fetch at 'auth.domain.com (redirected from 'studio.domain.com/auth/v1/admin/users&) from origin 'studio.domain.com& has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
```

with `domain.com` being my hostname of course. Do you know what to assess?

[David Lorenz](https://hashnode.com/@activenode)

[Jan 3, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-6595264de08a9c26915a0a83)

Hey [phil](https://hashnode.com/@phil383). Hm, that's unusual. Normally this shouldn't happen as it tries to redirect from an API request, so from a "background request". There was an error in the Supabase JS code that caused this because the auth info was explicitly omitted but I fixed this in a PR and it got merged so now I have to check again if it came back. Here's my PR: [github.com/supabase/supabase/pull/18156](https://github.com/supabase/supabase/pull/18156)

The good news: This isn't an infra problem, but a JavaScript problem in Studio if it is what it was back then. So you can still create users via API.

[David Lorenz](https://hashnode.com/@activenode)

[Jan 3, 2024](https://hashnode.com/posts/the-ultimate-supabase-self-hosting-guide/64e85d050e78298524ccbcfd/comment/64f49c8c448e318af4d5d933#reply-659527693cec7405d536754a)

[phil](https://hashnode.com/@phil383) So my fix is still there in the current source code. Can you check your version if you got the newest images? [github.com/supabase/supabase/blame/master/apps/st…](https://github.com/supabase/supabase/blame/master/apps/studio/data/auth/user-create-mutation.ts)
