2023-11-11, 12:54 PM
You should really not expose your server to the internet before you complete the install wizard. There's basically no security on that page and it's just asking for your server to get hijacked.
In regards to your docker container, having both "network_mode" and "ports" is conflicting. One of these is doing nothing, probably the ports section. The ports section also doesn't have enough ports listed for the automatic discovery to work, as it requires UDP ports as well.
> "Connection Failure -- We're unable to connect to the selected server right now. Please ensure it is running and try again."
This usually means that the browser has cached information about a server but can't reach it, due to an update or changing address or a handful of other situations. Usually clearing your cookies will fix it.
For any playback issues, you're really going to need to include logs from the server. There's nowhere near enough information here to help.
In regards to your docker container, having both "network_mode" and "ports" is conflicting. One of these is doing nothing, probably the ports section. The ports section also doesn't have enough ports listed for the automatic discovery to work, as it requires UDP ports as well.
> "Connection Failure -- We're unable to connect to the selected server right now. Please ensure it is running and try again."
This usually means that the browser has cached information about a server but can't reach it, due to an update or changing address or a handful of other situations. Usually clearing your cookies will fix it.
For any playback issues, you're really going to need to include logs from the server. There's nowhere near enough information here to help.