fahrvergnuegen

Well, the GoDaddy folks took their time, but they did get this all resolved. I am now using curl() with the following options set:

curl_setopt ($ch, CURLOPT_PROXY, “https://64.202.165.130:3128”);
curl_setopt ($ch, CURLOPT_SSL_VERIFYPEER, FALSE);

and it works like a charm.

Here is what they gave me, but (a) IT DOES NOT WORK and (b) you may need a different proxy IP:

curl_setopt ($ch, CURLOPT_HTTPPROXYTUNNEL, TRUE);
curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP);
curl_setopt ($ch, CURLOPT_PROXY, “https://64.202.165.130:3128”);
curl_setopt ($ch, CURLOPT_SSL_VERIFYPEER, FALSE);

When I try to use cURL with these settings, I get a “Received error code 403 from proxy.”

Godaddy customer service has basically refused to help me resolve this issue. Admittedly, I am on the cheapest plan they have, but it is still stupid on their part given that I am likely not to be the only one trying to host a WordPress blog (or any blog with trackback capability for that matter).

I will keep trying and will post if I make any progress. It might help if you also called them.

Thanks.

Just heard back grom GoDaddy tech support. They are in fact proxying all outbound traffic. Tech support suggested using cURL instead of fsockopen. They provided me with the parameters to make cURL proxyaware for their setup. I will try this later tonight/tomorrow and post any results here.

Bump

Tried the latest download (2-22-05), which has Ryan’s fix in it and trackback still did not work in either direction. I am using a subdomain and that might have something to do with it — maybe the URLs get resolved wrong.