Wowza CURL HTTP Code not 200, returned 401

Issue
Statistics Parser Error:: CURL HTTP Code not 200, returned 401


Cause
This issue occurs when the "AdminUserPass" in MediaCP -> Configuration -> Plugins is configured incorrectly and does not match the username and password of Wowza Media Server.
Steps to Resolve:
The Wowza Stream Manager Password is stored in [WowzaInstallDir]/vhosts/default/conf/admin.password.
It is important that your MediaCP is configured with the same username and password.
  1. Login to the MediaCP and navigate to Administration -> Configuration -> Plugins.
  2. Locate the setting for Wowza called AdminUserPass.
  3. The AdminUserPass should be set in the following format: "username:password"
    For example: "admin:mylongpassword"

  4. If you change the password in the admin.password file, you MUST restart Wowza Media Server before this takes affect.
Important Note: Your the username or password must NOT contain a colon (":"), if it does - replace this with any other character.
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Troubleshooting Facebook Stream Targets (NGINX-RTMP)

Troubleshooting steps for facebook stream target disconnect. Check abuse log to ensure no...

Stream Target is not working or stuck on Starting

If the status is stuck on Starting it likely means that Wowza is having difficulties connecting...

Do i need to reinstall Wowza Media Server?

Our installation software will install a fresh version of the very latest Wowza Media Server...

iPhone Video & Audio Streaming

For Audio/Video Streaming to an iPhone, we find a Baseline 3.1 (not lower) profile is required....

Sam Broadcaster Statistics - How to configure

Overview The MediaCP Wowza Edition supports the Statistic relay of SAM Broadcaster. (Only...