I can't connect to my vircadia-metaverse

[fortuneCookieGO]

I set up a metaverse server of my own,
but when I connect,
I changed metaverse to my own address from 'Settings' of 'vir Launcher'
(Error code 1: The full error is shown below : we were unble to retrieve the metaverse information for http://192.168.1.104),
What is the reason? Is it because I use an Intranet IP server ?Or you need to recompile your own client because you cannot use the official client .

[Misterblue]

When you run the ice-server and Interface (the client), you need to set the environment variable HIFI_METAVERSE_URL to the URL of your metaverse server. So, after building Vircadia with vircadia-builder:

To start the ice-server:
export HIFI_METAVERSE_URL=https://yourdomainserver:9400
/opt/vircadia/install_master/run_ice-server --url ${HIFI_METAVERSE_URL} &

Then, to start your domain-server:
export HIFI_METAVERSE_URL=https://yourdomainserver:9400
export ICE_SERVER_URL=youriceserver:7337
/opt/vircadia/install_master/run_assignment-client &
/opt/vircadia/install_master/run_domain-server -i ${ICE_SERVER_URL} &

Then, to start Interface
export HIFI_METAVERSE_URL=https://yourdomainserver:9400
./interface.exe

[johnfelipe]

@Misterblue i do this:

and

show m this

Error code 1
The full error is shown below:
We were unable to retrieve the metaverse information for http://localhost:9400/

how can configure all this for my local env?

[Misterblue]

Sorry for the delay...
Not sure what's failing there. If you add parameters to the debug section of iamus.json will cause the metaverse server to log detailed info. Hopefully, some log messages would give a clue.

I also notice that, in the configuration I run locally, I specify the port in the "metaverse" configuration section. The iamus.json file that I use locally, looks something like:

{
    "metaverse": {
        "metaverse-server-url": "http://192.168.86.56:9400/",
        "default-ice-server-url": "192.168.86.56:7337"
    },
    "database": {
        "db": "localtest",
        "db-host": "192.168.86.56",
        "db-user": "metaverse",
        "db-pw": "xxxxxxxxxxxx"
    },
    "debug": {
        "loglevel": "debug",
        "devel": true,
        "request-detail": true,
        "request-body": true,
        "metaverseapi-response-detail": true
    }
}

[Misterblue]

Also, once the image is running in a container, you can do:

vircadia@nyxx:~/run> docker ps
CONTAINER ID   IMAGE                           COMMAND                  CREATED              STATUS              PORTS                                       NAMES
079019400c99   ghcr.io/vircadia/iamus:latest   "/home/cadia/run-iam…"   About a minute ago   Up About a minute   0.0.0.0:9400->9400/tcp, :::9400->9400/tcp   metaverseServer
9b42bbeaa604   mongo:latest                    "docker-entrypoint.s…"   10 months ago        Up 6 days                                                       mongodb
vircadia@nyxx:~/run> docker inspect 079019400c99   # CONTAINER ID from above list
...

This will display all the information about the container and you can verify which ports are being exposed and used.

[johnfelipe]

Can u create doc.md for follow in Ubuntu 21 from scratch