- Joined
- Oct 4, 2022
- Messages
- 6
- Buyer
- #21
**Fix using Portainer**
1. Install the server and wait for it to stop at the same spot inflating the libssl.
2. Toggle the install of the server to your installed even though it’s not.
2. Open Portainer connect the “agent” to you docker server where the wing is installed, connect tot he server afterwards and locate the container by searching the server id. You will then see the <server id>_installer container.
3. Connect to the console of the container and run <bash /mnt/install/install.sh> go through the prompts and when it gets to the api stuff it will scream at you. Press Y and enter through all of the crap it will spit at you.
4. When you now go look for the same container I’d on Portainer you may have noticed there was two containers with the same id, one saying running and another saying “created”. Delete the created container and check delete non persistent volumes as well, click on the one that has the same <serverid_installer> and remove the “_installer” part and leave the server id.
5. Stop the container and don’t leave the screen, the server may auto start in the panel once you stop the container, stop it in the panel as well. Wait a second and start the container manually from Portainer and then go look at the panel and the api will load fine from here on out.
**this is a work around until the API stuff is fixed this is not a problem with GSH or the egg, it’s ark..**
I will need to spend more time making the steps without Portainer but I think if you installed pterodactyl, Portainer should be an easy install for this fix. Additionally if you run docker, Portainer is a must have.
