[BUDI-7347] Design Page Keeps Loading and the Official Fix Does Not Work

[frnksmdlkedjnfr]

Checklist

• I have searched budibase discussions and github issues to check if my issue already exists

Hosting

• Self
  • Method: docker single image & docker compose
  • Budibase Version: 2.8.1
  • App Version:
• Cloud
  • Tenant ID:

Describe the bug
The design page keeps loading infinitely with Google Chrome, but not so with FireFox. The same happens to preview page and published app page.

To Reproduce
Steps to reproduce the behavior:

1. Clean install of Budibase:
   1.1 On Debian, run cd / && mkdir data && cd /data to create a test folder;
   1.1 Run git clone https://github.com/Budibase/budibase.git to clone the whole repo;
   1.2 run cd /data/budibase/hosting && docker compose up to run the docker containers defined in the .yml file.
2. Open Budibase and Create the First App
   2.1 With Chrome, open [server-ip]:10000 to enter the front page, then create an admin account before logging in;
   2.2 Click the 'Let's go!' button to create the first app;
   2.3 Click the 'Design' tab.
3. Problem Occurs: The screen preview keeps loading

Expected behavior
The design page shall load instantly as it does on Firefox:

App Export
If possible - please attach an export of your budibase application for debugging/reproduction purposes.

Desktop (please complete the following information):

• OS:
  PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian
• Browser: Cent Browser
• Version: 5.0.1002.354 (Official Build) (64-bit) (Chromium 102.0.5005.167)

Additional context
Installing using the official Docker command docker run -d -t \ --name=budibase \ -p 10000:80 \ -v /local/path/data:/data \ --restart unless-stopped \ budibase/budibase:latest yielded the same problem.

Attempted fixes
As per the official docs, I have added * - nofile 65536 to /etc/security/limits.conf. both inside the container and the physical Debian device.

Steps:

1. Inside the Container
   1.1 Run docker ps to get the ID of the Budibase container: ababf50ecf6e;

1.2 Run docker exec -it ababf50ecf6e sh to get inside the container;
1.3 Run apt update && apt install nano -y && nano /etc/security/limits.conf;
1.4 Append * - nofile 65536 before the EOF line, then save the file.

1. On the Host Machine
   2.1 Run apt update && apt install nano -y && nano /etc/security/limits.conf;
   2.2 Append * - nofile 65536 before the EOF line, then save the file.

1. Reboot the Host Machine
   3.1 Run reboot, then log into the host machine;
   3.2 Open [server-ip]:10000 with Chrome;
   3.3 Problem persists as described before.

Screenshots
Network activities:

_{From SyncLinear.com | BUDI-7347}

[aptkingston]

Hi @frnksmdlkedjnfr. Are you trying to develop with Budibase, or just run it self hosted? This is an unsupported hosting strategy, and the official fix only applies to dev setups.

Please read https://docs.budibase.com/docs/hosting-methods for the official hosting methods.

[frnksmdlkedjnfr]

Hi @frnksmdlkedjnfr. Are you trying to develop with Budibase, or just run it self hosted? This is an unsupported hosting strategy, and the official fix only applies to dev setups.

Please read https://docs.budibase.com/docs/hosting-methods for the official hosting methods.

I was trying to run BudiBase self-hosted. And why my strategy is unsupported? Aren't I just self-deploying BudiBase with Docker the conventional way?

[aptkingston]

Sorry @frnksmdlkedjnfr - I skimmed over this pretty quickly and I think the repo cloning threw me, but you're completely right that that's an entirely valid way to grab the docker-compose config and the environment file.

I'd also like to say thank you for the extremely detailed issue!

The thing that stands out most here is that the same thing happens when you run the "single image" docker container... That rules out the vast majority of docker/hosting related issues, especially around the Minio container, which would normally be where I would point the finger for an error like this.

That leaves me thinking that this is an error specific to your browser, which I notice is Cent Browser.

A few questions which should help us get to the bottom of this:

• Do you have another chromium based browser, or even Chrome itself, which you could try? I don't know of anyone else having tried it with Cent, so it could be that there's an issue with that specific chromium implementation.
• Could you try publishing your app, then viewing the published app? I would like to see if it loads properly when published as this does not depend on message passing across an iframe boundary, which it does in the builder and the preview window. This is where some browser-specific behaviour could cause issues, with different security permissions around iframe origins.

Again, apologies for closing this prematurely.

[frnksmdlkedjnfr]

Sorry @frnksmdlkedjnfr - I skimmed over this pretty quickly and I think the repo cloning threw me, but you're completely right that that's an entirely valid way to grab the docker-compose config and the environment file.

I'd also like to say thank you for the extremely detailed issue!

The thing that stands out most here is that the same thing happens when you run the "single image" docker container... That rules out the vast majority of docker/hosting related issues, especially around the Minio container, which would normally be where I would point the finger for an error like this.

That leaves me thinking that this is an error specific to your browser, which I notice is Cent Browser.

A few questions which should help us get to the bottom of this:

• Do you have another chromium based browser, or even Chrome itself, which you could try? I don't know of anyone else having tried it with Cent, so it could be that there's an issue with that specific chromium implementation.
• Could you try publishing your app, then viewing the published app? I would like to see if it loads properly when published as this does not depend on message passing across an iframe boundary, which it does in the builder and the preview window. This is where some browser-specific behaviour could cause issues, with different security permissions around iframe origins.

Again, apologies for closing this prematurely.

It's all good. As for your suggestions, below are the results:

1. Other Chromium-based browsers:
   I have tried the same clean set-up with Microsoft Edge, Internet Explorer (not Chromium based), and Google Chrome. None of these managed to load the design page. Internet Explorer won't even load anything.
   
   
   

2. Publishing the app:
   Yields the same results. I actually have tried publishing apps long ago. No browser except Firefox could open the app page.