Troubleshooting

Important

If your issue is related to a specific activity, please submit it to the activity repository.

Activity Not Showing in Discord?

• Desktop app is running in system tray
• Website is supported and extension is enabled
• A song is actually playing (not paused or muted)
• The music tab is not minimized
• "Share my activity" is enabled in Discord:
  • User Settings (gear icon) → Activity Privacy → Toggle on
• If Discord runs as administrator, run Discord Music RPC as administrator too
• Check logs for errors:
  • Server logs: Tray app → "Open logs" (Debug section)
  • Extension logs: Extension popup → Settings → Toggle "Activate Debug Mode" → Check browser console

Browser Related Issues

Modern browsers use methods such as freezing background tabs and restricting JavaScript to save resources. This can cause issues with RPC updates.

Chrome

Disable Memory Saver and Energy Saver

1. Open:

   chrome://settings/performance
   

2. Turn OFF "Memory Saver"

3. Turn OFF "Energy Saver"

---

Add Site Exception

1. Open:

   chrome://settings/performance
   

2. Click "Add" next to:

   Always keep these sites active
   

3. Add your music site.

---

Disable Background Throttling & Window Occlusion

Chrome sometimes slows down background tabs. If your site is not updating properly, you can apply advanced settings:

Windows

You can run a pre-made Registry file and restart Chrome. [Click here to download Registry file]

This file sets the following registry keys:

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
"IntensiveWakeUpThrottlingEnabled"=dword:0
"WindowOcclusionEnabled"=dword:0

[HKEY_CURRENT_USER\Software\Policies\Google\Chrome]
"IntensiveWakeUpThrottlingEnabled"=dword:0
"WindowOcclusionEnabled"=dword:0

What this does: Stops Chrome from slowing down background tabs. Prevents "window occlusion" from pausing tabs when they're hidden.

---

Linux

Note: If you are using Chromium instead of Google Chrome, replace the path with: /etc/chromium/policies/managed/

1. Open the terminal (Ctrl+Alt+T on most distributions).
2. Create the managed policies folder if it doesn't exist:

sudo mkdir -p /etc/opt/chrome/policies/managed/

3. Create the policy file:

sudo nano /etc/opt/chrome/policies/managed/background_throttle.json

4. Paste this content into the file:

{
  "IntensiveWakeUpThrottlingEnabled": false,
  "WindowOcclusionEnabled": false
}

5. Save the file (Ctrl+O in nano) and exit (Ctrl+X).
6. Restart Chrome.

---

macOS

1. Open Terminal (Applications → Utilities → Terminal)

2. Create the managed policies folder if it doesn't exist:

sudo mkdir -p "/Library/Managed Preferences/"

3. Create the policy file:

sudo nano "/Library/Managed Preferences/com.google.Chrome.plist"

4. Paste this content into the file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>IntensiveWakeUpThrottlingEnabled</key>
    <false/>
    <key>WindowOcclusionEnabled</key>
    <false/>
</dict>
</plist>

5. Save the file (Ctrl+O in nano) and exit (Ctrl+X).

6. Restart Chrome.

Note: If policies are not applying, try placing the file in the user-specific folder instead: /Library/Managed Preferences/<your_username>/com.google.Chrome.plist

---

Firefox

About Config Method

1. Open:

   about:config
   

2. Click Accept the Risk

3. Search and set the following values to false:

   dom.suspend_inactive.enabled
   widget.windows.window_occlusion_tracking.enabled
   widget.windows.window_occlusion_tracking_display_state.enabled
   widget.windows.window_occlusion_tracking_session_lock.enabled
   

4. Search and set the following values to 0:

   dom.min_background_timeout_value
   dom.timeout.background_throttling_max_budget
   dom.min_background_timeout_value_without_budget_throttling
   

---

Performance Settings

1. Open:

   about:preferences
   

2. Scroll to Performance

3. Uncheck:

   Use recommended performance settings
   

---

Linux-Specific Issues

Quick Diagnostic (Recommended)

Use Tray → Debug → "Run IPC Diagnostic (Linux)" to auto-check your setup.

Discord Installation Types

Type	IPC Support	Setup
Native (Recommended)	Best	Install via package manager
Snap	Needs config	sudo snap connect discord:discord-ipc
Flatpak	Needs override	flatpak override --user --filesystem=xdg-run/discord-ipc-0 com.discordapp.Discord

Common Issues

Do Not Run Discord as Root
IPC sockets won't be accessible. Always start Discord as regular user (never sudo).

XDG_RUNTIME_DIR Issues

# Check if set correctly
echo $XDG_RUNTIME_DIR
ls -la $XDG_RUNTIME_DIR

# If not set, add to ~/.bashrc:
export XDG_RUNTIME_DIR=/run/user/$(id -u)

Wayland Users
Install xdg-desktop-portal:

sudo apt install xdg-desktop-portal xdg-desktop-portal-gtk  # Debian/Ubuntu
sudo pacman -S xdg-desktop-portal xdg-desktop-portal-gtk    # Arch
sudo dnf install xdg-desktop-portal xdg-desktop-portal-gtk  # Fedora

Manual Socket Check

# Check if Discord IPC socket exists
ls -la $XDG_RUNTIME_DIR/discord-ipc-0
ls -la $XDG_RUNTIME_DIR/snap.discord/discord-ipc-0      # Snap
ls -la $XDG_RUNTIME_DIR/app/com.discordapp.Discord/     # Flatpak

# Socket should be owned by your user (not root)