@melkia666
From what you've posted, I'm not seeing where PHP-FPM is being configured and since OwnCloud is a PHP script, PHP has to be handled somehow, otherwise the script won't work (or shouldn't).
With just what you've posted, the only thing that would actually be handled are standard requests for HTML files (i.e. index.html
), so if you're able to access OwnCloud at all, there has to be some sort of PHP configuration elsewhere that it's included in what you've provided. If you're not able to, then the configuration above is why you're not able to run the script.
The above files do not handle PHP requests at all. If you'll take at:
# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
#
#location ~ \.php$ {
# fastcgi_split_path_info ^(.+\.php)(/.+)$;
# # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
#
# # With php5-cgi alone:
# fastcgi_pass 127.0.0.1:9000;
# # With php5-fpm:
# fastcgi_pass unix:/var/run/php5-fpm.sock;
# fastcgi_index index.php;
# include fastcgi_params;
#}
This is part of what you'd normally use to handle PHP-FPM requests, but since it's commented out with #
at the start of each line, there's no handling going on.
So my thoughts on this would be:
1). Something has been installed and it overwrote your configuration, or;
2). The installer that you used was interrupted or didn't complete, or;
3). There's something else at play, though it's hard to tell just based on the provided output.
DigitalOcean does have an OwnCloud one-click image that you can deploy when creating a Droplet. What I would recommend is deploying a new Droplet and when doing so, click on the header "One-Click Apps" next to "Distributions", then scroll down and find "OwnCloud 9.0.3" and use it to deploy a new instance.
Last I ran, the DigitalOcean instance does correctly set things up and that should help you to get a working installation setup and ready to use.