Skip to main content

How to Fix: OBS Stops Streaming After Closing RDP

Keep OBS streaming after you close RDP — use a VNC session so your stream survives disconnects.

OBS (Open Broadcaster Software) is a powerful tool for livestreaming, but it doesn't always behave as expected on VPS environments when accessed over Remote Desktop Protocol (RDP). If your live stream cuts off the moment you disconnect from your VPS, this guide will help you understand why — and show you how to fix it using TightVNC.


Why OBS Stops Streaming When You Close RDP

When you connect to your VPS using RDP, Windows dynamically creates virtual GPU and audio devices to support your session. OBS relies on these virtual devices to capture and stream your content.

However, as soon as the RDP session ends, Windows assumes those resources are no longer needed and removes them — a process known as session cleanup or garbage collection. Since OBS was using these RDP-created devices, the stream drops or stalls immediately.


The Solution: Use TightVNC Instead

Unlike RDP, TightVNC doesn't rely on virtual graphics devices or session-dependent drivers. It operates by transmitting raw screen data and input commands over the network, so the screen session — and OBS — continue functioning normally even after you close the connection.


Part 1: Install TightVNC on Your VPS

  1. Download TightVNC Server

  2. Install TightVNC Server

    Run the installer and choose Complete Setup when prompted.

  3. Proceed through Setup Wizard

    Click Next until you reach the Install button. Click to install.

  4. Set Access Password

    After install, you'll be prompted to enter a password. Set a strong password and click OK.

  5. Complete Installation

    Click Finish to finalize setup.

  6. Verify Running Status

    Look for the TightVNC icon in the system tray (bottom-right corner of your VPS). If it's visible, the service is running.


Part 2: Install RealVNC Viewer on Your Local Computer

  1. Download RealVNC Viewer

  2. Install the Viewer App

    Follow the prompts and click Install.

  3. Finish Installation

    Click Finish to close the wizard.

  4. Launch RealVNC Viewer

    Find it in the Start Menu or under "Recently Added."

  5. Skip Sign-In

    On first launch, uncheck Send anonymous usage data. Then click:

    Use RealVNC Viewer Without Signing In

  6. Connect to Your VPS

    In the address bar, enter your VPS's own public IP address followed by :5900 — use the actual public IP of your VPS (found in your QuantVPS dashboard), not a private/LAN-style address.

    Example: <Your-VPS-Public-IP>:5900

  7. Connect and Enter Password

    Hit Enter and provide the password you set earlier in TightVNC.


Security: Locking Down Port 5900

Don't leave VNC open to the whole internet. Port 5900 (and TightVNC/RealVNC in general) were not designed with the same security hardening as RDP. If you expose port 5900 to all inbound traffic, it becomes a target for scanners and brute-force login attempts. Before you rely on this setup long-term:

  • Firewall it to trusted IPs only. In your VPS's Windows Firewall (and/or your QuantVPS network firewall, if applicable), restrict inbound access on port 5900 to only the specific IP address(es) you'll be connecting from — not "Any."

  • Use a strong, unique password for the TightVNC server — not something short or reused from another account.

  • Prefer tunneling over exposing the port directly. Where possible, tunnel your VNC connection through SSH or a VPN instead of exposing 5900 directly to the internet — this adds a layer of authentication and encryption VNC doesn't provide on its own.

  • If you no longer need remote VNC access, disable the TightVNC service or close the port again rather than leaving it open indefinitely.


Part 3: Configure OBS to Run Outside RDP

  1. First-Time Setup in RDP (One-Time Only)

    Log in via RDP and install + configure OBS on your VPS.

  2. Link Your Streaming Platform

    Set up your streaming account (YouTube, Twitch, etc.) inside OBS.

  3. Add a Source

    • Go to Sources → + (Add) → Window Capture

    • Give it a name and click OK

  4. Select the Window You Want to Stream

    Choose from the dropdown (e.g., browser, charting app).

  5. Click OK to confirm capture settings.

  6. Test Your Stream

    Preview the stream on your broadcasting platform in a browser.


How to Keep OBS Streaming After RDP Disconnect

Once OBS is fully configured and you've confirmed the stream is live:

  1. Disconnect from RDP

  2. Reconnect to the VPS using TightVNC instead

  3. If OBS shows a blank screen, click Stop Streaming then Start Streaming again

  4. Verify the stream is active on your browser

  5. Once confirmed, you may close TightVNC — OBS will continue running


TightVNC is Free to Use

TightVNC is open-source and licensed under the GNU GPL. You can use it commercially or privately without any cost. More on TightVNC licensing


Summary

RDP

TightVNC

Disconnecting ends stream

Stream continues after exit

Relies on virtual GPU/audio

Works independently of RDP

Great for setup

Great for persistent streaming


Need Assistance?

Our support team is available 24/7. If you have any questions or run into issues, open a support ticket from your QuantVPS dashboard and we'll get back to you as quickly as possible.

Did this answer your question?