I have managed to get seafile work on my internal ip as well as external ip on my raspberry pi. I have used seafile 6.2.3 version plus nginx and have generated ssl certs/keys etc.
i have port forwarded 80 to internal pi ip address and the same port as nginx which is 8000. This works as i can access seafile from outside of my LAN. My mobile can sync as well both inside LAN and outside of LAN through port 80.
FYI I also run
PIVPN that runs on port UDP/TCP 443
The issue comes when i try to use SSL by following all the guides that are available. I change nginx to run on 8001 as I dont want to use 443 because I run openvpn tcp on that and port-share option of openvpn does not work well for me for some reason. I make the chanes in ccnet.conf and seahub_settings.py, restart seahub on fastcgi. For router port forwarding I just match 8001 to 8001 as 443 to 8001 will stop my openvpn traffic.
Once i have done the above, the page does not load at all. I dont know why but I wonder if anyone with all these services i.e. pivpn running have managed to do this?
One more thing that I have not fully understood is on the settings page (web interface) I had to keep the FILE_SERVER_ROOT = http://192.168.1.86:8082 as this. Any other settings just does not work. I had to use the same setting under seahub_settings.py as well.
although my HTTP_SERVER_ROOT = ‘https://xxx.ddns.net:8000/seafhttp’ in both seahub_settings.py and under settings page on web gui.
If I change FILE_SERVER_ROOT = https://192.168.1.86:8082 it stops working and if change it to FILE_SERVER_ROOT = ‘https://xxx.ddns.net:8000’ or ‘https://xxx.ddns.net:8082’ or ‘http://xxx.ddns.net:8082’ it does not work.
I want to understand what should go in here and how it affects seafile.
If any one has any input, please share.