DarkWorld-Wiki - Recent changes [en]

DWShells:IPv6 and DNS

Fizi — Mon, 05 Oct 2026 20:24:35 GMT

Fizi protected DWShells:IPv6 and DNS [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''IPv6, DNS and assigned application ports'''

Understand which address and port belongs to SSH, your website and your IRC applications.

'''Last verified:''' 6 October 2026. This page covers the connection policy and basic panel workflow. Follow the current fields and validation shown in the panel for hostname changes.

[[DWShells:Documentation|← Documentation hub]]

== Three different connections ==
{| class="wikitable"
!Connection
!Where to get its settings
|-
|SSH / SFTP
|Shell Access and shell connection details; shared login host <code>shells.darkworld.network</code>
|-
|Personal website
|The selected shell's personal HTTPS link
|-
|ZNC / Eggdrop listener
|Packages, for the selected app instance; use its assigned listener port and TLS details
|}
A hostname can point to the same server while a port selects a different service. Do not enter an application's port in your SSH settings or use the network's IRC server port as your ZNC listener port.

== Inbound versus outbound ==
{| class="wikitable"
!Direction
!Meaning
!Policy
|-
|Client → application
|Your IRC client connects to your shell's ZNC listener
|Use assigned addresses/port. IPv4 requires confirmed forwarding.
|-
|Application → IRC network
|ZNC, Eggdrop or an IRC client connects outward
|Free uses IPv6 for IRC. Other permitted plans prefer assigned IPv6 with allowed IPv4 fallback.
|}
Inbound IPv4 forwarding does not grant a Free shell outbound IPv4 IRC access. Use only your assigned bind addresses and ports. Do not create tunnels or proxies to evade restrictions.

== Inspect IPv6 and DNS ==

# Select the correct shell in the customer panel.
# Open '''IPv6 / DNS''' and read the current addresses, hostname information and status.
# Use '''Refresh DNS status''' to read current records and pending operations.
# If the portal offers an extra managed hostname, select an assigned IPv6 address and supply the allowed hostname label.
# Review the result and any queued or running operation; wait for its completion before expecting the hostname to work.

Do not copy an address from another user's guide or account. Field availability and hostname validation depend on the current panel and your allocation.

== DNS records and certificates ==
An A record maps a hostname to an IPv4 address; an AAAA record maps it to an IPv6 address. Reverse DNS is a separate mapping from an address back to a name. None of these records alone grants an application port, confirms forwarding or issues a valid TLS certificate for an arbitrary hostname.

Use the hostname and certificate information displayed by the application manager. If the name does not match the certificate, ask staff to review it rather than disabling verification. A DNS change may not immediately replace records cached by your device or resolver.

== Troubleshooting ==
{| class="wikitable"
!Symptom
!Check
|-
|Website works, ZNC fails
|The ZNC process, allocated listener port, TLS and forwarding status; these are separate from HTTPS hosting.
|-
|ZNC works via IPv6, IPv4 fails
|Confirm the manager explicitly reports IPv4 forwarding for that listener. Report the port and error to staff without credentials.
|-
|ZNC accepts a client but its network is offline
|Check outbound network/server/port/TLS and IPv6 support on Free.
|-
|New hostname is unavailable
|Check job status and DNS records; verify it points to your assignment and account for cached records.
|-
|IRC network is blocked
|Request staff review of the network; do not bypass approved-destination rules.
|}

== References ==

* [[DWShells:Signup and Rules|Signup and Rules]]
* [[DWShells:ZNC|ZNC guide]]
* [[DWShells:Eggdrop|Eggdrop guide]]
* [https://panel.shells.darkworld.network/customer/ Customer panel]

DWShells:IPv6 and DNS

Fizi — Mon, 05 Oct 2026 20:24:25 GMT

Created page with "'''IPv6, DNS and assigned application ports''' Understand which address and port belongs to SSH, your website and your IRC applications. '''Last verified:''' 6 October 2026. This page covers the connection policy and basic panel workflow. Follow the current fields and validation shown in the panel for hostname changes. ← Documentation hub == Three different connections == {| class="wikitable" !Con..."

New page

DWShells:Security and Backups

Fizi — Mon, 05 Oct 2026 20:24:00 GMT

Fizi protected DWShells:Security and Backups [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Protect your account and important files'''

Use dashboard 2FA, public SSH keys and realistic backup expectations.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/security-and-backups/ Visual website guide]

== Protect access and recovery ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Dashboard
|Enable 2FA and save recovery codes.
|-
|02 · Shell
|Manage authorised public SSH keys.
|-
|03 · Files
|Keep independent copies and inspect backup coverage.
|}

== Dashboard two-factor authentication ==

# '''Open Security Centre.''' Select the shell if required and enter the current dashboard password for sensitive actions.
# '''Start authenticator setup.''' Follow the setup controls, scan the QR code with your authenticator and enter a current code to enable 2FA. Do not share the QR code or setup secret.
# '''Save recovery codes.''' Store them somewhere secure outside this shell. Replacing recovery codes invalidates the older set; security changes can sign out other sessions.

== Public SSH keys ==
Generate and protect a key pair on your own device. In Security Centre, add only the public SSH key and a useful label; confirm using your dashboard password. The matching private key stays on your device. Removing a key prevents future key logins but does not close an already open SSH session. Keep a working recovery method before removing your only key.

== What the panel backups cover ==
'''Before you continue:''' Current panel home-directory copies are stored on the shell server, with three recent copies retained. Off-server protection is not verified in the customer interface. These copies do not protect against loss of the server.

== Request file recovery ==

# '''Inspect the available copies.''' Open Backups & Restore. Read the backup time, integrity/coverage details and any stale status or warnings.
# '''Choose the copy and explain the need.''' Submit a recovery request with the affected paths and the problem. Approval is a review decision, not an immediate restore.
# '''Wait for actual recovery.''' Staff stage and inspect an approved copy and arrange manual recovery. Check the request status and completion notes; do not assume approved means your files have been restored.

== Keep your own backup ==
Download important files using SFTP and retain a separate copy outside the VPS. Copy website sources and app configurations before editing or fresh installation. A home copy may omit sockets or unreadable files and can include changing files; it does not promise an application-consistent database or live-session restore.

== If you suspect compromise ==
Contact staff promptly with your username, approximate time and the issue. Never send passwords, private keys, recovery codes or verification links. Review public keys and running applications, and follow staff advice on resetting credentials and ending sessions.

== You are protected when ==

* 2FA is enabled and recovery codes are stored independently.
* You recognise all authorised SSH keys.
* Important files have a separate off-server copy.
* You understand the coverage of a backup before requesting recovery.

== Backup request states ==
{| class="wikitable"
!State
!Meaning
|-
|Submitted
|Staff review is pending
|-
|Approved
|Awaiting manual recovery; files have not necessarily been restored
|-
|Completed
|Staff have reported manual recovery; read the completion notes and verify the files
|}
When requesting recovery, give the relevant paths, the approximate time the problem occurred, which copy you need and whether current files should be preserved. Staff must inspect and coordinate the recovery.

== Independent backup checklist ==

* Keep an off-server copy of website sources and essential application configuration.
* Store credentials securely; do not publish backup archives in <code>public_html</code>.
* Check that your copy contains the files you need and can be opened.
* Use application-specific export methods for databases where permitted; a changing home-directory copy does not guarantee a consistent database restore.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Security and Backups

Fizi — Mon, 05 Oct 2026 20:23:52 GMT

Created page with "'''Protect your account and important files''' Use dashboard 2FA, public SSH keys and realistic backup expectations. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/security-and-backups/ Visual webs..."

New page

DWShells:Python and Tmux

Fizi — Mon, 05 Oct 2026 20:23:33 GMT

Fizi protected DWShells:Python and Tmux [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Run Python and persistent sessions'''

Use approved Python environments and reconnect to portal-managed tmux sessions.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/python-and-sessions/ Visual website guide]

== Two ways to manage work ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Python app
|Environment → uploaded script → managed Run script.
|-
|02 · Persistent terminal
|Session → attach in Shell Access → detach and return.
|}

== Check your plan ==
'''Before you continue:''' Python and development permissions vary by plan. Use only approved workloads. All programs share the shell’s resource limits. A persistent session does not override Keep, account expiry, process limits or service restarts.

== A Python environment ==

# '''Create an environment.''' Open Python in Packages, choose an environment name and use Create environment.
# '''Upload a script.''' Select a UTF-8 .py file. The current portal upload limit is 64 KiB. Use Upload script, then select the uploaded script or its returned path.
# '''Install required dependencies.''' Enter the packages your script actually needs and use Install dependencies. Inspect the result before running the script.
# '''Run and inspect.''' Select the correct environment and script path relative to your home, then use Run script. Check View logs. Stop an unused application before changing or deleting its environment.

== A simple first script ==
Save as hello.py locally, upload it and use it to check that your environment works:<pre>
print("Hello from my DWShells Python environment")
</pre>This script prints one line and exits normally. A finished process is expected, not a failed always-on app. Deleting an unused environment keeps uploaded scripts, but you should still save independent copies.

== Persistent terminal work ==

# '''Create a session.''' In the appropriate Packages session manager, choose a session name and use Create session. Available IRC clients are shown by the panel.
# '''Attach in Shell Access.''' Use Copy attach command and run the exact command in your browser terminal or SSH connection. Portal-managed sessions use a dedicated tmux socket.
# '''Detach and return.''' Press Ctrl+B, release, then D to detach from tmux. Reconnect later and run the same attach command. Closing the session is different from detaching and terminates that session’s work.

== Example attach command ==
For a portal-managed session named ircsession:<pre>
tmux -S ~/.dwshell-tmux.sock attach -t ircsession
</pre>Use the name and command copied from your panel. A plain tmux attach can look for a different socket and miss the portal-managed session.

== Troubleshooting ==
{| class="wikitable"
!What you see
!What to do
|-
|Python is unavailable
|Check your plan and ask staff if your intended work needs additional permission.
|-
|Module not found
|Install the dependency in the selected environment and inspect its installation output.
|-
|Script exits immediately
|Read logs. A short script may have completed normally.
|-
|No tmux session found
|Check selected shell, session name and the dedicated socket in the copied command.
|}

== Environment, script and process ==
{| class="wikitable"
!Item
!Meaning
|-
|Environment
|The selected Python environment and its installed dependencies
|-
|Script
|A uploaded source file; choose its path relative to your home
|-
|Process
|The currently running invocation; a short script can exit normally
|}
Choose the same environment for dependency installation and script execution. Avoid pasting secrets into script source that you intend to share.

== Detach, exit and close ==
'''Detach''' leaves the tmux session available for reattachment. '''Exit''' ends the program or shell you are using. '''Close session''' terminates that managed session's work. Persistent sessions still depend on account status, Keep, resource limits and host availability; they are not an uptime guarantee.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Python and Tmux

Fizi — Mon, 05 Oct 2026 20:23:20 GMT

Created page with "'''Run Python and persistent sessions''' Use approved Python environments and reconnect to portal-managed tmux sessions. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/python-and-sessions/ Visual websit..."

New page

DWShells:Keep Renewal

Fizi — Mon, 05 Oct 2026 20:23:00 GMT

Fizi protected DWShells:Keep Renewal [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Keep your Free shell renewed'''

Read your countdown, renew before the deadline and understand the daily allowance.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/keep-renewal/ Visual website guide]

== The renewal check ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Select shell
|Each linked shell has its own status.
|-
|02 · Read countdown
|Check deadline, eligibility and allowance.
|-
|03 · Keep
|Complete renewal before expiry.
|-
|04 · Verify
|Confirm the deadline changed successfully.
|}

== What Keep does ==
Keep is enabled by default for Free shells. It is a dashboard renewal action, not a measurement of how long SSH or a bot has been connected. Leaving an application running does not replace renewal.

== Renew through the panel ==

# '''Open Keep / Renewal.''' Select the Free shell and open its Keep / Renewal page. Read the status, expiration date and remaining allowance.
# '''Use the available Keep action.''' Renew before the deadline. Wait for the response instead of repeatedly clicking.
# '''Check the new deadline.''' A normal successful Keep provides at least 14 days from renewal. Repeated Keeps do not accumulate unlimited time; a later staff-approved deadline is preserved.

== Daily allowance ==
At most two successful user Keeps are allowed per shell per UTC day. The allowance resets at midnight UTC—5:00 a.m. in Pakistan. Use the actual deadline in the dashboard; do not calculate eligibility from your local calendar alone.

== Disabled, expired or paused ==
{| class="wikitable"
!What you see
!What to do
|-
|Keep is off on another plan
|This is the default for non-Free plans. Paid renewal remains separate.
|-
|Keep enabled on a paid plan
|It records activity and does not extend the paid subscription.
|-
|No allowance left today
|Wait for the next UTC day if the deadline permits. Contact staff if renewal is urgent.
|-
|Expired, locked or suspended
|Ask staff to review the account. Keep does not bypass suspension.
|-
|Travel or illness
|Contact staff before expiry to request an extension or timer pause. These need staff review.
|}

== A useful routine ==

* Check the selected shell’s deadline after signing in.
* Set your own reminder ahead of that deadline.
* Verify a successful Keep rather than relying on the click alone.
* Read Inbox and service notices for account changes.

== How to read the deadline ==
Use the expiration date and remaining time displayed for the selected shell. Browser display dates can be localised, while the daily allowance resets according to UTC. If the page shows a paused timer or a staff extension, follow that state rather than adding days yourself.

== Keep is not a subscription payment ==
Keep renews eligible Free access. On other plans, where staff has enabled it, Keep records activity only and does not move the paid subscription deadline. If renewal is urgent and the normal action is unavailable, contact staff before the displayed deadline.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Keep Renewal

Fizi — Mon, 05 Oct 2026 20:22:51 GMT

Created page with "'''Keep your Free shell renewed''' Read your countdown, renew before the deadline and understand the daily allowance. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/keep-renewal/ Visual website guide] ==..."

New page

DWShells:Eggdrop

Fizi — Mon, 05 Oct 2026 20:22:27 GMT

Fizi protected DWShells:Eggdrop [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Create and manage an Eggdrop bot'''

Create an instance, edit its own configuration and keep other bots running during changes.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/eggdrop/ Visual website guide]

== One bot, one configuration ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Packages
|Create or choose a named instance.
|-
|02 · File Manager
|Edit that instance’s configuration and scripts.
|-
|03 · Restart + logs
|Apply settings and verify the bot’s connection.
|}

== Before creating a bot ==
'''Before you continue:''' Eggdrop must be allowed by your plan, and you need a free assigned listener port plus available app and IRC connection capacity. Obtain permission to operate the bot on your chosen network and channel.

== Create your first instance ==

# '''Open Eggdrop in Packages.''' Select the correct shell and expand Create a new Eggdrop instance. Choose a unique instance name, such as mybot. It is separate from the IRC nickname.
# '''Fill the bot settings.''' Enter the IRC nickname, owner handle, a separate owner password of at least 14 characters and its confirmation. The current owner-handle field allows up to nine characters.
# '''Choose server and channels.''' Use a permitted IRC server and its server port; keep TLS enabled when the server supports the chosen TLS port. Channels are entered as names such as #DWShells #MyChannel. Join only channels where your bot is welcome.
# '''Set up and start bot.''' The portal selects an available allocated listener port, excluding existing ZNC and bot reservations. Read the result, confirm the running state and open View logs.

== Edit one bot safely ==

# '''Choose the instance card.''' Use Edit configuration or Files and scripts on the bot you intend to change. Do not edit a similarly named bot by mistake.
# '''Save a copy and edit.''' File Manager lets you choose Eggdrop · INSTANCE. Save a local copy before modifying eggdrop.conf or scripts. SFTP locations are under ~/apps/eggdrop/instances/.
# '''Restart that instance.''' Save the text, then return to Packages and Restart the same bot to apply configuration changes. Other instances have their own controls.
# '''Check the result.''' Inspect View logs and the bot’s presence on IRC. A running process alone does not prove that it joined the correct network or channel.

== Learn from the installed reference ==
Full reference opens the configuration reference for that instance. Use it to understand settings rather than pasting an unrelated configuration with another account’s bind address, ports or owner credentials. The owner listener uses TLS; follow the displayed port and certificate fingerprint when connecting.

== Fresh install and deletion ==
Stop the instance and copy anything you want to keep. Install fresh or Delete bot permanently removes that instance’s configuration, credentials, logs and scripts after the typed confirmation. Fresh install opens new setup. Other instances are preserved, but choosing the wrong name still destroys the selected bot.

== Troubleshooting ==
{| class="wikitable"
!What you see
!What to do
|-
|Bot is stopped after setup
|Read the action result and logs; check configuration syntax and permissions.
|-
|Bot runs but is not on IRC
|Check server, TLS, nickname conflicts, network access and IPv6 on Free.
|-
|Cannot create another bot
|Check allowed instance count, assigned port reservations and resource limits.
|-
|Changes have no effect
|Save the correct instance’s file and restart that instance.
|}

== Instance name, nickname and owner handle ==
{| class="wikitable"
!Name
!Purpose
|-
|Instance name
|Identifies the bot's directory and panel controls, for example <code>mybot</code>
|-
|IRC nickname
|Name other IRC users see on the network
|-
|Owner handle
|Eggdrop's owner identity; follow the current field limit
|}
Changing one name does not necessarily change the other two.

== Add a script carefully ==

# Read the script's documentation and confirm that its commands and resource use fit your plan and network rules.
# Copy the selected instance's configuration and scripts to your own computer.
# Open '''Files and scripts''' for that instance, or use SFTP into its instance directory.
# Upload the script and edit the configuration according to the installed reference and the script's documented loading instructions.
# Save and restart that instance, then inspect '''View logs'''.

Do not source untrusted scripts or copy another user's passwords, bind addresses or allocated ports. A syntax error can prevent the bot from starting; retain a known-good configuration to restore.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Eggdrop

Fizi — Mon, 05 Oct 2026 20:22:18 GMT

Created page with "'''Create and manage an Eggdrop bot''' Create an instance, edit its own configuration and keep other bots running during changes. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/eggdrop/ Visual website guide] =..."

New page

DWShells:ZNC

Fizi — Mon, 05 Oct 2026 20:21:58 GMT

Fizi protected DWShells:ZNC [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Set up and connect to ZNC'''

Create a managed bouncer, connect your IRC client and understand the two network connections.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/znc/ Visual website guide]

== ZNC has two separate connections ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Your IRC client
|Connects inbound using ZNC login and assigned listener port.
|-
|02 · Your ZNC
|Runs on the shell and keeps its network session.
|-
|03 · IRC network
|Receives the outbound connection on its server port.
|}

== Check permissions and ports ==
'''Before you continue:''' Open Packages for the selected active shell. ZNC must be permitted and an assigned listener port must be available. If your allocation has only one listener port, ZNC and Eggdrop cannot both reserve it. Do not copy a port from another user.

== Create a managed instance ==

# '''Open the ZNC manager.''' In Packages, choose ZNC. If an existing instance is already configured, inspect its details instead of running setup again.
# '''Enter the ZNC identity.''' Choose the ZNC username, IRC nickname and a separate ZNC password of at least 14 characters. Confirm the password.
# '''Choose the IRC network.''' Enter a network name and a permitted IRC server. DarkWorld community connections use irc.darkworld.chat with TLS on 6697. Keep Use TLS to IRC server enabled for that connection. Other networks must meet shell network policy.
# '''Set up and start.''' Use Set up and start ZNC. The portal chooses an available assigned listener port. Wait for the result, then check status and View logs.

== Connect your IRC client ==
Use the Client connection details shown by the manager: hostname/address, listener port, TLS setting and login. The displayed login can include the network, such as ZNC_USERNAME/NETWORK_NAME. Use the ZNC password, not the shell or dashboard password.
{| class="wikitable"
!What you see
!What to do
|-
|Client → ZNC
|Your assigned application listener port, shown in Packages. Use the displayed SSL/TLS setting.
|-
|ZNC → IRC network
|The network server’s port, for example TLS 6697. This is not your allocated listener port.
|-
|IPv4 inbound
|Use only a connection marked IPv4 forwarding confirmed. Otherwise follow the IPv6 details or contact staff.
|-
|Free outbound
|IRC connections use assigned IPv6. IPv4 access from your client does not change that policy.
|-
|Other plans outbound
|Managed configuration prefers assigned IPv6 with permitted IPv4 fallback.
|}

== TLS and the web interface ==
Match the displayed hostname to the certificate. Verify a fingerprint when the portal supplies one; do not disable certificate verification to hide a warning. Use Open ZNC web only when the manager shows it. “Web Access is not enabled” means the web interface is not available, not necessarily that the IRC listener is down.

== Manage or replace ZNC ==
Use Start, Stop, Restart and View logs. Install fresh and Delete ZNC are destructive: stop first and make an independent copy of needed settings. The confirmation removes configuration, credentials, logs and scripts. Install fresh reopens setup; it is not a repair that preserves your existing account.

== Troubleshooting ==
{| class="wikitable"
!What you see
!What to do
|-
|Client cannot connect
|Check assigned listener port, TLS and forwarding status, then the running state and logs.
|-
|Client connects, network is offline
|Check IRC server, server port, TLS, permitted destinations and IPv6 support on Free.
|-
|Login rejected
|Use the displayed ZNC login and ZNC password. Network names matter.
|-
|No available port
|Review existing app reservations and your allocation; ask staff before changing ports.
|}

== Client connection checklist ==

# Open the selected shell's ZNC manager and confirm it is running.
# Copy the displayed hostname or address and allocated listener port.
# Match the displayed client TLS setting.
# Use the displayed ZNC login, including <code>/NETWORK_NAME</code> when present.
# Enter the separate ZNC password in your IRC client's appropriate credential field.
# Inspect the ZNC network connection after the client has authenticated.

For irssi, the panel provides '''Copy irssi command''' and, when forwarding is confirmed, '''Copy IPv4 command'''. Read the generated command, replace its password placeholder locally, and verify the displayed certificate information. Do not post the completed command in a public channel or support ticket.

== Recover without unnecessary reinstallation ==
Start with running state and logs. Restart only when appropriate. An inbound connection problem is different from an offline IRC network connection. Installing fresh destroys the selected configuration and credentials; use it only when you intentionally want a new setup and have copied what you need.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:ZNC

Fizi — Mon, 05 Oct 2026 20:21:41 GMT

Created page with "'''Set up and connect to ZNC''' Create a managed bouncer, connect your IRC client and understand the two network connections. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/znc/ Visual website guide] == ZNC has tw..."

New page

DWShells:Website Hosting

Fizi — Mon, 05 Oct 2026 20:21:18 GMT

Fizi protected DWShells:Website Hosting [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Publish your personal website'''

Upload a first page, use File Manager and keep private material out of public_html.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/personal-website/ Visual website guide]

== From a file to a public page ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Your computer
|Prepare index.html and a backup copy.
|-
|02 · public_html
|Upload using File Manager or SFTP.
|-
|03 · Personal HTTPS URL
|Open the website address from your dashboard.
|}

== What becomes public ==
'''Before you continue:''' Files in public_html are website content. Never place passwords, private keys, application configs, database dumps or backup archives there. Hosting must fit your approved use and plan.

== Publish a first page ==

# '''Select the website location.''' Open File Manager for the correct shell. Set File location to Website · public_html. The Eggdrop location is for bot files, not public web content.
# '''Upload index.html.''' Use Upload file for a file from your computer. For folders or larger transfers, use SFTP. Copy your existing site before overwriting files.
# '''Visit the right URL.''' Open the personal HTTPS website link in your dashboard. Do not add an SSH or ZNC port. The hostname alone is not a substitute for the exact dashboard link.
# '''Edit and check.''' Use the file editor for a text change and Save file. Reload the website and check that links, images and filenames match, including letter case.

== A minimal page to try ==
Save this as index.html on your computer. Replace the sample heading before uploading:<pre>
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>My shell website</title>
</head>
<body>
<h1>Hello from my DWShells website</h1>
<p>This is my personal page.</p>
</body>
</html>
</pre>

== Files and scripts ==
New folder creates a directory in the current location. Upload file transfers one file. The editor saves text files; it does not build a framework or enable unsupported runtimes. Static HTML is a good first check. PHP or other dynamic hosting depends on your effective permissions. Deletion is permanent in the file manager; keep your own copies.

== Troubleshooting ==
{| class="wikitable"
!What you see
!What to do
|-
|Old page still appears
|Check you edited the selected shell’s public_html, saved the file and refreshed the browser.
|-
|An image is missing
|Match the filename and relative path exactly; Linux paths are case-sensitive.
|-
|Upload is too large or a folder will not upload
|Use SFTP and check the disk allocation.
|-
|Page is unavailable
|Check shell status and the exact HTTPS link, then report the URL and error to staff.
|}

== Example directory layout ==
{| class="wikitable"
!Location
!Purpose
|-
|<code>public_html/index.html</code>
|Your entry page
|-
|<code>public_html/style.css</code>
|Public stylesheet
|-
|<code>public_html/images/logo.png</code>
|Public image referenced by your HTML
|-
|Outside <code>public_html</code>
|Private account files; keep credentials and backups out of the website
|}
Use relative links such as <code>images/logo.png</code> when the page is in <code>public_html</code>. A file named <code>Logo.png</code> is different from <code>logo.png</code>.

== Safe updates ==
Download a copy of the existing page, upload your replacement, then test the live HTTPS link. Do not use world-writable permissions or publish configuration secrets to fix a hosting error. Ask staff about unsupported runtimes and commercial hosting before deploying them.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Website Hosting

Fizi — Mon, 05 Oct 2026 20:21:02 GMT

Created page with "'''Publish your personal website''' Upload a first page, use File Manager and keep private material out of public_html. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/personal-website/ Visual website gu..."

New page

DWShells:SSH and SFTP

Fizi — Mon, 05 Oct 2026 20:20:41 GMT

Fizi protected DWShells:SSH and SFTP [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Connect through SSH and SFTP'''

Use the browser terminal or your own SSH client, then transfer files securely.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/ssh-and-sftp/ Visual website guide]

== Choose your connection ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Browser
|Panel → Shell Access → shell password.
|-
|02 · SSH client
|Terminal → shared login host → shell username.
|-
|03 · SFTP
|File client → same host and shell credentials.
|}

== Before connecting ==
'''Before you continue:''' Your shell must be active. Replace YOUR_USERNAME with the exact Linux shell username shown in your dashboard. Do not type it literally.

== Browser terminal ==

# '''Open Shell Access.''' Select the correct shell, open Shell Access and enter your shell password.
# '''Connect and focus.''' Click Connect to shell, then click inside the terminal and type at the visible prompt. The dashboard password is not the SSH password.
# '''Finish deliberately.''' Use Disconnect when finished. A normal foreground program can stop when its SSH session ends; use an approved persistent session for work that must stay attached elsewhere.

== SSH from your computer ==
Open a terminal such as PowerShell, Windows Terminal, macOS Terminal or a Linux terminal and run:<pre>
ssh YOUR_USERNAME@shells.darkworld.network
</pre>The shared login host is shells.darkworld.network. Use the SSH port shown in your dashboard; the command above uses the standard SSH port. A personal website address or application listener port is a different service. On a first connection, verify the server host-key fingerprint through a trusted staff channel before accepting it. Do not dismiss a changed-host-key warning without checking.

== Transfer files with SFTP ==
<pre>
sftp YOUR_USERNAME@shells.darkworld.network
</pre>For a desktop file client, select SFTP, enter the shared host and your shell username, then use the shell password or an authorised SSH key. Do not select plain FTP. Upload website content into public_html and keep private files outside it.<pre>
pwd
ls
cd public_html
put index.html
bye
</pre>These are example SFTP commands: inspect the current location before uploading; put index.html can replace an existing file. Keep a copy first.

== If the connection fails ==
{| class="wikitable"
!What you see
!What to do
|-
|Permission denied
|Confirm the Linux username, active status and shell password. Use the supplied reset process if needed.
|-
|Timeout or refusal
|Check hostname, displayed SSH port and service notices. Report the exact error and time.
|-
|Host key changed
|Pause and ask staff to verify the fingerprint; do not blindly remove the saved key.
|-
|Typing is not visible
|Password entry normally has no visible characters. In browser SSH, click inside the terminal after connecting.
|}

== Useful first shell commands ==
These commands inspect your own account and files:<pre>
pwd
ls -la
whoami
</pre><code>pwd</code> prints your current directory, <code>ls -la</code> lists entries including hidden names, and <code>whoami</code> prints the logged-in Linux username. Do not publish command output containing private paths or credentials.

== SSH keys and host keys are different ==
Your personal public key authorises your login and can be managed in Security Centre. The server host key identifies the SSH server to your client. Confirm an unfamiliar or changed server fingerprint with staff; uploading your personal key does not verify the server's identity.

== Desktop SFTP settings ==
{| class="wikitable"
!Setting
!Value
|-
|Protocol
|SFTP (SSH File Transfer Protocol)
|-
|Host
|<code>shells.darkworld.network</code>
|-
|Username
|Your Linux shell username
|-
|Port
|The displayed SSH port; do not use a ZNC/Eggdrop listener port
|-
|Authentication
|Shell password or your authorised private key on your own device
|}

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:SSH and SFTP

Fizi — Mon, 05 Oct 2026 20:20:20 GMT

Created page with "'''Connect through SSH and SFTP''' Use the browser terminal or your own SSH client, then transfer files securely. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/ssh-and-sftp/ Visual website guide] == Choo..."

New page

DWShells:Customer Panel

Fizi — Mon, 05 Oct 2026 20:19:53 GMT

Fizi protected DWShells:Customer Panel [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''Find your way around the panel'''

Choose the correct shell and know which page handles files, apps, access and renewal.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/dashboard/ Visual website guide]

== One account, selected-shell controls ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Dashboard account
|Your sign-in and Inbox belong to the customer account.
|-
|02 · Shell selector
|Choose the shell before making changes.
|-
|03 · Section
|Open files, packages, access or renewal for that shell.
|}

== Start with the selected shell ==
Use the shell selector when more than one shell is linked. Read the username and status before starting an app, editing files or renewing. Limits and network allocations can differ between shells. An inactive shell may have unavailable controls.

== Where to go ==
{| class="wikitable"
!What you see
!What to do
|-
|Overview
|Shell status, connection facts and next steps.
|-
|Plans
|Available plans and the request workflow.
|-
|Shell Access
|Browser SSH terminal using your shell password.
|-
|File Manager
|Website files or an installed Eggdrop instance.
|-
|Packages
|Manage permitted ZNC, Eggdrop, Python or persistent sessions.
|-
|Resource Usage
|Measured usage and the selected shell’s limits.
|-
|IPv6 / DNS
|Assigned addresses and supported hostname controls.
|-
|Keep / Renewal
|The selected shell’s deadline and renewal allowance.
|-
|Security Centre
|Dashboard 2FA and public SSH keys for the shell.
|-
|Backups & Restore
|Available home copies and recovery requests.
|-
|Inbox
|Messages for the customer account, shared across linked shells.
|}

== A safe daily routine ==

# '''Read notices.''' Check Overview and Inbox before assuming a service is ready.
# '''Check renewal and resources.''' Review Keep / Renewal if required, then Resource Usage. An app shares CPU, memory, disk and process limits with everything else on the shell.
# '''Make one change at a time.''' Choose the instance, apply the change and inspect the result or logs. Confirm the selected username again before destructive operations.

== Three credentials to distinguish ==

* Dashboard password: signs you into the portal and confirms sensitive security actions.
* Shell password: connects to SSH/SFTP and the browser terminal.
* Application password: connects to your ZNC or Eggdrop owner account; it is not your shell password.

== When controls are unavailable ==
Read the displayed explanation. A plan restriction, inactive shell or exhausted allocation can disable an action. Contact staff for changes rather than starting duplicate instances to bypass a limit.

== Diagnose a problem before contacting staff ==
Record the selected shell username, the panel section, the action you attempted, the exact error and the approximate time with timezone. Redact passwords, tokens, private keys and private messages. A screenshot should show the error and relevant status only.

A successful page refresh does not mean a queued operation has completed. Read the action result and the selected shell's current state. Changing shells changes the target of the controls; check it before every write operation.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Customer Panel

Fizi — Mon, 05 Oct 2026 20:19:41 GMT

Created page with "'''Find your way around the panel''' Choose the correct shell and know which page handles files, apps, access and renewal. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/dashboard/ Visual website guide]..."

New page

DWShells:Documentation

Fizi — Mon, 05 Oct 2026 20:19:20 GMT

Fizi protected DWShells:Documentation [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''DWShells documentation'''

Practical documentation for the DarkWorld shell service. Start with signup, learn your dashboard, then choose a guide for the task you want to perform.

'''Last verified:''' 6 October 2026.

The [https://shells.darkworld.network/guides/ website guides] provide illustrated introductions. This wiki contains the detailed instructions and [[DWShells:Signup and Rules|authoritative service rules]]. Your selected shell's dashboard shows its actual permissions, limits, assigned ports and status.

== Start here ==

* [[DWShells:Getting Started|Getting Started]] — Register, request a plan, complete verification and recognise when your shell is ready.
* [[DWShells:Customer Panel|Customer Panel]] — Choose the correct shell and know which page handles files, apps, access and renewal.
* [[DWShells:SSH and SFTP|SSH and SFTP]] — Use the browser terminal or your own SSH client, then transfer files securely.
* [[DWShells:Website Hosting|Website Hosting]] — Upload a first page, use File Manager and keep private material out of public_html.
* [[DWShells:ZNC|ZNC]] — Create a managed bouncer, connect your IRC client and understand the two network connections.
* [[DWShells:Eggdrop|Eggdrop]] — Create an instance, edit its own configuration and keep other bots running during changes.
* [[DWShells:Keep Renewal|Keep Renewal]] — Read your countdown, renew before the deadline and understand the daily allowance.
* [[DWShells:Python and Tmux|Python and Tmux]] — Use approved Python environments and reconnect to portal-managed tmux sessions.
* [[DWShells:Security and Backups|Security and Backups]] — Use dashboard 2FA, public SSH keys and realistic backup expectations.
* [[DWShells:IPv6 and DNS|IPv6 and DNS]] — Assigned IPv6, DNS status and inbound/outbound application connectivity.

== Important distinctions ==

* Dashboard registration and email verification do not immediately activate a Linux shell.
* Dashboard, shell and application passwords serve different purposes.
* Your application listener port is separate from the IRC network's server port.
* Inbound IPv4 forwarding does not change the Free outbound IPv6 policy.
* Keep renewal is separate from paid subscription renewal.
* Backup approval is separate from completed manual recovery.

== Rules and help ==

* [[DWShells:Signup and Rules|Signup and Rules]] — the single authoritative rules page; do not duplicate rules across guides.
* [https://panel.shells.darkworld.network/customer/ Customer panel] — requests, actual account status and management controls.
* [https://shells.darkworld.network/contact/ Contact staff] — corrections and enquiries.
* '''#DWShells''' on <code>irc.darkworld.chat</code>, TLS port '''6697''' — community support and announcements.

Never post passwords, SSH private keys, application credentials, recovery codes, verification links or private customer data in wiki examples or support requests.

DWShells:Getting Started

Fizi — Mon, 05 Oct 2026 20:19:03 GMT

Fizi protected DWShells:Getting Started [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite) [cascading]

New page

'''From signup to your first shell'''

Register, request a plan, complete verification and recognise when your shell is ready.

'''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples.

[[DWShells:Documentation|← Documentation hub]] · [https://shells.darkworld.network/guides/getting-started/ Visual website guide]

== Your path to an active shell ==
{| class="wikitable"
!Step
!What it means
|-
|01 · Register
|Create and verify the dashboard account.
|-
|02 · Request
|Choose a plan and complete its checks.
|-
|03 · Review
|Staff approve and provision the shell.
|-
|04 · Connect
|Set the shell password and check active status.
|}

== What you need ==
A supported Gmail or googlemail.com address, your intended use and—when requesting Free—your DarkWorld IRC identity. Registration creates a dashboard account; it does not immediately create a Linux shell.

== Follow the dashboard ==

# '''Register and verify.''' Open the [https://panel.shells.darkworld.network/customer/ customer portal]. Complete registration and the email verification requested there. Use the customer URL ending in /customer/.
# '''Choose the right plan.''' Open Plans. Free is intended for IRC-related use. Other plans may allow broader approved work. Read the limits and submit an accurate request. Follow payment-review instructions for a paid request.
# '''Complete Free verification.''' Register and identify your nickname with NickServ on DarkWorld IRC. Follow the dashboard’s DWShells challenge and community information steps exactly. Join #DWShells on irc.darkworld.chat with TLS on port 6697 for help; merely joining the channel does not complete every check.
# '''Watch the request status.''' Respond to staff questions and check Inbox. Approval and provisioning are separate stages. Do not submit repeated requests while review is pending.
# '''Set your shell password.''' Use the password form or recovery process provided when requested. This is separate from your dashboard password. Wait until the shell shows active before attempting SSH.

== Already have a shell? ==
Register and verify the dashboard account, then ask staff to link your existing shell after ownership checks. Do not request a duplicate. Linking does not automatically renew a subscription, reset the shell password or reactivate a suspended shell.

== You are ready when ==

* Your shell appears in the dashboard and is active.
* You have set the shell password and can see your connection details.
* You understand the plan’s permissions and any Keep requirement.

== If something blocks progress ==
{| class="wikitable"
!What you see
!What to do
|-
|Verified account, no shell
|Check request and provisioning status. Verification alone does not create a shell.
|-
|Request needs information
|Read Inbox and the eligibility instructions; complete the missing step.
|-
|Existing username not linked
|Contact staff with ownership details. Never send passwords or verification links.
|}

== Registration, approval and activation are different ==
{| class="wikitable"
!Stage
!Meaning
|-
|Dashboard registered
|A customer account exists; shell access has not been granted.
|-
|Email verified
|Ownership of the email is confirmed; the request can still need other checks.
|-
|Request approved
|Staff have accepted the request; provisioning or password setup may still be pending.
|-
|Shell active
|Use the assigned connection details and your shell password.
|}
Do not publish verification tokens, reset links or customer dashboard screenshots containing private details.

== Rules and support ==
This guide describes how to use the service; it does not replace [[DWShells:Signup and Rules|Signup and Rules]]. Join '''#DWShells''' on <code>irc.darkworld.chat</code> using TLS port '''6697''' for help. Use [https://panel.shells.darkworld.network/customer/ the customer portal] for your actual status and connection details. Never share credentials or recovery links.

[[DWShells:Documentation|Back to documentation]]

DWShells:Getting Started

Fizi — Mon, 05 Oct 2026 20:18:35 GMT

Created page with "'''From signup to your first shell''' Register, request a plan, complete verification and recognise when your shell is ready. '''Last verified:''' 6 October 2026, against the current customer panel and service rules. Your effective dashboard permissions and assigned values take precedence over examples. ← Documentation hub · [https://shells.darkworld.network/guides/getting-started/ Visual websi..."

New page

DWShells:Documentation

Fizi — Mon, 05 Oct 2026 20:17:43 GMT

Created page with "'''DWShells documentation''' Practical documentation for the DarkWorld shell service. Start with signup, learn your dashboard, then choose a guide for the task you want to perform. '''Last verified:''' 6 October 2026. The [https://shells.darkworld.network/guides/ website guides] provide illustrated introductions. This wiki contains the detailed instructions and authoritative service rules. Your s..."

New page

DWShells:Signup and Rules

Fizi — Sun, 04 Oct 2026 17:27:43 GMT

Fizi protected DWShells:Signup and Rules [Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)

New page

DWShells provides Linux shell accounts for IRC and other approved uses. These rules apply to every account, including Free, Support, Support-Plus, Premium, Staff and Developer. Available applications and resources depend on your plan and any approved account-specific limits.

== Signup process ==

=== 1. Register and verify your email ===

Open the [https://panel.shells.darkworld.network/customer/ DWShells customer portal] and complete registration. Registration currently accepts Gmail addresses, including the supported googlemail.com domain. Complete the email verification requested by the portal.

Your dashboard account and your Linux shell account are separate. Registering or verifying your email does not immediately create or activate a shell.

=== 2. Choose your plan and submit a request ===

Choose Free or an available paid plan through the dashboard. Provide accurate information and explain your intended use. Free shells are intended for IRC-related use; other plans may support broader approved uses.

For a Free request, complete the portal's IRC identity and community verification steps. Register and identify your nickname with NickServ on DarkWorld IRC, then follow the dashboard's instructions to complete the DWShells verification challenge and supply the requested community information.

For a paid plan, follow the displayed request and payment-review instructions. Payment or a donation does not bypass approval or these rules.

=== 3. Wait for staff review ===

Staff review your customer account, request, verification and eligibility. Respond to requests for additional information. Approval and provisioning are separate stages, and activation time depends on review and service availability.

=== 4. Set your shell password and await activation ===

When the dashboard requests it, set your shell password through the provided form. Follow the status shown until your shell is active. Never send your password, verification link or recovery codes to staff or post them in IRC.

=== 5. Connect and manage your shell ===

Once activated, use the connection details in your dashboard. The shared SSH and SFTP login host is <code>shells.darkworld.network</code>:

<pre>
ssh YOUR_USERNAME@shells.darkworld.network
sftp YOUR_USERNAME@shells.darkworld.network
</pre>

Your personal hostname, website and application ports are listed separately. Use Packages to manage permitted applications and Keep / Renewal to check renewal requirements.

=== Existing shell users ===

Register and verify your dashboard account, then contact staff to have your existing shell linked after ownership checks. Do not submit a duplicate new-shell request for an account you already own. Linking does not reset your shell password, renew a paid subscription or reactivate a suspended account.

== Account and security rules ==

* Use your account only for its approved purpose and plan.
* Keep registration and ownership information accurate. Do not impersonate another person or claim a shell you do not own.
* Do not share, lend, sell or transfer your shell or dashboard access. Additional shells require staff approval; do not create duplicate registrations to bypass limits or a suspension.
* Protect passwords, SSH keys, application credentials and recovery codes. Report suspected compromise promptly.
* Do not access another user's files, credentials, processes or private information, or attempt to gain elevated privileges.
* Do not bypass quotas, application limits, network restrictions, renewal controls or security monitoring.

== Prohibited activity ==

* Port scanning, vulnerability scanning or probing third-party Internet hosts from DWShells is prohibited. Security testing requires prior written staff permission and authorization from the target owner.
* DoS/DDoS attacks, flooding, brute-force attacks, credential theft and other disruptive activity are prohibited.
* Do not run or distribute malware, trojans, backdoors or exploit code intended to compromise systems.
* Cryptocurrency mining and unauthorized distributed computing are prohibited.
* Do not send spam, phishing messages or unsolicited bulk messages through email, IRC or another service.
* Do not store or publish illegal material, pirated software, stolen data or links intended to distribute such material.
* Do not operate public proxies, open relays, VPN gateways, Tor relays/exits or similar traffic-forwarding services without explicit staff approval. A plan-authorized personal ZNC bouncer is permitted within its limits.

== IRC and applications ==

* Follow the rules of every IRC network and channel you use. Do not evade bans, abuse channels, flood users or operate abusive bots.
* Use only permitted IRC destinations and ports. Request staff review when a required network is unavailable; do not tunnel around restrictions.
* ZNC, Eggdrop, IRC clients and other background applications are allowed only within your plan's permissions and account limits. Python environments and other development features depend on your plan.
* Stay within the displayed IRC connection and application limits. Do not run unnecessary duplicate clients or instances, or provide bouncer access to other people without approval.
* Use only your assigned IP addresses and ports. Do not bind another account's allocation or expose an unapproved service.
* Free shells use IPv6 for outbound IRC connections. Support and other non-Free plans can use IPv4 and IPv6 where permitted, with IPv6 preferred by the managed configuration.
* Allocated inbound IPv4 access to ZNC or another permitted application does not grant Free shells outbound IPv4 IRC access.
* Use encrypted connections wherever supported. Follow the application's displayed TLS settings, hostname and assigned listener port.

== Resources and hosting ==

* Respect your disk, memory, CPU, process, bandwidth, connection and application limits. Your dashboard shows your effective allocation, including approved overrides.
* Stop unused services and keep logs and temporary files under control. Do not use the shell for resource-intensive workloads outside its approved purpose.
* Request extra resources before exceeding limits. A paid account remains subject to fair use and security rules.
* Keep websites and scripts lawful, secure and within the permitted scope of your plan. Free hosting must support the approved personal or IRC-related use.
* Business use, resale, paid hosting for others and commercial workloads require explicit staff approval and a suitable plan.
* You are responsible for uploaded files, scripts, application configuration and website content. Do not leave an insecure application exposed.

== Free account Keep / Renewal ==

* Keep is enabled by default for Free shells. Check the selected shell's countdown and use the dashboard's Keep / Renewal page before its deadline.
* A normal successful Keep provides at least 14 days from renewal. Repeated Keeps do not accumulate unlimited time, and a later staff-approved deadline is preserved.
* You may complete at most two successful user Keeps per shell per UTC day. The allowance resets at midnight UTC, which is 5:00 a.m. in Pakistan.
* Each shell has its own renewal status. SSH activity or leaving a bot running does not replace Keep renewal.
* Contact staff before expiry if illness, travel or an emergency prevents renewal. Extensions and timer pauses require staff review.
* An expired, locked or suspended account may require staff review before access can be restored. Keep does not bypass suspension.
* Keep is off by default for other plans. If staff enables it there, it records activity and does not replace paid renewal or extend a subscription.

== Community and support ==

Join '''#DWShells on DarkWorld IRC''', using <code>irc.darkworld.chat</code> with TLS on port '''6697''', for help and service announcements. Add the channel to autojoin where practical and check dashboard notices regularly.

Treat users and staff respectfully. Do not harass, threaten, impersonate or publish another person's private information. Support volunteers may take time to respond; keep your question available and check back later.

== Backups and enforcement ==

Keep your own independent copies of important files. Available backup and restore features have coverage limits and do not guarantee recovery of every file or live application state. Review the warnings shown for your shell before relying on a backup.

Staff may stop an application, restrict access or suspend an account to contain abuse or protect the service. Minor issues may receive a warning and an opportunity to correct them; serious or repeated violations may result in immediate suspension or account closure. These rules apply equally to paid accounts.

If you believe an action was taken in error, contact staff with your username and relevant details. Do not create another account to evade the restriction.

[[Category:DWShells]]

DWShells:Rules

Fizi — Sun, 04 Oct 2026 17:27:27 GMT

Fizi moved page DWShells:Rules to DWShells:Signup and Rules

New page

DWShells:Signup and Rules

Fizi — Sun, 04 Oct 2026 17:27:22 GMT

Fizi deleted page DWShells:Signup and Rules content was: "a", and the only contributor was "Fizi" (talk)

DWShells:Signup and Rules

Fizi — Sun, 04 Oct 2026 17:26:42 GMT

Fizi protected DWShells:Signup and Rules [Create=Allow only administrators] (indefinite)

DWShells:Rules

Fizi — Sun, 04 Oct 2026 17:21:25 GMT

Created page with " DWShells provides Linux shell accounts for IRC and other approved uses. These rules apply to every account, including Free, Support, Support-Plus, Premium, Staff and Developer. Available applications and resources depend on your plan and any approved account-specific limits. == Signup process == === 1. Register and verify your email === Open the [https://panel.shells.darkworld.network/customer/ DWShells customer..."

New page