Elie Obeid

@kishorenc I have a public ip v6 and v4, and I'm using v4 as the peering address this is the config file ``` ; Typesense Configuration [server] api-address = n1.example.com...

@kishorenc here's the log file after I set the peering address to `0.0.0.0` ``` Log file created at: 2023/09/06 10:59:16 Running on machine: Running duration (h:mm:ss): 0:00:00 Log line format:...

One easy way to fix this issue is to have the private IP as `peering-address` but have the other nodes use the public IP in the `nodes` file to try...

@kishorenc I used the public ip in `peering-address` and `0.0.0.0` in `api-address`, the server still fails and restarting typesense now takes few minutes to complete, here's the log ``` I20230908...

I'm no longer part of the company using typesense nor have any interest in using it in the future. I'm leaving this issue open just because it's affecting other users...

> The listed extensions should be installed the first time you connect to the dev container, when you add extensions to the list you need to either rebuild the container...

@chrmarti your suggestion worked thank you, so I did is this, I left `Dockerfile` and `docker-compose.yml` as is because I don't want to touch production stuff just to fix some...

One last thing before we close this issue, please create a dev container and install the pylance extension `ms-python.vscode-pylance` when the dev container starts, it will ask you again to...

@chrmarti here's the output ``` 2025-05-22 20:26:44.810 [info] 2025-05-22 20:26:44.821 [info] Installing extensions... 2025-05-22 20:26:44.824 [info] Extension host agent started. 2025-05-22 20:26:44.839 [debug] Error while reading the extension cache file:...

@chrmarti yes the container has internet access, I pull everything from the web, it's my pc, not some isolated VPC network. Pylance is the only extension that doesn't get installed...