Not able to access rooms / admin with local Reticulum

[leonardoazzi]

Hi everyone,

My team and I are trying to setup a local reticulum against our local hubs instance, in order to run the whole application. We followed the steps in readme, both in Windows (with Docker) and Ubuntu. Though it's apparentlly up and running, we are not able to enter rooms, change our user to admin or even access the admin panel.

When I try to create and join a room, I get 'join crashed' in the console (in loop):

In the iex console I get this:

And when I go to the homepage (https://hubs.local:4000), I get this:

I successfully signed-in, but I think I can't turn the account into admin via the iex command. I get this:

Could anyone help us try to solve these problems? I've ran into the discussion #3082 while searching, but I think there was no definitive solution. Also found this issue in reticulum rep (didn't help hahah).
Thanks a lot! :)

[robinkwilson]

Another discussion thread to look over: #3323

^^ I'd essentially reiterate what I talked about in that message: you need to run dialog locally and configure it to talk to reticulum. Right now with only Hubs and Reticulum running locally, you're failing when reticulum tries to connect to the hubs dev dialog server (understandably, you're missing credentials).

Unfortunately, I've yet to see a local setup running all three reticulum/hubs/dialog working without the developer credentials. You're totally welcome to try and get this working, I can't guarantee the amount of help we can give you since we're a small team.

More relevant links:
#2565

[leonardoazzi]

Thanks, @robinkwilson.

I was not so aware of dialog and the developer credentials, but later I found some comments and recent discussions about it.

We are testing the system and, if we have success, we will be sharing with you right away.

[samkohli]

Once you go into dialog. Make sure to run:

npx browserslist@latest --update-db

or the error will still appear

[agriggs2]

I believe I found the issue with running the whole hubs stack locally.
Missing file index.html. Please try again.
from what I can tell the admin dashboard is trying to access https://hubs.local:4000/api/v1/app_configs but no matter what it returns {"error":"unauthenticated"} so it looks like you have to have an account prior to running https://hubs.local:4000/?skipadmin or going to admin dashboard.

any way to get around this?