Installing OBS on a Contabo VPS involves two separate jobs: installing the software, then confirming that the VPS has a working graphics and display environment in which OBS can run. SSH access lets you manage the server, but it does not establish that environment or prove the server can encode a continuous stream.
For a single-file loop, OBS can repeat a local video through a Media Source and send it to YouTube Live. Before you follow the interface steps below, check your Ubuntu release, display access, graphics support and ability to sustain the stream settings you intend to use.
What the setup requires
You need a Contabo VPS running an Ubuntu release for which the OBS installation route is currently supported, a working graphical display environment, the video file you want to loop, and a YouTube channel enabled for live streaming. You also need a way to open OBS in that display environment and enough compute and network capacity for the chosen video and encoding settings.
These are related but different requirements. A package manager can install OBS even if the session you have opened is not able to display its interface. Likewise, a desktop appearing through remote access does not establish that its graphics support or available CPU can handle your chosen resolution and frame rate. Treat package installation, graphical access and sustained encoding as separate checks.
A VPS is useful when you want the broadcast process to continue without leaving your personal computer switched on. It also makes you responsible for checking the server image, updates, display session and behaviour after a disconnect or reboot. If your goal is to schedule different videos rather than repeat one file, the trade-offs are different; see cloud services that schedule a YouTube playlist.
Check the VPS operating system and package support
Start by confirming the operating system and release in the Contabo control panel or in your server session. Do not assume that an Ubuntu instruction applies to every image, or that a package route documented for an older release will work unchanged on a newer one. OBS's Linux installation guide describes an Ubuntu route for Ubuntu 18.04 or newer, but its published guide dates from 2021. Check the current guidance and package support for the specific release you are using before making changes: OBS's Linux installation guide.
The same guide recommends Flathub for distributions other than Ubuntu. That distinction matters: the Ubuntu PPA route below is not a universal Linux recipe, and adding Ubuntu repositories to another distribution is not a safe substitute for checking its own instructions. If the VPS image is not Ubuntu, stop and follow the current OBS guidance for that distribution.
Also identify whether the VPS image includes a desktop session or only a command-line environment. A server that accepts SSH connections may be functioning exactly as configured, while offering no desktop in which to open OBS. Check the image description and Contabo's documentation for the access options attached to your instance. Contabo describes VPS plans and their resources on its VPS documentation page; plan details and available images can change, so verify the current listing rather than relying on an old tutorial.
Do this review before installing packages. If you discover that the chosen image lacks a supported desktop or that the graphics arrangement is unclear, resolve that first with Contabo's current documentation or support. A package installed into a command-line image does not by itself create a usable display session.
Install OBS on Ubuntu by the documented route
On an Ubuntu VPS, use the Ubuntu instructions in OBS's official guide as the reference for adding its PPA and installing through apt. Read the commands on the current page and check that they match your Ubuntu release before running them. This is the documented Ubuntu route, not a guarantee that every Contabo image, release or package state will behave identically.
The broad sequence is to update package information, add the OBS repository as directed by OBS, update the package list again, and install OBS Studio with apt. Use the exact repository and package commands from the current official page rather than copying a command from a different distribution or an old forum post. If the repository does not support your release, stop and resolve the package-source question before proceeding; do not force packages from another Ubuntu version.
Once installation completes, confirm that the package manager reports no unresolved errors. Then try to launch OBS from the graphical session you intend to use. This is a meaningful check that the application opens in that session, but it is not a sustained-load test and does not show that the stream can run unattended. Keep the distinction clear: package installation answers whether the software is present, not whether the whole broadcast arrangement is ready.
If you are comparing a local OBS workflow with other ways to send prerecorded material to YouTube, the practical differences are worth reviewing before committing. A comparison of free software for continuous prerecorded YouTube streams can help you decide whether OBS is the right fit for the job rather than simply the tool you happened to find first.
Understand graphics and display access
OBS's Linux system requirements include an OpenGL 3.3-compatible GPU and an X window system or Wayland. The OBS Project also cautions that meeting basic requirements does not guarantee that a machine is capable of streaming or recording. Encoder choice, resolution, frame rate and scene complexity all affect the work the system must do. Read OBS's system requirements and compare them with the actual VPS image and resources, rather than treating the OBS package's presence as proof of compatibility.
SSH is a remote command-line connection. It is useful for administration, but it is not a graphical display and does not show that an X or Wayland session exists. Running a graphical application from a shell may produce display-related errors if no suitable display is configured. Do not infer from a successful SSH login—or from a command completing—that OBS has a usable interface or graphics support.
Contabo documents remote VNC access, with instructions that include enabling VNC, rebooting, retrieving current credentials and connecting through a VNC client. Follow its current VNC connection instructions. VNC is a way to reach a display; it does not prove that the server image has a desktop installed, that the display session is configured for OBS, or that the graphics requirements are met. If you see a desktop, check that OBS opens there and that the environment provides the graphics support it needs.
Do not assume a standard VPS and a GPU VPS are interchangeable, or that a GPU offering is automatically necessary for a simple loop. The relevant question is whether the particular instance's display and compute arrangement can run your intended OBS scene and encoder. Contabo has announced GPU VPS products, but an announcement is not a benchmark for your workload or a guarantee of continuous operation. Check current vendor specifications and costs directly if comparing plans; do not select one based only on a headline specification.
If your available server has no suitable display route, you may be better served by a workflow designed for command-line streaming, or by a service that runs the uploaded file without your maintaining an OBS desktop session. That is a practical fit decision, not a claim that one approach is always more reliable. StreamNeo removes the need to keep your own computer and OBS session open by turning an uploaded video into a YouTube broadcast that runs independently of your desktop.
Configure OBS to loop and send a YouTube stream
Once OBS opens in the intended display session, create a scene for the broadcast and add a Media Source. Choose the local video file and enable the source's Loop option so playback starts again when it reaches the end. OBS explains the Media Source and related options in its media sources documentation. Check that the file is accessible to the account running OBS; a path on your own computer is not automatically available on the VPS.
For more than one file, OBS offers a VLC Video source with a playlist-loop option, and VLC must be installed for that source. A single Media Source is simpler when one prepared video should repeat; a VLC playlist is more appropriate when the broadcast should move through several files. Review the source settings after adding content, because a blank source, wrong file path or unintended playback setting can leave a scene that looks ready in the editor but does not play as expected in the stream.
| Approach | Best fit | What to check |
|---|---|---|
| Media Source with Loop | One local video repeated | File path, playback and audio at the loop point |
| VLC Video with Loop Playlist | Several files played as a repeating playlist | VLC availability, playlist order and transitions |
Set up the YouTube output in OBS using the current YouTube Live encoder instructions. For a routine SDR loop where you want to keep latency lower, RTMPS is the sensible default. YouTube recommends RTMPS, constant bitrate (CBR) encoding and a two-second keyframe interval; its guidance says not to exceed four seconds. Choose a resolution and bitrate that your instance and network can sustain, rather than assuming that the highest available setting is the best choice. See YouTube's encoder settings guidance for current requirements and recommendations.
Treat the stream key as a credential. Paste it into the appropriate OBS field, but do not include it in a public screenshot, shared log or support post. If YouTube rejects the key or OBS does not connect, check the selected service, key and YouTube control room before changing unrelated encoding options. The stream key troubleshooting guide for a 24/7 music channel covers common credential and connection checks.
HLS is another YouTube-supported ingest route, but it is not simply a different label for RTMPS. YouTube's HLS setup involves selecting the HLS stream key and URL and meeting its segment and rolling-playlist requirements. HLS has higher latency than RTMP, so for a straightforward loop it is usually worth choosing only when you have a specific reason to use it. Consult YouTube's HLS ingestion guidance if that route is required.
Plan for unattended operation and persistence
A stream that works while you are watching the desktop is not yet an unattended setup. Decide what should happen if OBS closes, the display session ends, the server reboots or the network connection drops. OBS's installation and scene settings do not answer those operational questions by themselves. You need to understand how your chosen desktop session starts, how you will regain access to it, and what recovery steps are available on this particular VPS image.
Before relying on a long run, confirm where the video file and OBS profile are stored, which account owns them, and whether they remain accessible after a reboot. Keep a copy of the scene and output settings somewhere private so you can restore them if needed. Do not store a stream key in a public script, screenshot or shared notes. If a key has been exposed, use YouTube's current controls to replace it and update OBS.
Think through a real interruption, not just the ideal launch. After a planned reboot, can you reconnect to the display and find OBS in the intended state? If the desktop session disappears, do you know whether OBS is still running, stopped, or waiting for a display? Do not assume a particular answer without checking the behaviour of your image and session. A guide to restarting a 24/7 stream after a power cut is useful for thinking about recovery, although a VPS reboot and a household power cut are not identical failure cases.
Be realistic about what must be monitored. YouTube's stream health can reveal ingest warnings, while the remote display lets you inspect OBS itself. Decide who will check those signals and what they will do if a warning appears. If you cannot inspect or recover the chosen setup when it fails, an unattended process may be a poor match even if you can start it successfully once.
Test the server before relying on it
Use a representative test before leaving the stream unattended. Include the actual video and audio, the scene complexity, resolution, frame rate and encoding settings you expect to use. Let playback pass through a loop point so you can check whether video and sound resume as intended. If the stream includes spoken introductions, changing images or music, test those parts too; a static test frame does not represent the same workload or content behaviour.
Check the picture and sound on YouTube, not only in the OBS preview. Confirm that the broadcast reaches the intended channel, that the file repeats correctly, and that the audio is audible and in sync. Watch the stream-health indicators and read any warnings rather than assuming that a visible preview means the ingest is healthy. YouTube advises testing before going live and monitoring stream health during the event in its encoder guidance.
A short successful test still cannot establish how the instance behaves over an extended run. If you intend to operate continuously, observe a representative period and inspect what happens after a planned reboot or reconnect before treating the process as dependable. Do not extrapolate performance from a different Contabo plan, display image or encoder setting. The exact VPS configuration, target resolution and sustained capacity are specific to your setup.
Keep a simple record of the settings that worked, the file used, any warnings and the recovery steps you verified. If you change the scene, file, encoder, display arrangement or stream key later, repeat the checks that those changes could affect. The goal is not to prove that a VPS can never fail; it is to know what your current setup does and how you will notice and respond when it needs attention.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can I install OBS on a Contabo VPS using SSH?
You can use SSH to administer Ubuntu and follow the package installation steps, but SSH alone does not provide OBS with a graphical display. Check for a supported X or Wayland environment and graphics capability, then launch OBS in the display session you intend to use.
Does Contabo VNC mean OBS will work?
No. VNC provides remote access to a display, but it does not prove that your image contains a desktop or that OBS's graphics requirements are met. Enable and connect to VNC using Contabo's current instructions, then verify the display and OBS on your actual instance.
Should I use RTMPS or HLS for a YouTube loop?
For a routine SDR loop, RTMPS is the usual starting point because YouTube recommends it and HLS has higher latency. HLS has different URL, key and playlist requirements, so use it when your workflow has a reason to do so and follow YouTube's current setup guidance.
Is a GPU VPS required to repeat one video?
The research and official requirements do not establish that a GPU VPS is required for every simple loop. The necessary capacity depends on the specific graphics environment, encoder, resolution, frame rate and scene, so test the instance you plan to use rather than treating a product label as proof of fit.