Skip to main content

Documentation Index

Fetch the complete documentation index at: https://wiki.daki.cc/llms.txt

Use this file to discover all available pages before exploring further.

This page covers the most common problems users run into on Daki Hosting and how to solve them. If your issue is not listed here, check the FAQ or reach out through the appropriate support channel.

Server Status Issues

Free Tier: Your runtime counter reached zero. Log in to the Free Tier Dashboard at dash.daki.cc and watch ads to add runtime. You have a 2-day grace period after suspension before the server is permanently deleted. See Renewing Your Free Server.Paid plan: Your billing period ended without a successful renewal. Log in to the Billing Panel at billing.daki.cc, add credits or a payment method, and renew your service. You have a 7-day window before the service is permanently cancelled and data deleted. See Billing & Payments.
No. Once a Free Tier server is deleted after the 2-day grace period, or a paid service is cancelled after the 7-day suspension window, all data is permanently removed and cannot be recovered. Always keep an external backup of your code (e.g., on GitHub).
Wait 1–2 minutes and refresh the Portal. If the status does not change, try clicking Kill in the Console tab and then Start again. If the problem persists, ask for help on Discord.

Startup & Runtime Issues

Open the Console tab in the Portal and read the error output. Common causes:
  • Wrong startup command — filename typo or wrong path. Compare the filename in the Startup tab to what appears in the Files tab.
  • Missing entry point file — your code may not have been uploaded yet, or is in a subdirectory. See File Manager.
  • Dependencies not installed — check that the install command is set correctly (e.g., npm install or pip install -r requirements.txt) in the Startup tab and restart. See Startup Settings.
  • Wrong Docker image — your code requires a newer runtime version. Check the image in the Startup tab.
Verify in the Startup tab:
  1. The startup command points to the correct filename (case-sensitive).
  2. The selected Docker image matches your application’s language version.
  3. You restarted the server after making changes.
See Startup Settings.
Go to the Startup tab, pick the correct image from the dropdown, and restart. Changing the Docker image does not delete your files.
Your application is using more RAM than your plan allows. The Console will typically show the process being killed without an error message, or a line like Killed or exit code 137.
  • Free Tier: The limit is 512 MB. Optimise your application’s memory usage or upgrade to a paid plan.
  • Paid plan: Optimise memory usage or upgrade to a higher-tier plan with more RAM. See App & Bot Hosting Plans.
Make sure the install command is set correctly in the Startup tab:
  • Node.js: npm install
  • Python: pip install -r requirements.txt
Restart the server after setting the install command to trigger it.

File Upload Issues

Direct folder upload is not supported in the web file manager. Use one of these workarounds:
  1. Compress your folder into a .zip or .tar.gz, upload the archive, then right-click and select Extract.
  2. Use SFTP to upload the folder directly with no restrictions.
See File Manager.
The web file manager has a per-file upload size limit. For large files, use SFTP. Your SFTP credentials are in the Settings tab. See File Manager.
Check the following:
  • Host and port — verify in the Settings tab of your server in the Portal.
  • Username — use your Portal username exactly as shown.
  • Password — use your Portal account password (not your Discord password or Billing Panel password).
  • Server state — SFTP requires your server to be in a non-suspended state.
See File Manager.

Networking Issues

Free Tier: Free Tier servers do not have publicly accessible ports. External inbound connections are not supported on the Free Tier. You need a paid plan to expose a web server or API publicly. See Network & Allocations.Paid plan: Verify that your application is listening on the port shown in the Network tab of the Portal. Applications listening on any other port will not be reachable from outside.
Discord bots connect outbound to Discord and do not need an open port — they work on both Free Tier and paid plans. HTTP servers need an inbound port, which requires a paid plan. See Network & Allocations.

Login & Account Issues

The Free Tier Dashboard uses Discord OAuth. Make sure you are logged into Discord in your browser (or have the Discord desktop app open). Try clearing your browser cache or using a different browser.If you recently changed your Discord email address, contact support on Discord — your account may need to be re-linked manually.
Use the “Forgot Password” link on the Billing Panel login page at billing.daki.cc. A password reset link will be sent to your registered email address.
Free Tier: Your Portal password is shown in the Credentials tab at dash.daki.cc/credentials.Paid plan: Go to the Password tab on your active service page in the Billing Panel and generate a new Portal password.
There are three separate interfaces:
  • Free Tier Dashboard (dash.daki.cc) — Free Tier account management, login with Discord.
  • Billing Panel (billing.daki.cc) — purchasing plans and billing, own login with email/password.
  • Portal (portal.daki.cc) — managing your actual servers, log in via SSO from the other two panels.
See Portal Overview for a full comparison.

Common Suspension Reasons

ReasonWhat happens
Free Tier runtime counter reached zeroServer suspended; deleted after 2-day grace period
Paid plan billing period expired without renewalServer suspended; deleted after 7-day grace period
Multiple accounts created by one personAll accounts may be suspended
Terms of Service violation / abuseAccount may be permanently suspended
To avoid unintentional issues: watch ads regularly (Free Tier), keep sufficient credits (paid), and follow the Terms of Service.

Still Stuck?

See Getting Help for full details on support channels.