Author Topic: `The requested URL returned error: 403` - Increase logging to discover problem?  (Read 1728 times)

gpsonet

  • Newbie
  • Posts: 2
I'm having an issue with a customer where they have started having problems with `The requested URL returned error: 403` upon pressing the Verify button.  Oddly it seems as though no one has done anything wrong or amiss with the configuration.  Disabling the cache, reverting .htaccess, and so forth all yield no success.  Apache DOES have byte-range support enabled for this server, yet I am wondering if something with WP or the plugin is screwing up and causing this problem.

Unfortunately neither the Apache error log nor the debug.log that I enabled with full verbosity give any specific information / details when I trigger this error.  Is there a way to increase verbosity for logging for PowerPress that will allow me to pinpoint the real error that is going on here?

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
There is a lot more to it than just byte serving. Read here: http://create.blubrry.com/manual/internet-media-hosting/

e.g. server is most likely blocking HEAD requests for what ever reason (read link above).

Also happens with podcast feeds, read last section at bottom of this page: http://create.blubrry.com/manual/syndicating-your-podcast-rss-feeds/podcast-feed-validator/solving-issues-with-your-feeds/