Network error for other users

Please fill in the questionnaire below.

Technical Help Questionnaire

Have you read and followed the instructions at: *READ ME FIRST* Technical Help FAQs - #2 by nigel ?

Answer: Yes

Self-Hosted Installation and Setup Questions

Delete this section if you are using Baserow.io.

How have you self-hosted Baserow.

Using the official helm chart for Baserow

What are the specs of the service or server you are using to host Baserow.

NA

Which version of Baserow are you using.

1.27.1

How have you configured your self-hosted installation?

Global Changes:

global:
  baserow:    
    domain: baserow.test.eks.kube
    backendDomain: baserowapi.test.eks.kube 
    objectsDomain: baserowobjects.test.eks.kube 

Ingress changes:

ingress:
  className: alb-ingress-class
  annotations:    
    alb.ingress.kubernetes.io/ssl-redirect: "443"
    alb.ingress.kubernetes.io/target-type: "ip"
    alb.ingress.kubernetes.io/load-balancer-attributes: "routing.http2.enabled=true"
    alb.ingress.kubernetes.io/backend-protocol: "HTTP"
    kubernetes.io/ingress.class: null

Disabled Caddy:

caddy:
  enabled: false

What commands if any did you use to start your Baserow server?

helm install baserow baserow-chart/baserow --namespace baserow --values .\values-test.yaml

Describe the problem

I deployed Baserow to my local K8s cluster and created an account at the login page. I am able to login and access the baserow webpage as expected. However, other users are not able to login using those same credentials. Is this intended? I am deploying it for another member so they can try it out and determine whether it is something they, as a team, would like to use going forward. When trying to login or create an account, they get the following network error: “Could not connect to the API server”.

Describe, step by step, how to reproduce the error or problem you are encountering.

Provide screenshots or include share links showing:

NA

How many rows in total do you have in your Baserow tables?

NA

Please attach full logs from all of Baserow’s services

NA

Hi @zshyikh, I’m sorry to hear that you’re having some problems. Would you mind asking your users to open the network tab of their browser and then login? It would be useful so know which backend URL they’re connecting to. It sounds like they can’t reach the backend URL to make a login API request to.

Hi @bram,

Yes, I can ask them to do that. By “network tab” are you referring to the Developer Tools (they are using chrome) and selecting the network tab from there?

Hi @zshyikh, yep, that’s exactly what I meant. It would be useful to see where the login request is being made to, and that the response is. They should share a screenshot directly after logging in.

Sure, here is the screenshot from the network output:

Hi @zshyikh, thanks for sharing. It looks like there is a some noise in the network requests, maybe because of browser plugins. Would you mind filtering on “fetch/XHR” so that we’re only seeing the relevant requests? I also see that the token-auth/ is indeed failing. That’s what’s probably causing the problem. Although I don’t see enough information to identify which URL it tried to make a request to. Can you click on that request so that we see more details?

Nvm, I resolved the issue. Thank you for your help.