websocket issue

adi

Describe the bug

I try to evaluate rootdb but failed with the websocket communication:
after entering default credential, I am prompted to to change the password. Updating the password fails with the following error: Request has been blocked because the Websocket server is not running. Please contact you administrator.

I use you docker image and changed 'localhost' to the public facing hostname of the server. In tcpdump I see packages going back and forth on the ws port.

What else need to be changed?

Thanks, Adi

To Reproduce
Follow the installation instruction but connect from other host than localhost.

Expected behavior
A clear and concise description of what you expected to happen. (if not obvious)

Provide relevant log

For frontend error: none
For an API error: none in nginx ws error log

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Browser chrome, edge win10, firefox debian 12
Version firefox 115.13.0esr (64-Bit)

Smartphone (please complete the following information):

Installation method

With Docker
If without Docker, at least the PHP version.

Additional context
Add any other context about the problem here.

Sébastien P.

Hi,

Is it possible to have more details about your config, so I can I have a better understanding on how you want to use a facing hostname instead of the default localhost`?

are you using a nginx/apache2 proxy ?
or did you simply updated /etc/hosts with the facing hostname pointing to 127.0.0.1 ? (in this case it should not works at all, because of SRF token mismatch)
did you change some configuration files ?

Log that if you want to use a custom hostname to access RootDB I think you have to setup nginx proxies :

for the frontend, a rootdb.yourhostname.tld, proxy to : localhost:8090
for the api a rootdb-api.yourhostname.tld , proxy to: localhost:8091
for the ws ap a rootdb-ws-api.yourhostname.tld, proxy to : localhost:8081
and update, from docker-compose side, the files api_env and app-config.js to fit your custom hostnames, and it should work, I guess. ( I'm not using docker on my productions servers (for rootdb), so did not took time to test that)

Take a look at the proxy for the ws api proxy in the documentation.

Sébastien P.

Hi again @adi ,

I made tests from my side, based on the configuration you sent me by email and I was able to make it work with a different hostname than the default localhost

Here what I made :

add, indeed, a 127.0.0.1 thehostnamefromyouconfigfile.tld
and updated the api_env to let the websocket server (reverb) listen on localhost instead of the custom hostname.

And with these changes I was able to access RootDB, using the custom hostname, setup the root password, an admin/dev user and create a report.

Please find the updated configuration here : rdb-mariadb-memcached-2024-07-18.zip

adi

Dear Sébastien
Thanks for your help. I understood you added 127.0.0.1 thehostnamefromyouconfigfile.tld to /etc/hosts and accessed the url from the same machine as docker runs. When these are separate machines, it won't work. (same error)

Thanks, Adi

Sébastien P.

Hi @adi,

For testing purpose, I temporarily installed docker and RootDB images on one of my remote server :

Opened ports 8090,8091,8081
Updated my /etc/hosts file with 185.143.103.214 thehostnamefromyouconfigfile.tld
And you can access RootDB without issue here
This setup is working with the archive's content I provided earlier, without modification. (I'll remove it later today )
You have an account adi with the super-admin default password.

If it's not working, maybe try:

in your web-browser private mode ;
delete all cookies and data associated to the `thehostnamefromyouconfigfile.tld domain, and then make a clean refresh of the webapp.

adi

Dear Sébastien

It is working now. Thanks a lot for our help. After applying your config, the browser cache was the problem.

Thanks, Adi

Sébastien P.

You're welcome 🙂

Have a nice weekend.