"Hub Operator FID is not set" via docker even already set in .env

[kodaicoder]

I has setting .env file like documents has guided but
after running I got warning sign that telling "Hub Operator FID is not set " as per image below

but I already set it in .env file as per image below

[Chaoqun-Guo]

you can have a try like this.
docker compose down hubble, then up it again.
make sure that docker init the .env and make the $XXX variable active.

[poringbom]

same error i will stop compose and remove and then not working

[wjdfx]

same here:

{"message":"✅ | Bootstrapping from 4 peers\n","timestamp":"2024-06-25T06:20:26.201Z","type":"out","process_id":0,"app_name":"hubble"}
{"message":"⚠️  | Hub Operator FID is not set\n","timestamp":"2024-06-25T06:20:26.201Z","type":"out","process_id":0,"app_name":"hubble"}```

I can confirm have been config .env file. 

[Cyncra]

Currently, it seems that only the custody FID created with warpcast is recognized as valid. As a temporary workaround, we are manually modifying the .env file to make it work. When I inquired about this issue with farquest, they advised me to report it in this repository.

[hoanmq]

The same for me. Any solution for that?

[mgladson]

getting same error message. defining the FID in docker-compose.yml, doesn't help either.

[kingo233]

Same issue. Anyone can help me?

[thuthuyng0119]

I got the same issue:
2024-07-07 12:47:05 {"message":"⚠️ | Hub Operator FID is not set\n","timestamp":"2024-07-07T05:47:05.873Z","type":"out","process_id":0,"app_name":"hubble"}
please help