revertinc / revert

Revert makes it incredibly easy to build integrations with any third party API
https://revert.dev
GNU Affero General Public License v3.0
935 stars 74 forks source link

[ISSUE-REVERT]: localhost:3000 shows a blank screen even when the clerk publishable key is present in the client .env #492

Open manish-singh-bisht opened 7 months ago

manish-singh-bisht commented 7 months ago

Describe the bug localhost:3000 shows a blank screen and the clerk publishable key is present in the client .env as mentioned in the documentation of revert.

the console of dev tools shows missing clerk publishable key.

To Reproduce proceed as mentioned in the docs of revert for self host https://docs.revert.dev/overview/developer-guide/self-host-revert

Expected behavior the expected behaviour would be that it should show a login form.

Screenshots devtools error

Desktop (please complete the following information):

Additional context Add any other context about the problem here.

geetansh commented 4 months ago

same issue, any update on this

manish-singh-bisht commented 4 months ago

hey @geetansh a possible answer from another user who faced similar issue "Found the issue. I added the REACT_APP_CLERK_PUBLISHABLE_KEY after the first run, so it was not copied over in the build process. Redid a build and now it seems to work."

other than this not sure.

geetansh commented 4 months ago

@manish-singh-bisht thanks, it worked. steps to resolve the issue:

commands: docker-compose build docker-compose run db-seed docker-compose up -d

geetansh commented 4 months ago

I was able to run the self hosted version but getting a different error now : You don't seem to have access to the Revert, please contact us at team@revert.dev.

any suggestions ?

Screenshot 2024-05-07 at 1 30 09 AM

schnetzlerjoe commented 3 weeks ago

I was able to run the self hosted version but getting a different error now : You don't seem to have access to the Revert, please contact us at team@revert.dev.

any suggestions ?

Screenshot 2024-05-07 at 1 30 09 AM

I fixed this by following logs in the api container and clicking that refresh button on the top left. It seems that the proper user tables/authentication was erroring.