Trouble with invalid PUBLIC_BACKEND_URL in helm deployment

Technical Help
1

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.

I am using the helm charts for baserow deployment.

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

I am using an AWS EKS cluster running the r5a.xlarge instance type and the ami-0fc370be4e6093918 image.

Which version of Baserow are you using.

Latest version

How have you configured your self-hosted installation?

The only configs are the ones that were mentioned here on the helm installation guide.

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

Helm install command

Describe the problem

I have deployed the baserow app in my EKS cluster via helm charts. I am currently experiencing an issue where, when trying to reach the frontend web page, I am met with a page that says:

The PUBLIC_BACKEND_URL environment variable has been set to an invalid value. Your site admin must change PUBLIC_BACKEND_URL to a valid URL starting with http:// or https:// and then restart Baserow to fix this error.

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

Deploy baserow using the helm installation guide, configuring both frontend and backend ingresses as well as domains along with any AWS S3 configs as mentioned in the guide.

Provide screenshots or include share links showing:

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

N/A

Please attach full logs from all of Baserow’s services

Where would I obtain these logs from?

2

Hi @zshyikh, would you be able to share all the environment variables that you’ve set? Feel free to hide the privacy-sensitive ones. I would specifically be interested in the value of the PUBLIC_BACKEND_URL?

3

Hi @bram,

Sure, I can share them. Most of the changes I introduced are to the frontend and backend ingresses. They have the following annotations:

  alb.ingres s.kubernetes.io/backend-protocol: "HTTP"
  alb.ingress.kubernetes.io/healthcheck-interval-seconds: "5"
  alb.ingress.kubernetes.io/healthcheck-timeout-seconds: "4"
  alb.ingress.kubernetes.io/success-codes: '400'
  alb.ingress.kubernetes.io/load-balancer-attributes: "routing.http2.enabled=true"
  alb.ingress.kubernetes.io/security-groups: "sg-03452c58d507822b8"
  alb.ingress.kubernetes.io/ssl-redirect: "443"
  alb.ingress.kubernetes.io/target-type: "ip"
  alb.ingress.kubernetes.io/subnets: "subnet-0cca458eb809c2747,subnet-08f312e743108d54f"
  alb.ingress.kubernetes.io/certificate-arn:

The public backend URL and public frontend URL are as follows:

publicBackendUrl: https://baserowapi.navy.eks.kube
publicFrontendUrl: https://baserowserver.navy.eks.kube`Preformatted text`
4

Hi,

Could I please get an update for this? Please let me know if any additional information is needed.

5

Hey @zshyikh, apologies for my delayed response. I don’t have much experience with this Helm chart because it’s maintained by the community, and not an official one from Baserow. When checking the config variables, I noticed this one frontend.config.disablePublicUrlCheck. Maybe you can disable this check, although I’m not 100% sure this config var disabled the error you’re encountering.

6

I changed that config option to a “non-empty” value like it is mentioned in the notes for the helm chart however I do not see anything different. It it still showing that invalid public backend URL message.

7

Hey @zshyikh, I’m not really sure what could cause the Helm chart to run into this problem, to be honest. Would it be possible for you to reach out to the author of the Helm chart and ask them for help?

8

Or maybe use one of the officially supported ways of self-hosting, like the all-in-one image (https://baserow.io/docs/installation%2Finstall-with-docker)? We will definitely be able to help you there. We’re also planning on building an official Baserow Helm chart soon.

9

Hey Bram,

I see…Let me try reaching out to the current author of the community baserow chart. It is important for my organization to have a helm chart deployment if possible.

It is also great to hear that there will be an official baserow helm chart. Do you have an idea of the timeline for that perhaps?

10

Hi @zshyikh, I completely understand that a Helm chart is desired within your organization. I’m going to do my best to expedite the development of our own official Helm chart internally. I can’t make any promises yet, but what would be an ideal timeline/deadline for you?

11

Hey Bram,

There is a lot of interest from particular departments within my organization for the use of Baserow. The quicker we could start using it, via helm chart, the better. No ideal timeline that I have in mind but a month or two might be nice if possible.

12

We’ve actually started the development of our official Helm chart this week. I hope to be able to release before the end of the month.

13

Hi, I just wanted to check in and get the status of the official Helm chart for Baserow. Is it still in development or has a release been published for use? If there is a release, where could I find it?

Thank you.

14

Hi @zshyikh, we expect to launch an early version of our official Helm chart somewhere this week.

15

Hello @bram,

Is there a version of the official Baserow helm chart available for use?

16

Hi @zshyikh, there is, but it’s not 100% finished yet. We’re still putting some dots on the I. But in case you’re interested, you can find it here baserow 0.1.2 · baserow/baserow-chart.

17

Oh nice! This looks promising. I will wait for the 1.0 release before using it however to eliminate possible issues. Thank you for this and I will keep an eye on it for further development.