The situation
Beeper Server 4.3.152 (stable), headless, Linux x64 in Docker. Updated from 4.3.144, same result on both.
Logged in four local bridges through POST /v1/bridges/{id}/login-sessions: local-whatsapp, local-signal, local-facebook (flow messenger-lite) and local-instagram (flow instagram-password). All four logins completed.
- WhatsApp and Signal show up in
GET /v1/accounts, and their chats come back from GET /v1/chats.
- Facebook and Instagram don't.
GET /v1/bridges/local-facebook returns accounts: [] with status available, but GET /v1/bridges/local-facebook/logins lists the login with its account IDs.
GET /v1/chats?accountIDs=<facebook or instagram account> returns 0 items.- Right after login the bridges did work: account state was
RUNNING, and portals and messages were landing in each bridge's megabridge.db.
- After a server restart, FB and IG are never started again. The log shows
Bridge started for WhatsApp and Signal on every restart, nothing for Facebook, and Instagram only once at the initial login. Their message counts stop growing from that point.
One difference I noticed: the FB/IG account states have an empty displayName, while WA/Signal have the phone number.
The FB/IG logins also came back with the same login IDs my Beeper Desktop on another machine uses for its own local FB/IG bridges, so the server might be treating them as another device's accounts. Signal reused the Desktop ID too and works fine, so I'm not sure that's it.
Ask
Start local-facebook and local-instagram on server boot like WhatsApp and Signal, and list their accounts and chats in /v1/accounts and /v1/chats so API/MCP clients can read them.
Looks related to #14 / #31 (bridge accounts not initialized on headless server), which is fixed for WA/Signal on 4.3.152 but not for these two.
The situation
Beeper Server 4.3.152 (stable), headless, Linux x64 in Docker. Updated from 4.3.144, same result on both.
Logged in four local bridges through
POST /v1/bridges/{id}/login-sessions:local-whatsapp,local-signal,local-facebook(flowmessenger-lite) andlocal-instagram(flowinstagram-password). All four logins completed.GET /v1/accounts, and their chats come back fromGET /v1/chats.GET /v1/bridges/local-facebookreturnsaccounts: []with statusavailable, butGET /v1/bridges/local-facebook/loginslists the login with its account IDs.GET /v1/chats?accountIDs=<facebook or instagram account>returns 0 items.RUNNING, and portals and messages were landing in each bridge'smegabridge.db.Bridge startedfor WhatsApp and Signal on every restart, nothing for Facebook, and Instagram only once at the initial login. Their message counts stop growing from that point.One difference I noticed: the FB/IG account states have an empty
displayName, while WA/Signal have the phone number.The FB/IG logins also came back with the same login IDs my Beeper Desktop on another machine uses for its own local FB/IG bridges, so the server might be treating them as another device's accounts. Signal reused the Desktop ID too and works fine, so I'm not sure that's it.
Ask
Start
local-facebookandlocal-instagramon server boot like WhatsApp and Signal, and list their accounts and chats in/v1/accountsand/v1/chatsso API/MCP clients can read them.Looks related to #14 / #31 (bridge accounts not initialized on headless server), which is fixed for WA/Signal on 4.3.152 but not for these two.