[Bug]: Not able to login. Dead home page.

[srigurubyo]

What happened?

While I tried to login, no response from the screen - even after I click the login button.

The page layout is completely distorted.

Steps followed:

1. Installed Docker on Ubuntu 22.04.4 LTS
2. Installed supabase
3. Started supabase and followed the remaining instructions as per the guide

Problem: Able to access supabase, backend (returns OK) and the docs but not able to login

Public URL: http://52.66.8.225:3000/

User / Password: [Default Values]

Relevant log output

No response

Twitter / LinkedIn details

No response

[dosubot]

Hello @srigurubyo! 👋 I'm Dosu, a bot here to help you solve bugs, answer your questions, and guide you on your way to becoming a contributor. While we wait for a human maintainer, feel free to think of me as your assistant in this process. I'm here to support you. I've seen the issue you're facing, and I'm currently looking into it. Expect a full answer shortly!

[StanGirard]

Can you make sure that the NEXT_PUBLIC_FRONTEND_URL is correctly set to use either your ip or your domain name ?

[srigurubyo]

Sure, thanks for your quick response.

Will check and revert.

Best wishes to th team for the great work!

[tc0715888]

I also clicked on login but there was no response, using the account admin@quivr.app!

[StanGirard]

Hey guys!

If you are installing on your own vps, you can follow this tutorial :) https://docs.quivr.app/deployment/digital_ocean

[tc0715888]

I already have my own VPS, following the tutorial I can still open 3000 web pages, but clicking on login is ineffective!

[tuninger]

I also clicked on login but there was no response, using the account admin@quivr.app/admin! how to fix it?

[dosubot]

To address the login issue you're experiencing, first ensure that the NEXT_PUBLIC_FRONTEND_URL in your environment configuration matches your application's public URL, including the correct protocol and port. For your setup, this means including http:// and specifying port 3000 if that's what you're using.

Next, check your browser to ensure JavaScript is enabled, as its restriction could hinder login functionality. Also, inspect the browser's console for any JavaScript errors that might reveal more about the issue.

Additionally, use your browser's developer tools to monitor network requests when attempting to login. Look for any requests that fail or return error responses, as these could indicate where the problem lies.

Finally, confirm that all related services, including Docker containers and Supabase, are running correctly. This involves checking that Docker containers are up and that Supabase services are accessible.

By following these steps, you should be able to identify and resolve the issue preventing login.

Details

Sources

• Cannot login at browser remotely
• Using the docker deployment in the project, the front-end page cannot be accessed normally
• docs/deployment/digital_ocean.mdx
• docs/configuring/environment-variables.mdx
• .env.example
• backend/supabase/config.toml

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[github-actions]

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.