Login page sometimes appears to be not working (if you are already logged in)

I’ve build an app where users can login (used the prebuilt login page). In 95% of all logins the page works as expected. But sometimes the page shows no reaction. No error message, just nothing.
I’m trying it again and again and after 3 or 10 times (sometimes 2 seconds, sometimes 10 seconds) the page seems to be “back again” and logs in successful.
Is there any idea what might be the problem? Baserows SaaS-server not available & not answering?
Is there anything I can do to provide more details?

Anyone else with the same problem?

Hi @be_Berlin, if you could open your dev tools in your browser when this is happening and go to the network tab and check for errors there, giving us the details of any errors you see there will help us identify the possible cause of this.

HI @cwinhall ,
is it this information that you need? (see screenshot)

I tried to login two or three times (and it didn’t work).

Thanks for your help in advance.

Could you try filtering by Fetch/XHR as I don’t see any requests here that are failing (They would show up in red)

It seems as there are no errors (nothing in red).

But the login still don’t work.

Finding no errors in the log is exactly how it “feels”: just nothing happens…?

Hey @be_Berlin,

When you say nothing happens, what do you expect? Did you add a redirect action or something after the login that is not triggered? What do you expect to happen?

As the credentials are correct the page should login in myself and redirect to the next page.
In general this works as expected. But not in 100% of all cases. 95% are okay, but sometimes the page just don’t react.
Even if my credentials would be wrong I would expect anything like a “Password incorrect”-message.
I’ve just send @cwinhall test credentials via direct message - maybe it is a chance to find out more.

Thanks, I think I know what’s happening: if you are already loggued in and visit the login page and try to login you won’t be redirected to the next page as you are already loggued in.

Could you try to hide the login form when the user is loggued in (Visibility tab of the element configuration) and add a link to the protected page that is shown only when the user is loggued in to see if it helps?

Okay, I’ll try that and give you an update later if it helped…

I changed the site as @jrmi suggested.

Now the behaviour is as follows:

  • as a not-logged-in user I see the login form to enter my credentials (as expected)
  • login in works (as expected)
  • the login form has Events “after login” and there is the command to open the next page (start page for logged-in users). This does NOT work anymore. Instead, the same page now shows the content for logged-in users (instead of opening the next page).

I’m not sure if this is really the case but it seems for me as the site is “hiding” (=no visibility) the login form in the moment after a successful login but BEFORE the events associated with the login form are executed.

It’s probably the good analysis, good job. We need to fix that. In the meantime may be you could just keep the link to redirect to the new page and keep the login form displayed so at least already loggued in users know they are loggued and have a way to navigate to the protected pages?

Altenatively, you could change your home page (the one with / as path) to an authenticated page so if a user that is not loggued visit it he will be redirected to the login page (and redirected back after login) but if he is already loggued in he can directly see the page what do you think?

Thanks for your kind reply. If this is helpful for developing Baserow I’m really happy to contribute that little piece. Moreover I’m happy to receive your dedicated support.

Concerning my Application and my home page: no problem, I’ll find a good solution now that I understand what’s happening behind the scenes.

I’ll also update the title of this post from old version “Login page sometimes doesn’t work” to a more precise new version.

1 Like

For your information, these problems will be fixed with the next release.