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 May 26, 2024. It is now read-only.
Whenever I try and connect to the website, it just says it couldn't connect and such, even though it successfully starts — there are no errors in console and everything seems to be setup correctly. One minor detail tho, this is running inside a Pterodactyl node.js egg. Though, other websites have worked perfectly on it and such, so I know it's possible, as well as the ports work fine with other applications so it likely isn't a firewall issue. I've been going at it for a couple hours and can't figure it out, so please help lol
The text was updated successfully, but these errors were encountered:
Sure, it is the not loading at all, there are some attached images for context. If you would like I can always give you access to the panel
As you can see above, the website isn't loading even though the ports are open (the bot is running on the primary (25565), I can run other things on the ports (I have tried both 1027 and 3000), and I am visiting it with the port added http://ip:Port.
Oh, and I'd like to add that the api backend part isn't done yet, I wanted to make sure I could get the dashboard up before I committed to adding that to my bot
Whenever I try and connect to the website, it just says it couldn't connect and such, even though it successfully starts — there are no errors in console and everything seems to be setup correctly. One minor detail tho, this is running inside a Pterodactyl node.js egg. Though, other websites have worked perfectly on it and such, so I know it's possible, as well as the ports work fine with other applications so it likely isn't a firewall issue. I've been going at it for a couple hours and can't figure it out, so please help lol
The text was updated successfully, but these errors were encountered: