You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2023. It is now read-only.
When running the jarfile in a hosting service that uses ExoticalCat's MultiEgg for Pterodactyl, the server startup fails completely when using the OpenJ9 version of the egg. I assume this may be an issue with running the jar under OpenJ9 overall, though I am unconvinced.
Extra Information
When attempting to run this in a hosting service called FalixNodes.net, the server boots, but downloading installer.sh fails completely, this is possibly caused by the hosting service blocking the download link, if that is the case, the workaround is simple and it involves possibly changing the download link for the file.
The text was updated successfully, but these errors were encountered:
Download the installer.sh file to load from, you can download it manually here, once you have downloaded it, go ahead and and upload it to the files of your server and the Jarfile should load from it instead of trying to download the file from source.
A commit has been pushed to ease the issue of running the Jarfile on FalixNodes, atleast as much as we can, Installer.sh will still fail to download it's dependencies, but that has to be fixed by the original Ptero-VM developers.
What's the Issue?
When running the jarfile in a hosting service that uses ExoticalCat's MultiEgg for Pterodactyl, the server startup fails completely when using the OpenJ9 version of the egg. I assume this may be an issue with running the jar under OpenJ9 overall, though I am unconvinced.
Extra Information
When attempting to run this in a hosting service called FalixNodes.net, the server boots, but downloading
installer.sh
fails completely, this is possibly caused by the hosting service blocking the download link, if that is the case, the workaround is simple and it involves possibly changing the download link for the file.The text was updated successfully, but these errors were encountered: