Home / server / Questions / 196097
Accepted
Mojah
Asked: 2010-10-30 01:06:16 +0800 CST

Lighttpd: requesting local URLs via PHP

  • 772

I have a webserver which serves content for a site, let's call it "domain.com". On that site, I have several PHP scripts that serve content. When someone browses to that site, everything works.

If I request, from within PHP (with Curl/Fopen), a URL on my own site (I'll call "domain.com/api/something.php?x=y", I get a timeout that the site could not be contacted. That only happens when I request that URL via PHP, not when called via the CLI. When I browse the URL from externally, that works.

On the server, I can "curl " or "wget ", and that works. I can use PHP to request pages externally hosted (google.com etc.), but I can not do it with pages hosted on my lighttpd config on the same server.

Is this familiar to anyone? Are there known parameters that could conflict with this?

php fastcgi lighttpd

2 Answers

  1. Best Answer

    FIGURED IT OUT! By default, Lighttpd on FreeBSD is configured like this:

    fastcgi.server = ( ".php" =>
                   ( "php-local" =>
                     (
                       "socket" => socket_dir + "/php-fastcgi-1.socket",
#                       "bin-path" => server_root + "/cgi-bin/php5",
                       "bin-path" => "/usr/local/bin/php-cgi",
                       "max-procs" => 1,
                       "broken-scriptfilename" => "enable",
                     )
                   ),

    The key line being:

     "max-procs" => 1,

    If you change it to, say, 50, it works fine. I'm assuming that it needs to fork off another process or something to make the CURL request, and can't because max-procs is set to 1 by default.

    Change it, restart Lighttpd, works perfect. Yeah!

    • 1

  2. Can your own box correctly resolve the domain name you're using? If you're requesting files from www.domain.com, can you ping 'www.domain.com' from itself - Does it resolve the correct external IP that would receive when you ping 'www.domain.com' from an external connection.

    I'm thinking:

    1) The machine name is aliased in your /etc/hosts as 127.0.0.1 and your webserver isn't bound to the loopback address

    2) What about load-balancers, are you using any that might cause routing issues when trying to route to itself

    Andrew

    • 0