Pterodactyl cant find server.jar on boot which results in crash

for context im using tailscale to setup my panel vps as an exit node instead of port fowarding my home network

honestly theres like no files when the server is reinstalled so idk, just server.properties

Yeah, that typically indicates the install script failed

the containers wings spins up need internet connectivity for the install script

Nor be to get dependencies

Be able*

Like the Minecraft vanilla jar

That's fair, yeah, for any fresh install, you will always need connectivity

(I've only really ever lossed connectivity after the initial install, so forgor libs)

yeah found that out the hard way

do you know of any documentation on how to cleanly remove wings?

also im using ptero documentation and not the probably backdoored install script on github

nvm did it

@Polish yeah idk whats going on

this was after a reinstall of wings

it was able to download the docker image and such but cannot download the mojang stuff

ive tested connection to google and such and that comes back fine

cant communicate with forge either from my testing

Your wings subnet is probably not going via the tailscale exit gateway

any tips on making it do that?

Policy-based routing with your wings subnet is the way I've done it in the past, but unsure if that's the best way

eh any way is the best way rn

e.g. from 172.16.10.0/24 to 0.0.0.0/0 via tailscale gateway

how would I implement that?

like creating a routing table then ussing ip route to add a route for the wings subnet via tailscale?

then add a policy rule to make the subnet use that table and then also use NAT

You can do it via the ip route command to just verify it's working as expected, depending if you're using netplan, ifupdown, etc. It'll change how you implement it in the long term

would be networkmanager cause fedora

wait no

would be netplan cause node is ubuntu