Same as the handle directive, but implicitly strips the matched path prefix. Next, we can see that they proxy /seafhttp and strip the prefix, which we do in Caddy with handle_path: reverse_proxy (Caddyfile directive) - Caddy Documentation Proxies requests to one or more backends with configurable transport, load balancing, health checking, header manipulation, and buffering options. We don’t care about listeners, server names or tokens.įirst up, we see that in nginx they proxy /seafile locally to 127.0.0.1:8000, although you proxy the web root /. Location /seafmedia static content of Seafile Server First configure Seafile as the user it should run - in this example 'Administator'. Unfortunately, once I tried downloading a file out of seafile later, it did not honor the port in my URL, instead it uses the just the servername, so it failed. Seafile client can be configured to run as a daemon using tools like Firedaemon. Server_tokens off Nginx does not reveal its version number to make life more difficult for attackers How to use run Seafile client as a service on Windows. Server_name _ The 'name' of the virtual server The most interesting parts of this configuration are: listen 80 The port Nginx listens to It’s pretty cool because they actually explain what the important sections do: I found it was also useful to peek at the Seafile docs on the recommended nginx configuration, to get an understanding of what they’re doing on both servers. Thank you and Hope you have a nice weekend The server is running Debian 10 buster with kernel 5.6. This video demonstrates the features of the Seafile client software use to backup, sync, and share your data.We can install and manage the privat. but the problem is how can I redirect the /seafhttp to the fileserver and how can I point the media location of seahub in Caddy? Tried somethings but I’m kinda lost. SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1 SSLCertificateKeyFile /etc/letsencrypt/live//privkey.pemĪlias /media /opt/seafile/seafile-server-latest/seahub/media RewriteEngine on Some rewrite rules in this file were disabled on your HTTPS site, because they have the potential to create redirection loops. Here is the apache2 code, works flawlessly: ServerAdmin files.***********.euĭocumentRoot /var/www/files.***********eu/html 'High sync rates due to delta syncing' is the primary reason people pick Seafile over the competition. Seafile, Nextcloud, and Syncthing are probably your best bets out of the 13 options considered. Since I’m new with caddy I think here is the best place to fix this problem and ditch apache2. My Recommendation for Enterprise Data Storage. I’m trying to move from apache2 because I don’t host a lot of websites, its for mostly my own services and the KISS approach of the caddy is just awesome, my only problem is the Seafile server, I cannot get it to work under Caddy and I cannot find much information about seafile working under caddyV2 on the searches Ive done.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |