I have D6.10 with the latest version of Private Upload, and I get this error when I go to the Private Upload settings page:

* warning: fsockopen() [function.fsockopen]: unable to connect to www.mysite.org.uk:80 in /home/sites/mysite.org.uk/public_html/modules/private_upload/private_upload.module on line 768.
* Unable to test file access: Connection refused

However, all seems to be working ok - it's just this error indicates something is not happy.

Can't find anyone else referring to this - is anyone else experiencing it, and better still, can you advise a fix please?

Regards
maranjo

Comments

nattyweb’s picture

nattyweb commented

Further to this, I've checked with the hosting company I use (Heart Internet) and got this response from a member of the support team:

Is the drupal module trying to connect back to the same server? If so then yes, i'm afriad we block loopback connections to the servers. It's setup like this to prevent badly coded scripts from running in a loop and taking down the server.

So it seems that Private Upload in D6.10 is considered to be a badly coded script.

Comments, anyone?

seanbfuller’s picture

seanbfuller commented

I'm running into the same loopback issue with a site hosted on Rackspace. This timeout is also causing the /admin page to take forever to load and give that error. I'd like to request that:

  • The privacy check on the admin page be removed.
  • Instead of automatically checking this on the private_upload settings page it'd be nice to make it a button that performs the test.
  • Add a warning about how the loopback will fail if the server is behind a firewall.
  • Optionally add instructions on how to test this if the loopback test doesn't work (copy the link to the test file, log out and paste it into the browser maybe?) might be helpful to others.

Because this issue is also affecting the admin page, I'd like to request that we switch it to a bug.

Thanks!

jody lynn’s picture

jody lynn
she/her
Primary language English
commented

We had the same problem on Rackspace

Adding an entry in the hosts file for the fully qualified domain name to map to the server fixed it for us.