owncloud broken

Question

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?

Jonathan Tittle · Accepted Answer

@melkia666 Questions : Are you using Apache, NGINX, or both (i.e. NGINX proxying to Apache)? How was Apache/NGINX setup (i.e. one-click or using apt-get from the CLI)? What do you consider to be normal security measures? * Why? 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… /etc/nginx/sites-enabled …please post the output of the default file (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.

melkia666 · Answer

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 :)

melkia666 · Answer

honestly i used set up the first droplet using the install the owncloud and i do have and i have this file like you said /etc/nginx/sites-enabled

so is apache2 not the one running the own cloud?

what confuses me is when i first boot up the system it did work i was able to login to my owncloud.

here is the server info that i cat.

i hope this helps you figure out whats wrong with my server thank you response

You may add here your

server {

…

}

statements for each of your virtual hosts to this file

You should look at the following URL’s in order to grasp a solid understanding

of Nginx configuration files in order to fully unleash the power of Nginx.

http://wiki.nginx.org/Pitfalls

http://wiki.nginx.org/QuickStart

http://wiki.nginx.org/Configuration

Generally, you will want to move this file somewhere, and start with a clean

file but keep this around for reference. Or just disable in sites-enabled.

server { listen 80 default_server; listen [::]:80 default_server ipv6only=on;

root /usr/share/nginx/html;
index index.html index.htm;

# Make site accessible from http://localhost/
server_name localhost;

location / {
	# First attempt to serve request as file, then
	# as directory, then fall back to displaying a 404.
	try_files $uri $uri/ =404;
	# Uncomment to enable naxsi on this location
	# include /etc/nginx/naxsi.rules
}

# Only for nginx-naxsi used with nginx-naxsi-ui : process denied requests
#location /RequestDenied {
#	proxy_pass http://127.0.0.1:8080;    
#}

#error_page 404 /404.html;

# redirect server error pages to the static page /50x.html
#
#error_page 500 502 503 504 /50x.html;
#location = /50x.html {
#	root /usr/share/nginx/html;
#}

# 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;
#}

# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
#	deny all;
#}

}