Seafile Installation

Ups, i see.
I can not really help you, because I am not using the nginx plugin.

I got a bad gateway 502 error.
/etc/init.d/seafile-server

seafile.sh, seahub.sh

installation permissions:

I just found out that I enabled SSL and forced it to a non-standard port, but somehow it's running on port 8000.
I can't log in my 7443 port.

You need to fix the https paths in Seafile admin or the uploads error I think. In a couple of hours ill come back finish part 4 of the guide test run I was doing. I stopped doing the test at the end of part 3 cause I was waiting for others to sort their problems out...lol.

I can't log into Seafile at all.

Ok, Keeping in mind that I have followed the Guide and installed Seafile as the root user. I have confirmed that yes you do have to change the settings in Seafile's admin page for uploads to be successful. If you don't you will get access denied errors upon unloading files. Its the very last step in the guide Part 4 Steep 9.

tinh_x7, if you proceed to Part 4 and install Nginx then once you complete Part 4 step 6 (fastcgi=true) and reboot you will not be able to load Seafile in your browser using port 8000. If you wish to use a non secure address such as HTTP and not HTTPS then you will need to revert fastcgi back to the false value. You cannot use port 8000 in nginx for Seafile it must be a different port.

However, I did actually complete the installation following the guide with no errors at all. Next ill run up another virtual machine and try installing Seafile as another user and auto create the databases. If successful I'll update the guide

I know but I still get 502 Bad gateway on https.
When I ran seahub.sh, it starts automatically at port 8000.

root@server:~# /root/seafile/seafile-server-latest/./seafile.sh start


[05/30/16 09:04:38] ../common/session.c(132): using config file /root/seafile/conf/ccnet.conf
Starting seafile server, please wait ...
Seafile server started


Done.
root@server:~# /root/seafile/seafile-server-latest/./seahub.sh start


LC_ALL is not set in ENV, set to en_US.UTF-8
Starting seahub at port 8000 ...


Seahub is started


Done.

# Change the value of fastcgi to true if fastcgi is to be used
fastcgi=true
# Set the port of fastcgi, default is 8000. Change it if you need different.
fastcgi_port=7443


#
# Write a polite log message with date and time
#
echo -e "\n \n About to perform $1 for seafile at `date -Iseconds` \n " >> ${seafile_init_log}
echo -e "\n \n About to perform $1 for seahub at `date -Iseconds` \n " >> ${seahub_init_log}


case "$1" in
start)
sudo -u ${user} ${script_path}/seafile.sh ${1} >> ${seafile_init_log}
if [ $fastcgi = true ];
then
sudo -u ${user} ${script_path}/seahub.sh ${1}-fastcgi ${fastcgi_port} >> ${seahub_init_log}
else
sudo -u ${user} ${script_path}/seahub.sh ${1} >> ${seahub_init_log}
fi
;;
restart)
sudo -u ${user} ${script_path}/seafile.sh ${1} >> ${seafile_init_log}
if [ $fastcgi = true ];
then
sudo -u ${user} ${script_path}/seahub.sh ${1}-fastcgi ${fastcgi_port} >> ${seahub_init_log}
else
sudo -u ${user} ${script_path}/seahub.sh ${1} >> ${seahub_init_log}
fi
;;
stop)
sudo -u ${user} ${script_path}/seahub.sh ${1} >> ${seahub_init_log}
sudo -u ${user} ${script_path}/seafile.sh ${1} >> ${seafile_init_log}
;;
*)
echo "Usage: /etc/init.d/seafile-server {start|stop|restart}"
exit 1
;;
esac

[General]
USER_NAME = seafile
ID = a0df893073be2c9b84b300aaa811b4dbc84af1dc
NAME = seafile
SERVICE_URL = https://192.168.1.97:7443


[Client]
PORT = 13419

Your scrip file needs to have fastcgi=false and fastcgi_port=8000. You only need to change fastcgi to the true value if you're using Nginx (part 4). The port number is not changed here.

I'm using Nginx.
My https is 7443, do I need to change fastcgi_port to 7443?

then change your script settings to port 8000 and set fastcgi to true. Then use 7443 as your ssl port in nginx

I got confused b/c I'm thinking if I use a non-standard port SSL, I need to change the fastcgi port in the script too.
Thanks, baldman.

by the way: how do add smb/cifs/external storage share drive from OMV to seafile?

No, Think of it like this. The Seafile application installs and runs in its normal state on pot 8000. Nginx then runs in front of the Seafile application as a proxy listening on SSL port 7443, it then tunnels all Seafile request securely to Seafile. So you are not actually exposing Seafile to the external web, you only expose Nginx on its SSL port.

I'm not really sure about adding external storage to Seafile cause to be honest I haven't really used it. I like owncloud ... Maybe when I update to the latest Seafile there might be some new features.

Gotcha.
I thought Seafile has a plugin or an external storage feature like OwnCloud that we can use.

Yeah maybe, I'll have a look next time I'm back in the GUI.

Ok, I've run into a snag with auto database creation. This is also why I gave up last time and went with manual database creation. No mater what I do a cannot get the MySQL root user password correct. I've tried the normal omv root user password, I've tried creating the root password in the MySQL Plugin settings, I've even tried using no password as you do when visiting plugins management site. I'm not sure what I'm missing here?

I think ill just change it in the management site if that's what I meant to do, but Isn't it meant to be done in the plugin settings page?