Sharing an X11 Server Across Hosts with FamilyWild
This technical guide explains how to resolve X11 authorization errors when running applications across different hosts or containers. It introduces the use of the FamilyWild wildcard to bypass hostname-specific cookie restrictions.
Why it matters
It provides a practical solution for developers and system administrators struggling with Linux display server permissions.
Ever tried running an X11 application from inside a container, a chroot, or over ssh with a bind-mounted .Xauthority — only to be greeted by the ever-helpful Authorization required, but no authorization protocol specified ?
The file is right there, mounted read-only where the client expects it, and yet X refuses the connection. The reason is subtle, and the fix is a single line of sed .
An .Xauthority file is a list of cookies, and every entry is keyed by a family and a hostname . When a client connects, it doesn't just grab the first cookie it finds — it looks for the entry whose hostname matches the machine the client believes it's running on.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in