obsproject / obsproject/obs-studio

Mandatory Protocol Entry Leads to Confusing 'Invalid Path or URL' Error during Server Configuration

Open
#9,399 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

29.1.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/8ObhxOKOASFDx1dl

OBS Studio Crash Log URL

No response

Expected Behavior

Users would anticipate successful server connection and streaming initiation without encountering any errors when leaving the protocol field blank during server configuration.

Current Behavior

When attempting to begin a livestream after configuring server settings with an address lacking a protocol entry (e.g., 192.168.182.1:11451), the software seemingly fails to establish a connection. Instead, an immediate error message pops up, indicating "Invalid path or URL. Please review your settings to ensure their validity."

Steps to Reproduce
  1. Open the OBS application.
  2. Navigate to "File" > "Settings" > "Livestream."
  3. Enter an address in the server field without specifying a protocol (e.g., 192.168.182.1:11451).
  4. Save the settings.
  5. Attempt to initiate a livestream by clicking "Start Streaming."
  6. Instead of attempting a connection, the software instantaneously displays the error message: "Invalid path or URL. Please review your settings to ensure their validity."
Anything else we should know?

I am using the Chinese version of OBS, so the names of operations and prompts are translated and may not align precisely with those in the English version of OBS.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in OBS Studio at File > Settings > Livestream and reproduce the issue with 192.168.182.1:11451, using the linked OBS log for context. Trace the server URL validation and connection-start path; done means the behavior for an address without a protocol is intentional and clearly reported, or the connection proceeds as specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.