Wowza SSL Streaming Tutorial: How to Stream with SSL on Shoutcast Net (No Per-Viewer Pricing)

If you’ve been running a Wowza workflow and you’re trying to get SSL/TLS (HTTPS) streaming working reliably—without surprise bills—this guide walks you through a clean, broadcaster-friendly alternative: Shoutcast Net. You’ll learn how to enable SSL endpoints, configure your encoder, and update your website player links so your listeners stop seeing “Not Secure” warnings in Chrome and mobile browsers.

Most importantly, you’ll move from Wowza’s expensive per-hour/per-viewer pricing model to a flat-rate plan built for radio DJs, podcasters, churches, schools, and live event streamers—while keeping modern requirements like SSL streaming, unlimited listeners, and 99.9% uptime.

Best for

24/7 radio, podcasts, worship streams, campus radio, events

What you’ll set up

HTTPS/SSL stream URL, encoder settings, player link updates

Start here

Grab a plan from the shop or use the 7 days trial

Planned steps:

  • 1) Why SSL matters (and why broadcasters leave Wowza)
  • 2) Choose Shoutcast/Icecast and the right plan
  • 3) Get an SSL certificate
  • 4) Enable SSL/TLS on your stream endpoint
  • 5) Configure your encoder for HTTPS
  • 6) Update your player links and test on mobile/Chrome

Why SSL streaming matters (and why people leave Wowza)

SSL streaming (TLS/HTTPS) is no longer optional. Modern browsers, mobile OSes, and embedded players increasingly block or warn users when media loads over non-secure HTTP. That means you can have a great show—yet lose listeners because the page looks unsafe, autoplay fails, or the player refuses to connect.

What SSL fixes for broadcasters

  • Removes “Not Secure” warnings in Chrome/Safari when your website is HTTPS
  • Prevents mixed-content blocking (HTTPS website trying to load an HTTP stream)
  • Improves compatibility with mobile browsers and in-app webviews
  • Builds trust for churches, schools, and donation-supported stations

Why broadcasters leave Wowza for SSL streaming

Wowza can be powerful, but many broadcasters hit the same wall: billing complexity. If you’re streaming live events, weekly services, or sports, you don’t want to calculate costs by the hour or worry about spikes in viewers. Wowza’s per-hour/per-viewer style pricing often becomes expensive at exactly the moment your audience grows.

Shoutcast Net focuses on the needs of internet radio and always-on broadcasters with a simpler model: flat-rate plans built for unlimited listeners, stable uptime, and straightforward SSL endpoints—so you can spend your time programming, not forecasting invoices.

Feature Typical Wowza-style billing Shoutcast Net approach
Cost structure Often per-hour/per-viewer (can rise fast during peaks) Flat-rate, predictable monthly pricing
SSL streaming Possible, but can require extra configuration and adds cost complexity SSL streaming on supported endpoints with simple setup
Radio-first tooling Generic streaming platform Built for DJs/stations with AutoDJ options
Scaling listeners Cost increases can punish growth Unlimited listeners on flat-rate plans

Pro Tip

If your website is already HTTPS (most are), you should treat SSL streaming as mandatory. The fastest “win” is swapping every http:// stream URL in your site/player to the secure https:// stream endpoint provided by Shoutcast Net.

One more note: Wowza often gets discussed with “do anything” workflows—like “stream from any device to any device” or even “any stream protocols to any stream protocols (RTMP, RTSP, WebRTC, SRT, etc)”. Those are great capabilities for complex video distribution, but most audio broadcasters need something different: reliable, browser-friendly, always-on audio streaming with SSL, simple encoders, and predictable cost.

Choose Shoutcast/Icecast and the right plan (flat-rate from $4/mo)

Before you touch certificates or encoder settings, decide which streaming server type you need: Shoutcast or Icecast. Both work well for audio streaming and both can be delivered securely over HTTPS. The “right” choice usually depends on your player ecosystem, metadata needs, and your station workflow.

Shoutcast vs Icecast: quick selection guide

You are… Recommended Why
A radio DJ or music streamer using standard radio tools Shoutcast hosting Classic radio compatibility, easy listener URLs, strong metadata support
A podcaster or multi-mount broadcaster who wants flexible mountpoints Icecast Flexible mount structure and broad software support
A church/school station that needs “set-and-forget” 24/7 playback Either + AutoDJ AutoDJ keeps you on-air even when no one is live

Pick a plan that matches your real-world use (not peak panic)

With Wowza-like pricing, you can end up “afraid” of success because more listeners can mean more cost. Shoutcast Net is designed to remove that fear with a flat-rate unlimited model—starting at $4/month—plus a 7 days trial so you can validate SSL streaming end-to-end before committing.

  • Starting price: $4/month (flat-rate approach)
  • Uptime: 99.9% uptime target for consistent delivery
  • Listeners: unlimited listeners on flat-rate plans
  • Features: SSL streaming, optional AutoDJ

To get started, choose your server type and plan in the shop (or activate the 7 days trial first).

Pro Tip

If you run weekly live shows (church services, school sports, DJ nights), consider pairing your stream with AutoDJ. It keeps your mount live 24/7, helps players stay connected, and avoids “dead air” when the live encoder disconnects.

If you also do social distribution, you can still run your audio stream as the “source of truth” and Restream to Facebook, Twitch, YouTube using your production setup while keeping Shoutcast Net as the stable, SSL-secured listener endpoint.

Get an SSL certificate (Let’s Encrypt or your own cert)

To stream over HTTPS, your stream endpoint needs a valid SSL certificate. In most cases, this is handled for you at the platform layer (the best experience). If you’re using a custom domain (recommended for branding), you’ll typically use either Let’s Encrypt or upload your own certificate.

Option A: Let’s Encrypt (recommended for most stations)

Let’s Encrypt is free, trusted by browsers, and renewable. It’s ideal for broadcasters who want secure endpoints without managing renewals manually.

  • Pros: free, automated renewal, widely trusted
  • Cons: requires DNS/domain control; some workflows need validation steps

Option B: Use your own certificate (business/enterprise workflows)

If your organization already has a certificate provider (common for schools/churches/enterprises), you can use your own cert—just ensure it’s valid for the hostname your listeners will use.

  • Pros: centralized org policy, custom validation, extended support options
  • Cons: you’re responsible for renewal and certificate chain correctness

Certificate checklist (avoid the 3 most common SSL failures)

  • Hostname match: certificate must match the exact domain listeners use (e.g., stream.yourstation.com)
  • Full chain: include intermediate certificates (prevents “works on desktop, fails on mobile” issues)
  • Renewal plan: don’t let certs expire before a big event
# Quick sanity checks (your admin team can run these)
# 1) Does the certificate match the hostname?
# 2) Is the chain complete?
# 3) Does the endpoint negotiate TLS correctly?

# Example (OpenSSL):
openssl s_client -connect stream.yourstation.com:443 -servername stream.yourstation.com

Pro Tip

If you’re migrating off Wowza, don’t try to replicate every “media server” feature. Focus on what listeners experience: a secure HTTPS stream URL that loads instantly on mobile and in Chrome—then add advanced workflow pieces (like social restreaming) around it.

Once your certificate approach is decided, you’re ready to enable SSL/TLS on the Shoutcast Net endpoint and generate the correct secure listener URLs.

Enable SSL/TLS on your Shoutcast Net stream endpoint

This step is where your stream becomes “browser-friendly.” The goal is simple: ensure you have a working https:// listener URL (and, where supported, a secure admin/management endpoint). Shoutcast Net’s infrastructure is designed to provide SSL streaming without turning it into a per-viewer cost problem.

Step 1: Provision your stream server

Choose either Shoutcast hosting or Icecast and activate your plan from the shop (or start with the 7 days trial).

Step 2: Locate your secure stream URL(s)

In your service details, you’ll typically see one or more listener URLs. What you want to use on your site and in apps is the HTTPS version. Your URLs usually look like one of these patterns:

# Examples (your exact host/port/mount will differ)

# Shoutcast-style:
https://your-hostname:PORT/stream

# Icecast-style mount:
https://your-hostname:PORT/mountname

# Playlist endpoints (often used for players):
https://your-hostname:PORT/stream.m3u
https://your-hostname:PORT/stream.pls

Important: Some older “legacy Shoutcast limitations” discussions online revolve around older players, older ports, and non-SSL defaults. The modern fix is straightforward: use the platform-provided HTTPS endpoints and update players/links everywhere you publish.

Step 3: Confirm TLS works before changing your website

Before you update your player, validate the secure URL in a browser on both desktop and mobile. If the endpoint loads and begins playback (or downloads a playlist file), your SSL path is working.

  • Open the https:// stream URL directly in Chrome
  • Test a playlist link (.m3u or .pls) if your player uses it
  • Test on mobile data (not just Wi‑Fi) to mimic real listeners

Pro Tip

If you’re used to Wowza’s “do everything” approach—like “stream from any device to any device” and “any stream protocols to any stream protocols (RTMP, RTSP, WebRTC, SRT, etc)”—keep that for your production pipeline if needed. For listener delivery, a stable HTTPS audio endpoint is the simplest, most compatible solution.

After SSL is confirmed on the listener side, you’re ready to configure your encoder. Note that encoders usually send audio to the server over a source protocol (not always HTTPS). Listeners, however, should consume your stream over HTTPS for maximum compatibility.

Configure your encoder (BUTT/Mixxx/RadioDJ/OBS) for HTTPS

Your encoder setup has two jobs: (1) send audio to your Shoutcast/Icecast server reliably, and (2) maintain consistent metadata (artist/title, show name, etc.). Many broadcasters confuse “SSL streaming” with “encoder must connect via HTTPS.” In practice, listeners must connect over HTTPS; your encoder typically connects to a server/port/password using the server’s source connection method. You still benefit from SSL because your published player links are HTTPS.

Before you start: collect these details

  • Server address: hostname or IP from your Shoutcast Net service
  • Port: source port provided in your service details
  • Password: source/admin password (keep private)
  • Mount/stream name: (Icecast mount or Shoutcast stream path)
  • Codec/bitrate: MP3/AAC, 64–320 kbps depending on audience

BUTT (Broadcast Using This Tool) setup

BUTT is popular for DJs and churches because it’s lightweight and stable. Create a new station profile and choose the correct server type.

# Typical BUTT settings (example)
Server Type: Shoutcast or Icecast (match your plan)
Address: your-hostname
Port: your-source-port
Password: your-source-password
Mountpoint (Icecast): /live (example)
Codec: AAC+ or MP3
Bitrate: 128 kbps (common starting point)

Mixxx setup (DJ + live mixing)

Mixxx includes built-in broadcasting. Select your server type (Icecast or Shoutcast), then enter the host/port/password and mount (Icecast). Confirm your audio format matches your station requirements.

# Mixxx Broadcast (example fields)
Type: Icecast 2 or Shoutcast
Host: your-hostname
Port: your-source-port
Login: source (Icecast, often "source")
Password: your-source-password
Mount: /stream (Icecast example)
Format: MP3 or Ogg/AAC (depending on server support)
Enable Metadata: Yes

RadioDJ + encoder (24/7 automation)

RadioDJ commonly pairs with an external encoder (like BUTT or AltaCast). The key is ensuring your encoder runs continuously and reconnects automatically. If you use AutoDJ, you can keep music running even if your live encoder drops.

  • Enable auto-reconnect in your encoder
  • Set a sensible buffer to prevent network hiccups from dropping the stream
  • If using AutoDJ, configure live takeover correctly (so live overrides AutoDJ)

OBS (events, churches, and “studio-to-social” workflows)

OBS is great for live video, but many broadcasters use it as a central mixer for audio too. If your goal is audio streaming to listeners plus social distribution, a practical workflow is:

  • Use OBS to produce your program (audio/video)
  • Send your audio stream to Shoutcast Net for stable, SSL-secured listening
  • Restream to Facebook, Twitch, YouTube for discovery and live chat

If you need “very low latency 3 sec” for a specific interactive event, keep in mind that ultra-low latency is usually tied to specialized protocols and player support. For most radio and talk formats, stability and compatibility matter more than shaving seconds—especially when you want every phone/browser to play cleanly over HTTPS.

Pro Tip

Do a “two-device test”: run your encoder from one device (laptop/studio PC) and listen from another (phone on cellular). That’s the fastest way to confirm you can stream from any device to any device without local-network false positives.

Once your encoder is connected and stable, the final step is updating every player and link to use HTTPS—otherwise your website may still trigger mixed-content issues.

Update your website player links and test on mobile/Chrome

This is the step that makes SSL streaming “real” for your audience. Even if your stream supports HTTPS, your listeners won’t benefit until every embed, link, app config, and playlist file reference is updated from http:// to https://.

Step 1: Replace stream URLs everywhere

Search your website (and any mobile app config) for your old stream URL and update it to the secure endpoint. Common places to check:

  • Website HTML audio player or JavaScript player config
  • WordPress radio/player plugins
  • “Listen Live” button links
  • M3U/PLS playlist links shared on social media
  • Embedded players inside donation or event pages (often forgotten)
<!-- Example: HTML5 audio tag using HTTPS -->
<audio controls preload="none">
  <source src="https://your-hostname:PORT/stream" type="audio/mpeg">
  Your browser does not support the audio element.
</audio>

Step 2: Test for mixed content in Chrome

In Chrome, open your site and press F12 (Developer Tools). Look for “Mixed Content” warnings. If your page is HTTPS but the stream URL is HTTP, Chrome may block it or downgrade the experience.

Step 3: Mobile tests that actually catch real problems

  • iPhone Safari: open your site, press play, lock the screen, confirm audio continues (if supported)
  • Android Chrome: test on both Wi‑Fi and cellular
  • In-app browsers: test from a link clicked inside Instagram/Facebook (they behave differently)

Step 4: Confirm metadata and fallback behavior

Listeners notice when song titles are wrong or when silence happens after a disconnect. Confirm:

  • Artist/title updates correctly (for music streamers)
  • Your “Now Playing” widget points to the same HTTPS stream endpoint
  • AutoDJ takes over when live disconnects (if enabled)

Pro Tip

Keep both a direct HTTPS stream URL and an HTTPS playlist URL (M3U/PLS) published. Some players prefer playlists for reconnection logic, while browsers often play the direct stream link more easily.

What you gain by switching from Wowza to Shoutcast Net for SSL streaming

When your SSL endpoints are live and your players are updated, you get the practical benefits broadcasters care about: fewer listener drop-offs, easier sharing, and predictable cost.

  • Flat-rate pricing (no per-hour/per-viewer surprises like Wowza)
  • $4/month starting plans built for broadcasters
  • 7 days trial so you can test SSL playback end-to-end
  • 99.9% uptime target for reliability
  • SSL streaming to satisfy modern browser requirements
  • Unlimited listeners on flat-rate plans so growth is welcomed
  • Optional AutoDJ for true 24/7 stations

Ready to set it up? Choose your plan via the shop or start your 7 days trial. If you’re deciding between server types, compare Shoutcast hosting and Icecast, then lock in your HTTPS stream URL and update your player links.

Recap: SSL streaming success comes down to three things: a valid HTTPS endpoint, an encoder that stays connected, and player links that use HTTPS everywhere. Do that, and you’ll have a secure stream that works in Chrome and on mobile—without Wowza’s expensive per-hour/per-viewer billing.