Unable to setup a reliable REI3 instance

Julien

Hi there,
first off, I must say that I'm impressed with REI3 with all its features!

The issue
I'm down to about 8-10h trying to setting up an instance on a local server. Following the documentation, all went pretty well except that after every reboot of the server, the login page gets stuck on the "Waiting for server connection..." message and the console logs "WebSocket is closed before the connection is established." every few seconds. I just can't nail the reason why it happens. On each reboot, I go change some settings and it magically starts working again (until next reboot).
I feel that I'm close to find the solution to that seemingly random problem but I'm running out of solutions...

My setup

REI3 3.10 for Linux on Ubuntu Server 24.04 on a VM
Postgresql 16
Accessing VM through SSH and REI3 from an M1 mac
REI3 is listening on port 8080
REI3 is installed in the server's user's home folder (/home/rei3/r3).

More info
Launching REI3 with the -http flag doesn't solve the problem.

When running the commands systemctl status postgresql@16-main and netstat -tunelp | grep 5432, I can confirm that Postgres is active and listening on the right port.

When running the command systemctl status rei3, I can tell that REI3 is active and logging incoming request from the client browser on the mac.

Have anyone experienced this kind of problem? Any advice could help me figure out how to make REI3 work for good! 😅
Thanks in advance for any help!

gabriel

The setup sounds fine from what you describe. In general, if all services are running (r3, postgres) we need to take a look at network and client.

Do you use a proxy?
Do you have the same issues with another browser?

Some other points:

What changes do you do so that it suddenly works? Do you have an example?
When restarting the server, REI3 takes a bit of time to build its cache - depending on the system and installed apps, this can take even a full minute. In this case you would notice system load on the r3 and postgres processes until the cache is ready. While the server cache builds, clients (eg. browsers in this case) would still show "Waiting for server connection".