- 01Your browser
Open CloudIRC inside the panel or in a new tab.
- 02Your shell instance
The Lounge runs under your shell account and shared limits.
- 03IRC networks
Connect using your assigned IPv6 and existing IRC allowance.
Check access
CloudIRC is enabled by default on Support-Plus and Premium. Staff and other plans need an explicit administrator grant; staff can also disable it on an included plan. Select an active linked shell, open Packages and check the CloudIRC card. Its actual availability follows that shell’s effective access, not just the plan name.
Install and connect
Choose CloudIRC in Packages
Click Manage on the CloudIRC · The Lounge card for the correct shell.
Create a separate password
Enter and confirm a CloudIRC password. Use at least 14 characters and no more than 72 UTF-8 bytes; non-ASCII characters can occupy several bytes. This is separate from your dashboard, shell and ZNC passwords.
Install and start
Use Install and start. Wait for the action result and Running status. The instance’s data is stored in ~/apps/thelounge/.
Open the client
Use Open Cloud IRC here for the embedded client or Open in new tab. Sign in with the shell username shown in the manager and your CloudIRC password.
Add your IRC connection
Use The Lounge’s network connection screen with a permitted server, its port and TLS setting. DarkWorld community connections use irc.darkworld.chat with TLS on 6697. Your IRC nickname and any NickServ credentials are separate from the CloudIRC login. Check network rules and join only channels where you are welcome.
The managed instance remains connected while its service is running even if you close the browser. A stopped service, account restriction, network error or host interruption can disconnect it.
Understand limits
| Feature | Current behaviour |
|---|---|
| Resources | Shares the shell’s CPU, RAM, disk and process limits with other applications. |
| Networks | The saved-network cap comes from the effective IRC connection allocation. Active IRC connections share that allowance with ZNC, Eggdrop and other clients. |
| Connectivity | Uses the shell’s assigned IPv6 first. Permitted non-Free plans can fall back to IPv4; a granted Free instance remains IPv6-only for outbound IRC. |
| History | Current managed retention is 30 days. Retained history uses your disk allocation. |
| Uploads | File uploads are disabled in the managed CloudIRC instance. |
CloudIRC uses an assigned address from your shell; it does not add another IPv6 allocation or give an unlimited network allowance. Check Resource Usage before adding networks or running more apps.
Manage your instance
Use Start, Stop, Restart and View logs in its package manager. Reset Cloud IRC password changes the application password and signs out existing CloudIRC sessions. Turning access off in the admin panel stops the managed instance and blocks its web route, while retaining its data.
Troubleshooting
| What you see | What to do |
|---|---|
| Not included / not enabled | Check the selected plan and ask staff to review per-shell access. An included plan may have an explicit disable. |
| Setup says hosting is not ready | Ask staff to check the personal HTTPS hosting prerequisite. |
| No Open Cloud IRC button | Check that installation completed and the service is Running. |
| Login rejected | Use the displayed shell username and the separate CloudIRC password. Reset it from Packages if necessary. |
| One network will not connect | Check server, TLS, network rules, outbound permissions and shared IRC capacity. Look at logs without posting credentials. |
| Embedded client is unavailable | Try Open in new tab. Report the selected shell, time and exact error to staff. |
Verified against the current CloudIRC package manager and managed policy. Follow DWShells rules and your dashboard’s displayed permissions. See the wiki documentation hub or contact staff.