Page not found on Fresh install

Actually I did. After a broken database I wanted a fresh installation. So I deleted user seafile and started from scrarch. I also opend the ports 8000 and 8082 on my firewall. I nginx logs nothing shows that there is something wrong. Thanks for your help.

So did you (in your first post) mean that only the NGINX log does not have any errors? What about all of the Seafile logs? See https://manual.seafile.com/maintain/logs.html for more information about them. If you are using NGINX you don’t have to open other ports than 443 or 80 (in your test case). The other ports are only used by the Seafile built in webserver. You could post your NGINX site config, too.

Edit: You can also have a look here: https://manual.seafile.com/faq/setup.html

Here is my NGINX SERVER

server {
listen 80;
server_name data.ffcag.de;

proxy_set_header X-Forwarded-For $remote_addr;

location / {
    fastcgi_pass    127.0.0.1:8000;
    fastcgi_param   SCRIPT_FILENAME     $document_root$fastcgi_script_name;
    fastcgi_param   PATH_INFO           $fastcgi_script_name;

    fastcgi_param    SERVER_PROTOCOL        $server_protocol;
    fastcgi_param   QUERY_STRING        $query_string;
    fastcgi_param   REQUEST_METHOD      $request_method;
    fastcgi_param   CONTENT_TYPE        $content_type;
    fastcgi_param   CONTENT_LENGTH      $content_length;
    fastcgi_param    SERVER_ADDR         $server_addr;
    fastcgi_param    SERVER_PORT         $server_port;
    fastcgi_param    SERVER_NAME         $server_name;
    fastcgi_param   REMOTE_ADDR         $remote_addr;

    access_log      /var/log/nginx/seahub.access.log;
    error_log       /var/log/nginx/seahub.error.log;
    fastcgi_read_timeout 36000;
    client_max_body_size 0;
}

location /seafhttp {
    rewrite ^/seafhttp(.*)$ $1 break;
    proxy_pass http://127.0.0.1:8082;
    client_max_body_size 0;
    proxy_connect_timeout  36000s;
    proxy_read_timeout  36000s;
    proxy_send_timeout  36000s;

}

location /media {
    root /home/seafile/haiwen/seafile-server-latest/seahub;
}

}

logs are empty only seahub_django could give a hint:

2017-06-16 19:53:40,814 [WARNING] django.request:170 get_response Not Found: /index.php

thanks for your help

Sorry I can’t detect any problem there. Bad question but did you try reinstalling the whole server and starting from scratch? :sweat_smile: Or maybe someone else can help you here.

After a clean install I get an error in seahub.error.log at nginx!

“can’t connect to upstream fastcgi:127.0.0.1:8000”

The funny thing is my seahub is listening and! I don’t get an 502…strange

And would you like to post this error here?

After a clean install I get an error in seahub.error.log at nginx!

“can’t connect to upstream fastcgi:127.0.0.1:8000”

The funny thing is my seahub is listening and! I don’t get an 502…strange

First: Did you modify the seahub_settings.py like on https://manual.seafile.com/deploy/deploy_with_nginx.html ?
Second: Did you start seahub via “./seahub.sh start-fastcgi” ?

Both times yes, can’t imagine where the error is…:frowning:

Did you install all of the packages mentioned at https://manual.seafile.com/deploy_pro/download_and_setup_seafile_professional_server.html ? I remember someone with a similar problem, where the package python-urllib3 was missing.

Here’s another one with the same problem. But no solution there. Maybe @GITchristoph has found one?

Also maybe worth a try:

Hi

The “solution” was to delete the path to the media folder.
I mention that in the post.

But that’s CentOS, not Debian.

I had a quick look over the post here and to me it looks like a permission issue to the media folder.
Or the folder definition in the Nginx conf file is wrong.
100% sure that this is correct?

/home/seafile/haiwen/seafile-server-latest/seahub

Just asking, I made many mistakes like typos etc.

@curioussoul you say that it’s a “fresh install” but actually you then say

“After a broken database I wanted a fresh installation. So I deleted user seafile and started from scrarch.”

It’s not really fresh then. Small things like this is how the permissions get messed up in my experience :wink:

Let’s see if we can get you over the line.

Greetings, Chris

Wait I’ll try

Deleting the Line didn’t Help.

What I did was Deleting the User, Databases and every folder containing Seafile in its name :slight_smile:

I could use a different username, than it would be a fresh installation…:slight_smile:

You could also make a real fresh installation and install it step-by-step with the help of the manual. :slight_smile: At first without NGINX and if that worked, with NGINX. Then you can check where the problem is.

A colleague made it run by adding the nginx user (www-data or http user) to the seafile group and chmod 0750 on the seafile home-directory. Maybe worth a try.

I tried didn’t work. My fresh install is like the one in the manual.

what do you get when you visit

http://data.ffcag.de

Sorry for my late reply. Maybe you can try chown the seafile directory to root and try to run nginx and seafile as root - just for a test. If it works it’s a permission issue.

Actually it was a wrong path to seahub/media

and now I’m using Seahub without! fastcgi

regards