Closed tenmar closed 7 months ago
Update: Turns out my network started DNS blocking the playit gg api doman due to a DNS blocker (pi-hole) on the network. Allowlisting the domain(s) fixed the issue immediately.
To be sure: it didn't manifest until yesterday morning, I was running the proxy just fine for at least a week, and I don't have anything setup to automatically add a domain to a blocklist and hadn't updated my blocklists from external sources for some time.
In any case, the issue was on my end. Closing this.
Environment
Install Methods Tried
apt install playit
Expected Behavior Running
playit
will result in tunnel claim/setup process starting so that I can connect agent using accountActual Behavior Running
playit -s
results in the following console output:Other Notes I HAVE BEEN ABLE TO GET A TUNNEL WORKING USING https://www.spigotmc.org/resources/playit-gg.105566/ it is running within a server that is running via pterodactyl wings agent, and it is working flawlessly (minus support for creating tunnels to other ports on the same instance, which seems to be broken, since I always get logs pointing at the port of the minecraft server even if the other tunnels (tcp, tcp+udp) were setup to point at a different port, but that seems to be a limitation of the plugin)
I was previously using this docker image without issue. This morning the tunnel suddenly stopped working. I was able to use the tunnel for both my server and a web page serving the server map on a different port on the same machine.
Is there a reason the linux client doesn't work anymore in either VM or Docker environments, but the minecraft plugin does?