Author Topic: Recv failure: Connection reset by peer  (Read 3765 times)

buckinspire

  • Newbie
  • Posts: 2
Recv failure: Connection reset by peer
« on: August 14, 2013, 04:24:13 pm »
I am trying to verify any mp3 file and I get this error.  Size is not the issue.  My webhost said it's a problem with the plugin.  I reinstalled it with the same error.  I looked at other podcasts and the file has numbers and the duration.  Does anyone know how to fix the issue or generate the random number string to help me add it in manually?  Thanks in advance!

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Recv failure: Connection reset by peer
« Reply #1 on: August 15, 2013, 01:10:52 pm »
Please share the URL to the media file so we can test.


angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Recv failure: Connection reset by peer
« Reply #3 on: August 15, 2013, 09:15:58 pm »
I just tested the URL (http://buckinspire.com/wp-content/uploads/podcast/soldier_of_finance_jeff_rose.mp3) with Firefox using the HTTP Live Headers plugin, it duplicates the same behavior iTunes and PowerPress does. I also got a "couldn't connect to host" error.

Send this link to your "webhost" (http://create.blubrry.com/manual/internet-media-hosting/ ), tell them the server needs to be COMPLETELY HTTP/1.1 COMPLIANT. If they don't fix the issue then you should go else where for your hosting.

null2099

  • Newbie
  • Posts: 1
Re: Recv failure: Connection reset by peer
« Reply #4 on: August 20, 2013, 11:49:28 am »
After uploading several podcasts successfully I am getting this same error as well. What might have changed? I am using iPage as a host.

http://www.thejaguarandtheowl.com/Podcasts/thejaguarandtheowl_episode05.mp3

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Recv failure: Connection reset by peer
« Reply #5 on: August 20, 2013, 12:10:32 pm »
Contact your web host!

A lot could have changed. Here are 3 examples, of hundreds of reasons why this could be happening...

1. Server administrator setup a firewall and is blocking outbound requests
2. Local server DNS is not resolving the host name where you're hosting you rmedia to localhost (127.0.0.1)
3. Someone installed mod_security and configured it to block many of the HTTP/1.1 protocol methods that iTunes requires.

You have three options:

1. Contact your web host to fix the problem.
2. Leave your web host
3. Host your media on a different infrastructure specifically designed for podcasting (like Blubrry Media Hosting).