302 error on PHP 5.4.13

Do you have open_basedir restrictions on your server?

This can affect the correct operation of the cURL functionality used by this plugin.

Do you have open_basedir restrictions on your server?

This can affect the correct operation of the cURL functionality used by this plugin.

Hello,

Thanks for your reply. Here is my host manager’s reply:

So safe_mode was depreciated a while ago in PHP, and actually does not exist in recent supported versions like we run. open_basedir is set to .../httpdocs/:.../tmp/. What this does is gives you access to PHP’s /tmp/ folder, where it stores things like files you have uploaded, and to the entire /httpdocs/ directory of the website. This is the standard setting for open_basedir. Can you ask them specifically what directory they need access to that is outside of the httpdocs folder?

I can not simply disable this setting. If the site was compromised, it would give the attacker access not only to your site, but every single other one (since he would not be limited to httpdocs). Disabling it is a highly unusual request. I would not be surprised if your problem lies elsewhere. You would be hard pressed to find a host that will do this for you, unless you get a server dedicated for your site like a VPS or similar.

Basically your server is for some reason ignoring the CURLOPT_FOLLOWLOCATION setting when it is set to “true”.

Setting the CURLOPT_FOLLOWLOCATION to true tells cURL to continue to follow redirects until it gets a non-redirect header.
(NOTE: the plugin uses cURL to make HTTP requests to SoundCloud)

But in your case it is ignoring this command and hence why you are seeing the 302 “redirect” result. This is why I think there may be some setting on your server which is causing this.

Can you check if there are any logs being created on your server which might be related to this?

I’ve just released a new version which should solve the 302 issue. Please try it and let me know how it goes.