Help Center

Knowledge Base

Search support guides, infrastructure details, billing policies, and troubleshooting protocols.

  • Verification Hold: Transactions flagged by automated security (MaxMind) due to VPN/proxy usage or billing address discrepancies are placed on hold.
  • Resolution: Open a support ticket on the billing portal (Blesta).
  • Required Identification: Submit a clear photo of an official government ID (DNI, ID Card, or Passport).
  • Privacy Protection: Sensitive personal data may be blurred or redacted. The Full Name, Photo, and Expiry Date must remain legible and match the billing details of the payment method (PayPal or Credit/Debit Card).
  • Timeframe: Refund requests are only eligible within 48 hours from the date of the first purchase. This applies strictly to new clients.
  • Service Requirement: Refunds are only granted if there is a verified service or network outage exceeding 24 consecutive hours.
  • Exclusions: No refunds are issued for client-side configuration errors, resource exhaustion due to excessive mods/plugins, in-game bans, or AUP suspensions. All sales are final after 48 hours.
  • Due Date (Suspension): Unpaid invoices on the due date trigger immediate server suspension and container shutdown.
  • Day 7 (Termination): After 7 consecutive days of non-payment, the server container, databases, and backup storage are permanently deleted.
  • Data Recovery: Files deleted due to non-payment cannot be recovered. Endurance Nodes does not retain backups of terminated services.
  • Uptime Target: We guarantee a 99% hardware and network uptime per billing month.
  • Compensation Tiers:
    • 98.0% to 98.99% uptime: 1 day of service credit.
    • Below 98.0% uptime: 3 days of service credit, plus 1 additional day for every 12 hours of verified downtime (capped at 30 days total).
  • Policy: Compensation is applied strictly as service time credits on the next billing cycle. Cash refunds are not issued for SLA breaches.
  • How to Claim: Open a billing support ticket within 7 days of the incident with the Server ID and outage logs.
  • Authorized Client: Technical support and account management services are provided exclusively to the registered billing account holder.
  • Third-Party Requests: Tickets opened by developers, moderators, or sub-administrators on behalf of the owner will not be processed.
  • Resolution: The billing account owner must submit the ticket directly or add the user as an authorized contact with specific access permissions within the Blesta billing portal.
  • Ticket Queue: All support inquiries are processed chronologically. Submitting follow-up messages or spamming to elevate priority resets the ticket position to the end of the queue.
  • Duplicates: Opening multiple tickets for the same issue is prohibited. Duplicates will be closed immediately.
  • Conduct: Offensive language, insults, or abusive behavior toward support staff will result in the suspension of ticketing permissions and potential service termination.
  • Webhook Synchronization: While credit card or PayPal payments are authorized instantly, the payment gateway webhooks (IPN) can take 2 to 5 minutes to sync with the Blesta billing engine.
  • Activation: The API instantiates the server container only after invoice validation is recorded.
  • Protocol: Allow 5 minutes for setup emails containing server credentials to arrive before submitting a billing ticket.
  • No Swap Space: To maximize Ryzen 7 9700X hardware performance and disk I/O rates, swap memory is disabled on our nodes.
  • Out of Memory (OOM): If a server exceeds its allocated RAM limit, the system kernel terminates the container instantly, displaying a 'Killed' or 'OOM' status in the console.
  • Troubleshooting: Check logs for memory leaks, optimize plugin configurations, disable unused/heavy mods, and prune unnecessary entities.
  • Java Selection: Java 8, 11, 17, and 21 are available in the Settings tab of the Pterodactyl panel to match different server software requirements.
  • Startup Flags: Performance flags (such as Aikar's Flags or modern GCs like G1GC and ZGC) can be edited via startup variables in the panel.
  • Memory Restrictions: Min/Max memory flags (-Xms and -Xmx) are dynamically locked to the plan's allocation to ensure container stability.
  • Default Ports: Every server includes 1 primary game port and 2 additional ports for plugins (e.g. GeyserMC, Dynmap, BlueMap, or Votifier).
  • Additional Ports: Extra ports beyond the included allocations can be requested via support ticket for $0.30 USD per port per month.
  • Supported Areas: We support physical node hardware, power, network connectivity, DDoS filtering, and panel accessibility.
  • Unsupported Areas (Client Managed): Configuration of game files, plugin or mod debugging, error logs analysis, MySQL database content management, and player administration.
  • Professional Setups: Advanced optimization or configuration tasks may be referred to our partner studio, EndStudios.
  • Database Limits: Each MySQL database is limited to 500 MB of storage space and 150 concurrent connections.
  • Usage Policies: Databases must only be used for game-related plugins. Connecting high-traffic external applications (such as public web forums) is prohibited.
  • Optimization: Logging plugins (like CoreProtect) must be configured to purge database records regularly to prevent exceeding the 500 MB storage quota.
  • Eligibility: Advanced plans (Atenea and higher) support resource splitting, allowing users to partition CPU and RAM into multiple independent servers.
  • Technical Support: Setting up proxy networks (such as Velocity or BungeeCord), syncing databases, and configuring port routing are entirely client-managed.
  • Engine Constraint: Minecraft runs its core game loop (physics, entities, redstone) on a single CPU thread. Even if your plan has 3 vCores (300% max in panel), a saturated main thread shows as only ~33% usage.
  • Performance: Our Ryzen 7 9700X processors offer top-tier single-core speeds, but poorly optimized plugins or excessive entities will still saturate the single main thread.
  • Resolution: Run a /spark profiler report to identify the exact plugins or coordinates causing tick delays. Do not use panel overall usage as a gauge for server resource limits.
  • Security Policy: Standard FTP (port 21) and system SSH (port 22) are blocked at the firewall level to secure the node hypervisor.
  • Port: External SFTP connections must be routed through Pterodactyl's secure container SFTP daemon port, which is 2022.
  • Credentials: Connect using the host, username, and port listed under the 'SFTP Details' tab of the panel. The password is identical to your panel login password.
  • Limitations: Vanilla Mojang or raw Forge software does not support async chunk loading, thread optimization, or network compression. This causes performance drops even with low player counts.
  • Recommendation: Migrating to optimized server software such as Paper, Purpur, or Pufferfish is required for public multiplayer environments.
  • Support Policy: Performance complaints regarding servers running unoptimized Vanilla or unpatched Forge engines will not be processed.
  • Remote Storage: Premium backups are saved to external S3 arrays (HDD RAID-Z2) to ensure maximum data survival.
  • Duration: Restoring large servers (e.g. over 10 GB) requires pulling compressed data across the local network and unzipping it onto the node NVMe. This process can take 10-30 minutes.
  • Caution: Do not cancel the process or restart the container while a restore is active, as this leads to permanent database and file corruption.
  • Mechanism: The Pterodactyl daemon (Wings) runs cron tasks every 5 to 10 minutes to compute directory sizes. Real-time scanning is disabled to preserve CPU I/O cycles.
  • Delay: After deleting large files via SFTP or the File Manager, the panel disk quota may take up to 10 minutes to reflect the newly freed storage space.
  • Action: Wait for the automated cycle to refresh the quota limits before restarting the container.
  • Syntax Rules: You cannot log in to SFTP using your billing email or regular web panel username.
  • Format: Pterodactyl generates a specific SFTP username using your account name and the unique server container ID, separated by a dot (e.g., admin.a8f3b2c1).
  • Details: Locate the exact string in the 'SFTP Details' tab of your server panel and use it as the login username.
  • Database Lock: SQLite writes data to a single flat file (.db). When multiple game threads write data concurrently (e.g. from block logging or economic plugins), the operating system locks the file. This blocks the main game thread, dropping TPS.
  • Resolution: Plugins processing high volumes of transactions (such as LuckPerms or CoreProtect) must be configured to use a MySQL engine.
  • Support Policy: Free MySQL databases are provided with all server plans. Tickets reporting lag caused by local SQLite locks will be closed.
  • Mitigation: Network traffic is routed through Path.net L4/L7 DDoS mitigation layers, optimized specifically for game protocols.
  • Null-Route Policy: Volumetric attacks that exceed standard mitigation limits and threaten node-wide stability trigger a temporary IP null-route (blackhole).
  • SLA Exclusions: Preventive null-routing is a security policy and is excluded from SLA downtime compensation calculations.
  • Prohibited Activities: Port scanning, hosting botnets, malware distribution, cryptocurrency mining, and sending spam emails (outbound Port 25 is blocked).
  • IP Blacklisting: Actions causing node IP addresses to be blacklisted (e.g. by Mojang or Spamhaus) lead to permanent account termination without refund and liability for damages.
  • Security Vulnerability: Disabling Mojang authentication (online-mode=false) allows players to connect with custom client usernames. This enables unauthorized admin account spoofing.
  • Protection Requirement: An authentication plugin (e.g., AuthMe Reloaded) must be installed and configured immediately when running in offline mode.
  • Liability: Endurance Nodes is not responsible for griefed worlds, stolen accounts, or command abuse on offline-mode servers.
  • Security Threat: Plugins downloaded from unofficial forums or 'nulled' repositories frequently contain malicious code (backdoors, force-OP exploits, or disk-wiping scripts).
  • Policy: Under ToS Article 19, clients assume full responsibility for software security. Ticketing services will not clean infected servers or recover compromised files.
  • Suspension: Instances running malware that degrades node-wide resource availability will be suspended immediately.
  • Vulnerability: If a proxy network (BungeeCord/Velocity) is created, leaving backend servers (Lobby, Survival, etc.) exposed on public ports allows players to join backend instances directly, bypass registration, and spoof admin usernames.
  • Resolution: Enable and configure IP forwarding (ip-forwarding: true in BungeeCord, or modern forwarding in Velocity) and set online-mode=true on backend servers linked to the proxy.
  • Policy: Securing proxy networking configurations is a client-side responsibility (DIY policy). Support does not perform audits or setup network firewalling for clients.
  • The Risk: Automated bots scan public ports looking for active RCON ports. Using weak or default credentials (e.g. 12345) allows bots to log in and execute console commands (such as deleting files).
  • Requirement: RCON must be configured with a strong, random alphanumeric password of at least 16 characters.
  • Disclaimer: Endurance Nodes does not assume liability for command injection, griefing, or data loss caused by insecure RCON configurations.
  • Protocol Mismatch: Cloudflare's free proxy (Orange Cloud) only supports Layer 7 HTTP/HTTPS traffic. Minecraft connections run on Layer 4 TCP/UDP protocols, which are blocked by the proxy.
  • Resolution: Set Cloudflare DNS records for the game server domain to DNS Only (Grey Cloud). Use an SRV record to map custom ports.
  • Port Conflict: Shared docker nodes do not permit multiple servers to bind to the default Bedrock port (19132 UDP).
  • Setup: Allocate a secondary port in the panel, and configure GeyserMC's config.yml to listen on that port with the protocol set to UDP. Bedrock players must specify this custom port to connect.
  • Upload Limit: The browser-based file manager has a maximum file upload limit of 1024 MB to maintain panel stability.
  • Resolution: Files larger than 1GB (such as maps or large modpacks) must be uploaded via an external SFTP client (e.g. FileZilla or WinSCP) using the SFTP credentials found in the panel settings.
  • EULA Blacklist: Violating Mojang's commercial EULA rules (e.g., selling pay-to-win perks) can lead to Mojang blacklisting the server IP, blocking connections for the entire node.
  • Policy: Servers blacklisted by Mojang for EULA violations are suspended immediately without refund. The account holder is liable for any damages to other clients sharing that IP address.
  • Shared IP Address: Multiple game servers are hosted on a single node IP. Only one server can bind to the default port (25565).
  • Connection Format: Servers assigned a custom 5-digit port must be connected to using the full IP:PORT format (e.g. bhs01.endurancenodes.com:25582).
  • Hiding Ports: Domain SRV records can be configured to mask the custom port, or a Dedicated IP can be purchased if available.
  • Inodes Definition: Disk storage usage is capped by both file size (GB) and the maximum number of individual files (inodes). Minecraft servers generate numerous files via regions, logs, and player cache.
  • The Error: Reaching the inode limit triggers a 'No space left on device' error even if storage space (GB) remains available.
  • Resolution: Delete older logs inside the /logs folder, remove crash reports, and optimize plugin data directories.
  • Firewall Restriction: Port 3306 is closed to external connections. External database access (e.g., from desktop clients or external websites) is blocked.
  • Configuration: Plugin database configurations must use the local host address displayed on the panel's Databases tab (typically 127.0.0.1 or the container bridge IP) rather than the node's public IP.
  • Node Timezone: The BHS-01 node operates on Eastern Time (EST/EDT) or UTC.
  • Configuration: Tasks configured in the panel Schedules tab execute based on the node's timezone. You must calculate the offset difference from your local time before scheduling automated events.
  • Compatibility Issue: Minecraft worlds are not backward compatible. Running a map generated in a newer version on an older server core (e.g. downgrading from 1.21 to 1.12.2) corrupts region chunks, leading to infinite boot crash loops and high CPU usage.
  • Resolution: When downgrading server software versions, the old world data and configurations must be wiped. Create a backup first, delete root files, then change the core version and use the **Reinstall** button to reset files.
  • Permitted Files: Disk storage is allocated exclusively for active game files. Storing personal data, non-server files, or hoarding archives is prohibited.
  • Backup Management: Keeping large volumes of uncompressed backups on the active disk reduces NVMe I/O performance. Backups should be downloaded locally and deleted from the server disk.
  • Diagnostics Requirement: Before submitting a ticket regarding network lag, packet loss, or high ping, users must run a traceroute test using WinMTR (Windows) or mtr (Linux) towards bhs01.endurancenodes.com with at least 100 packets sent.
  • Analysis: If packet loss or latency spikes occur in the initial hops (user's local router or ISP transit networks), the issue is external. Support tickets with external routing faults will be closed.
  • Verification: Attach the diagnostic MTR log or screenshot to any network-related support inquiry.
  • Monitoring: Nodes are monitored 24/7. Verified infrastructure outages are immediately reported on the official Discord channel (#service-status).
  • Wait Period: Clients must wait 5 minutes before opening a support ticket during a connection loss. This allows automated DDoS mitigation (Path.net) or scheduled restarts to complete.
  • Policy: Tickets opened immediately for brief connection drops under 5 minutes will be closed automatically as resolved.
  • The Cause: This error occurs when the server-ip or server-port values in server-properties are modified manually. The container tries to bind to an unauthorized port or IP, causing Linux to block it for safety.
  • Wings Automation: The Pterodactyl daemon (Wings) automatically binds correct ports dynamically on launch.
  • The Fix: Leave the server-ip line completely blank and reset the server-port to your assigned primary port, or use the **Reinstall** button in the administration panel to reset default settings.
  • The Limit: The browser-based file manager enforces an Nginx/PHP-FPM script execution timeout. Extracting compressed files larger than 500 MB often hits this limit, freezing the progress bar or corrupting data.
  • Resolution: For files larger than 500 MB, extract the archive locally on your computer and upload the extracted files directly via an external SFTP client.
  • Risk: Clicking the red **Kill** button abruptly cuts power to the container. If Java threads are writing region chunk data to the NVMe disk, this causes Chunk NIO read/write errors.
  • Best Practice: Always use the standard orange **Stop** command. Only use **Kill** as a last resort if the server console fails to respond for more than 60 seconds.
  • Disclaimer: Corrupted world region files (.mca) resulting from forced shutdowns are the administrator's responsibility. Support does not repair region files.
  • WebSocket Link: The console window uses real-time WebSockets to show console output.
  • Disconnection: Browser tab inactivity, local network drops, or expired session keys will cause the console to show Connecting to daemon... or Connection lost.
  • Status: This only affects the browser session; the game server container remains active. Reload the browser window (F5) to restore the console view.
  • The Error: java.io.IOException: An existing connection was forcibly closed... is caused by saturation in the Java Netty network thread.
  • Triggers: High-bandwidth packets generated by unoptimized scoreboards, massive holograms, custom skin restoration loops, or client-side cheat spam.
  • Policy: These network disconnects originate from in-game application packet limits, not the edge firewall. Debug and optimize network plugins to resolve.
  • Mechanism: Tebex and Buycraft plugins do not receive instant pushes. They poll the store's API at set intervals (usually every 15 minutes) to download purchases.
  • Wait Time: Allow up to 20 minutes for automated store deliveries to run.
  • Force Update: Run the command /tebex force (or equivalent plugin sync command) inside the server console to trigger instant package delivery.
  • The Concept: Plugins like ViaVersion translate network packet formats on the fly to let newer client versions connect to older server jar files (e.g. client 1.21 connecting to server 1.8.8).
  • Anomalies: This can cause visual glitches, incorrect hitboxes, disappearing blocks, or false flags on your anti-cheat plugin.
  • Analysis: These glitches are software translation errors, not network latency or server-side lag. They must be resolved by adjusting compatibility configurations.
  • The Cause: If a plugin prints thousands of stacktrace errors per second, Pterodactyl's WebSocket streams this massive volume of text directly to your browser. This overloads the browser's Javascript rendering engine and freezes your tab or PC.
  • Resolution: Access the server files via SFTP, navigate to the /logs directory, and inspect latest.log in a text editor to locate and remove the misbehaving plugin. Do not open the console page while the loop is active.

Still need Assistance?

Can't find the answer you are looking for? Reach out to our technical support team directly or join our community Discord.

Contact our Team Join our Discord