Self hosted foundry guide is wrong, outdated or incomplete

Hi,

I'm following this guide line by line:
https://github.com/bekriebel/fvtt-module-avclient-livekit/wiki/Installing-LiveKit-on-an-Existing-Self-Hosted-Foundry-Server
But there is an issue with it.

The assumption is that you have installed foundry using the official guide, that means that your 443 port is already in use by the reverse proxy you configured there.
So when you follow this livekit on existing self-hosted foundry server guide, and you are activating the server in the last step, you get this error `tcp :443: bind: address already in use. livekit-caddy-1 exited with code 1` on every start or reboot of the service.

Here you can see all process trying to listen on 443:
`sudo lsof -i:443`

> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> nginx 961 root 14u IPv6 25349 0t0 TCP *:https (LISTEN)
> nginx 961 root 15u IPv4 25350 0t0 TCP *:https (LISTEN)
> nginx 962 nginx 14u IPv6 25349 0t0 TCP *:https (LISTEN)
> nginx 962 nginx 15u IPv4 25350 0t0 TCP *:https (LISTEN)
> nginx 963 nginx 14u IPv6 25349 0t0 TCP *:https (LISTEN)
> nginx 963 nginx 15u IPv4 25350 0t0 TCP *:https (LISTEN)
> nginx 964 nginx 14u IPv6 25349 0t0 TCP *:https (LISTEN)
> nginx 964 nginx 15u IPv4 25350 0t0 TCP *:https (LISTEN)
> nginx 965 nginx 14u IPv6 25349 0t0 TCP *:https (LISTEN)
> nginx 965 nginx 15u IPv4 25350 0t0 TCP *:https (LISTEN)
> livekit-s 4293 root 19u IPv4 38008 0t0 UDP *:https`

The guide should be updated.
Still, I was trying to change livekit server ports to solve it, but then I discover that the livekit Foundry plugins doesn't accept that.
Is there any way I can have both on the server, and the VTT listening the 443?

Thanks in advance for the help!

Start by reading the Installing LiveKit on an Existing Self-Hosted Foundry Server wiki guide and reproduce the reported failure with `sudo lsof -i:443`. Update the guide to explain coexistence with the existing nginx reverse proxy and the required LiveKit and Foundry plugin configuration. Done means the documented setup avoids the port conflict on startup and reboot.

Written by the indexing model from the issue text.