HK blog

If you like Seafile, you can deploy it in your organization easily. I did that a couple of years ago and it is always working fine under Debian (my favourite distro). However, today I thought of deploying a second server, which will be more important. Following the setup procedure under CentOS, everything was fine (I used this link :  https://manual.seafile.com/deploy/using_mysql.html ) but the web interfacewasn't working! I checked Firewalld, SELinux, MariaDB, Logs everywhere... Nothing was really weird, except a new file that I wasn't used to it : gunicorn.conf! Well, that file was a new addition to Seafile starting from 6.3! and it seems that in my configuration, the server was bound to... 127.0.0.1:8000! I just changed that, restarted Seafile and Seahub, and it worked! Hoping that would help someone, someday :)

Environnement : VMware Workstation, VyOS 1.2.0 et Windows 7 Schéma : [laptop1]--[R1]--[R]--[R2]--[laptop2] laptop1 : 192.168.111.2/24 sans passerelle laptop2 : 192.168.111.3/24 sans passerelle R1 : eth0 vers R : 172.30.30.2/29 eth1 vers laptop1 : sans adressage R : eth0 vers R1 : 172.30.30.1/29 eth1 vers R2 : 172.31.31.1/29 R2 : eth0 vers R : 172.31.31.2/29 eth1 vers laptop2 : sans adressage Configuration sur R1 : set interfaces bridge br0 aging 300 set interfaces bridge br0 max-age 20 set interfaces bridge br0 priority 0 set interfaces bridge br0 stp false set interfaces ethernet eth1 bridge-group bridge br0 set protocols static route 0.0.0.0/0 next-hop 172.30.30.1 set interfaces l2tpv3 l2tpeth0 bridge-group bridge br0 set interfaces l2tpv3 l2tpeth0 destination-port 10000 set interfaces l2tpv3 l2tpeth0 encapsulation udp set interfaces l2tpv3 l2tpeth0 local-ip 172.30.30.2 set interfaces l2tpv3 l2tpeth0 peer-session-id 1 set interfaces l2tpv3 l2tpeth0 pe