We're back on GitHub, new Heliactyl versions are releasing soon.

All features:

• Resource Management (Use it to create servers, etc)
• Coins (AFK Page earning, Linkvertise earning, Gift them away)
• Renewal (Require coins for renewal)
• Coupons (Gives resources & coins to a user)
• Servers (create, view, edit servers)
• Login Queue (prevent overload)
• User System (auth, regen password, etc)
• Store (buy resources with coins)
• Dashboard (view resources)
• Join for Resources (join discord servers for resources)
• Admin (set/add/remove coins & resources, create/revoke coupons)
• API (for bots & other things)

We cannot force you to keep the "Powered by Heliactyl" in the footer, but please consider keeping it. It helps getting more visibility to the project and so getting better. We won't do technical support for installations without the notice in the footer.

Warning: You need Pterodactyl already set up on a domain for Heliactyl to work

1. Upload the file above onto a Pterodactyl NodeJS server Download the egg from Parkervcp's GitHub Repository
2. Unarchive the file and set the server to use NodeJS 12
3. Configure settings.json (specifically panel domain/apikey and discord auth settings for it to work)
4. Start the server (Ignore the 2 strange errors that might come up)

1. Login to your DNS manager, point the domain you want your dashboard to be hosted on to your VPS IP address. (Example: dashboard.domain.com 192.168.0.1)
2. Run apt install nginx && apt install certbot on the vps
3. Run ufw allow 80 and ufw allow 443 on the vps
4. Run certbot certonly -d <Your Heliactyl Domain> then do 1 and put your email
5. Run nano /etc/nginx/sites-enabled/heliactyl.conf
6. Paste the configuration at the bottom of this and replace with the IP of the pterodactyl server including the port and with the domain you want your dashboard to be hosted on.
7. Run systemctl restart nginx and try open your domain.

server {
    listen 80;
    server_name <domain>;
    return 301 https://$server_name$request_uri;
}
server {
    listen 443 ssl http2;
location /afkwspath {
  proxy_http_version 1.1;
  proxy_set_header Upgrade $http_upgrade;
  proxy_set_header Connection "upgrade";
  proxy_pass "http://localhost:<port>/afkwspath";
}
    
    server_name <domain>;
ssl_certificate /etc/letsencrypt/live/<domain>/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/<domain>/privkey.pem;
    ssl_session_cache shared:SSL:10m;
    ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers  HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers on;
location / {
      proxy_pass http://localhost:<port>/;
      proxy_buffering off;
      proxy_set_header X-Real-IP $remote_addr;
  }
}