Alternative Seahub port not open. And firewall considerations

Seafile Server
1

I’m trying to install seafile 7.1.5 on a Debian 10 vps which has php-fpm on port 8000.

So I edited /conf/gunicorn.conf.py to bind to 127.0.0.1:8085

When I ./seafile.sh start, that started seaf-server process and opened port 8082.

When I ./seahub.sh start 8085, it started 5/6 Python processes listeining on por t8085.

But it didn’t open port 8085 like .seafile.sh start opened port 8082.

I’m a newbie to firewall. And it was suggested to get port 8085 open. But I can’t get nftables to open port 8085.

Was ./seahub.sh start 8085 supposed to open port 8085 without me doing anything?

Port 8082 seems to be open, but does this mean I still have to add a firewall rule for it?

2

I’m making some progress on this seafile 7.1.5 install on Debian 10 vps which has php-fpm listening on port 8000.

I decided to move php7.3-fpm to /var/run/php7.3-fpm.sock and that seemed to free up port 8000.

A key change, I think, that opened port 8000 with the ./seahub.sh start command with changing gunicorn.conf.py from
bind = " 127.0.0.1:8000"
to
bind = "0.0.0.0:8000"

The active ethernet was enp3s0, so maybe that’s why the change from 127.0.0.1 to 0.0.0.0 was needed?

Anyways, now I have a seahub signin screen when I go to http://krishnify.com:8000 Yay!

http://krishnify.com:8082 doesn’t give a promising result. It just gives a blank screen.

But at least I have part of seafile working.

Maybe it’s now dealing with the Nginx conf. Which I’m a newbie at also.

3

Being a vps system admin newbie, I wonder if anyone might have any input on the following questions I have:
0. Currently I have SERVER_ROOT commented out in seahub_settings.py
If I try to set it to seafile.krishnify.com/seafhttp, seahub won’t start. Seahub starts without SERVER_ROOT right now.

  1. Do I need to create a CNAME DNS entry for the SERVER_ROOT?
    Currently, I do have a CNAME DNS entry for seafile.krishnify.com.
    However, probably due my lack of Nginx config knowledge, seafile.krishnify.com goes to another website on the vps, instead of correctly proxy_passing to seafile.krishnify.com

  2. What’s wrong with my Nginx config?

server {
listen 80;
listen [::]:80;
server_name seafile.krishnify.com;
autoindex off;

proxy_set_header X-Forwarded-For $remote_addr;

client_max_body_size 100M;
access_log /etc/nginx/seafile.com.access.log;
error_log /etc/nginx/seafile.com.error.log;

 location / {
        proxy_pass         http://localhost:8000;
        proxy_set_header   Host $host;
        proxy_set_header   X-Real-IP $remote_addr;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Host $server_name;
        proxy_read_timeout  1200s;
    }


 location /seafhttp {

location ^~ /seafhttp {

        rewrite ^/seafhttp(.*)$ $1 break;
        proxy_pass http://localhost:8082;
        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_connect_timeout  36000s;
        proxy_read_timeout  36000s;
        proxy_send_timeout  36000s;
        send_timeout  36000s;
    }

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

}

Any tips and suggestions would be appreciated.