Skip to main content

Connect Discord

Connect Discord in the Provider Portal so renters can invite you into private pod support channels. Without a connected provider Discord account, renters see Provider has not connected Discord on pods running on your machines and cannot create the shared channel from the pod detail page. Keeping Discord connected also keeps your provider account eligible for extra subnet incentives.

Discord and extra incentives​

Providers must keep Discord connected to remain eligible for extra subnet incentives. If Discord is not connected, your nodes do not earn the incentive portion until Discord is connected again.

This requirement applies to subnet incentives only. Rental fees paid by renters for active GPU usage are separate.

Connect your provider account​

  1. Sign in to provider.lium.io.
  2. Open Profile Settings.
  3. Find the Discord section.
  4. Click Connect Discord.
  5. Approve the Discord OAuth prompt.
  6. Return to the Provider Portal and confirm the Discord section shows Connected.

The Provider Portal stores your Discord user ID on your provider profile. The support channel flow uses that ID to grant you access to channels for pods rented from your machines.

Connect from the CLI​

After logging in with the provider CLI:

lium provider portal login
lium provider config connect-discord

The CLI opens the Discord authorization URL when possible. On a headless machine or in an agent workflow, use:

lium provider config connect-discord --json --no-wait

Open the returned authorization_url as the Discord account owner and approve the OAuth prompt. Check readiness with:

lium provider status --json

Look for discord_connected: true and extra_incentive_eligible: true.

Disconnect Discord​

Use Disconnect Discord from the same Discord section if you need to unlink the account. After disconnecting, new renter support channels cannot include you until you connect Discord again.

How renter support channels work​

When a renter clicks Request Discord Support on a pod detail page:

  1. Lium checks that the renter has connected Discord.
  2. Lium checks that the provider assigned to that pod has connected Discord.
  3. Lium creates a private Discord text channel under the configured Lium support category, or returns the existing pod channel if one already exists.
  4. Lium grants channel access to the renter, the provider, and the configured support role.
  5. Lium posts a pod context message with the pod ID, machine details, Docker image, ports, SSH command, hardware, price, and location.

The channel name is generated from the pod name and pod ID. The channel is stored on the pod record, so repeated support requests reopen the same channel instead of creating duplicates.

When the pod is removed, Lium attempts to delete the stored Discord channel during pod cleanup.

Troubleshooting​

IssueWhat to check
Connect Discord fails immediatelyThe Provider Portal backend Discord OAuth configuration may be missing. Contact Lium support.
OAuth returns Discord Connection FailedRetry the connection. If it repeats, contact Lium support with the error shown in the notification.
The portal says Discord is connected but renters still cannot request supportConfirm the pod is running on a machine owned by the same provider hotkey that has Discord connected.
You cannot see a support channel after a renter says they requested oneConfirm you are signed in to Discord with the connected account. If you recently disconnected/reconnected, ask the renter to retry from the pod detail page.