Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.allthingslinux.org/llms.txt

Use this file to discover all available pages before exploring further.

This page covers operational tasks for the bridge: checking health, debugging adapter connections, and managing Portal identity integration.

​
Health check

The bridge container uses pgrep to verify the Python process is running. Check the health status: 
docker inspect --format='{{.State.Health.Status}}' atl-bridge
# Expected: healthy
The underlying health check command is pgrep -f "bridge.__main__".

​
Restarting the bridge

docker compose restart atl-bridge
After a restart, verify all adapters reconnect by inspecting logs: 
docker logs --tail 50 atl-bridge
Look for connection confirmation messages from each adapter.

​
Debugging adapters

Each adapter logs connection events and errors. Key log patterns to watch for:
PatternMeaning
[Discord] bot readyDiscord adapter connected successfully
[IRC] connected to <host>IRC adapter connected to the server
[XMPP] component startedXMPP adapter established a session

​
Common error patterns

PatternMeaningResolution
[Discord] auth/token errorsInvalid or expired Discord tokenRegenerate DISCORD_TOKEN in the Discord Developer Portal
[IRC] connection refusedIRC server unreachableVerify UnrealIRCd is running with just status
[XMPP] auth/connect errorsWrong XMPP passwordCheck XMPP_BRIDGE_PASSWORD matches Prosody config
[Relay] no mappingMessage from an unmapped channelAdd the channel to the mappings list in config

​
Viewing full logs

# Follow logs in real time
docker logs --follow atl-bridge

# Show last 200 lines
docker logs --tail 200 atl-bridge

# Filter for a specific adapter
docker logs atl-bridge 2>&1 | grep "\[IRC\]"

​
Portal integration

The bridge supports an optional Portal identity service for unified user profiles. When Portal is configured, the bridge resolves consistent nicknames across platforms.

​
Checking Portal connectivity

If BRIDGE_PORTAL_BASE_URL and BRIDGE_PORTAL_TOKEN are set, the bridge logs Portal status at startup: 
docker logs atl-bridge 2>&1 | grep -i "portal"
When Portal is not configured, you see: 
XMPP adapter running without Portal (dev mode): using fallback nicks

​
Identity cache

The Portal client caches identity lookups (default: 1024 entries with TTL expiry) to reduce API calls. The cache is in-memory and resets on bridge restart.