FPP Connect cannot reach this device directly: it requires an HTTP connection, and xLights
builds every discovery URL on port 80, which an unprivileged Android process cannot bind.
A proxy entry on the player should work. FPP writes a rewrite rule per proxied host that explicitly
accepts a port:
RewriteRule ^<host>:([0-9]*)/(.*)$ http://<host>:$1/$2 [P,L]
so adding <device>:8080 as a Proxied Host should make the device reachable at
http://<player>/proxy/<device>:8080/....
The pieces are in place and verified as responding: GET / carries the literal Falcon Player - FPP
that the discovery path tests for, /api/system/info includes the mandatory uuid (without it the
whole exchange is abandoned), /api/channel/output/channelOutputsJSON reports a VirtualMatrix
output, and /api/proxies answers.
Not proven: no upload has actually been pushed through a proxy end to end.
FPP Connect cannot reach this device directly: it requires an HTTP connection, and xLights
builds every discovery URL on port 80, which an unprivileged Android process cannot bind.
A proxy entry on the player should work. FPP writes a rewrite rule per proxied host that explicitly
accepts a port:
so adding
<device>:8080as a Proxied Host should make the device reachable athttp://<player>/proxy/<device>:8080/....The pieces are in place and verified as responding:
GET /carries the literalFalcon Player - FPPthat the discovery path tests for,
/api/system/infoincludes the mandatoryuuid(without it thewhole exchange is abandoned),
/api/channel/output/channelOutputsJSONreports aVirtualMatrixoutput, and
/api/proxiesanswers.Not proven: no upload has actually been pushed through a proxy end to end.