this is my first DO droplet and i was using owncloud and everything was fine it connected to the owncloud login and i was able to login. Then i added normal security measures like a new user and had ssh keys instead of a password. I did this on the server and i do not know why now when i try to login to own cloud i am now at the default niginx page. what should i do?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
apt-getfrom the CLI)?
The first question I’m asking simply because you’ve tagged this question with both, but only mention NGINX in your comment. The second question is because directory structures may differ from the one-click and a repository package. The third is because adding a new user and setting up an SSH key should not cause Apache/NGINX to fail or revert back to the standard “success” page you see when the web server is first installed.
If you have this directory and Apache isn’t actually installed…
…please post the output of the
defaultfile (this is your default server block for NGINX). If NGINX is the only web server running and you’ve not configured any other server blocks, this is the one that should be pointing to where your website resides.
thank you for your help but a support just said to delete it because i modified something and start from scratch i mean thats fine thank you for your help :)
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:
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.