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.
@melkia666
Questions:
apt-get
from the CLI)?*
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…
…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.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 :)
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.
Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
server { listen 80 default_server; listen [::]:80 default_server ipv6only=on;
}
another virtual host using mix of IP-, name-, and port-based configuration
#server {
listen 8000;
listen somename:8080;
server_name somename alias another.alias;
root html;
index index.html index.htm;
location / {
try_files $uri $uri/ =404;
}
#}
HTTPS server
#server {
listen 443;
server_name localhost;
root html;
index index.html index.htm;
ssl on;
ssl_certificate cert.pem;
ssl_certificate_key cert.key;
ssl_session_timeout 5m;
ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers “HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES”;
ssl_prefer_server_ciphers on;
location / {
try_files $uri $uri/ =404;
}
#}