[[Support] Linuxserver.io - Nextcloud]

44 minutes ago, skois said:

You added the whole block on the advanced tab right? Not only the 4 lines.

I still find this very hacky. I wanna start looking on the traefic instead of swag, but need to read a lot! 
I had a talk the other day with someone that used both traefic and nginx and HAproxy, he had simillar problems with nginx and haproxy but no with traefic.

Not even sure at this point, but I think I actually tried both ways. But if I remember correctly, the conf file for the nginx proxy manager's nextcloud host actually looked the same with and without the location block in the advanced tab.
I used traefik about a year ago or so and it definitely seemed easier compared to nginx, but there wasn't much info about it back then from users so finding solutions to things were more difficult. But it seems like more and more people are starting to use it now. Maybe should do some digging indeed if I'll find a way to add fail2ban without swag, because that's kind of the only reason I switched to swag at all right now.

[[Support] Linuxserver.io - Nextcloud]

On 12/25/2020 at 5:08 PM, skois said:

About the assembling chunks problem, i found a fix.

Go to NginxProxyManager edit your nextcloud proxy host, Go to advanced tab.

Now copy the location block from your nextcloud.conf and add the following lines:

(Set the times to your liking. I was doing some testing and had this big times. Also depends on your net speed. From my testing the time you need is time_to_upload + time_to_assemble_the_chunks, so on big uploads that needs eg. 1hour to upload you need like 1hour and 5 minutes timeout).

proxy_connect_timeout 1d;
proxy_send_timeout 1d;
proxy_read_timeout 1d;
send_timeout 1d;

 

The pasted conf on your advanced tab should be like this:

location / {

    proxy_connect_timeout 1d;
proxy_send_timeout 1d;
proxy_read_timeout 1d;
send_timeout 1d;
    


    # Force SSL
    include conf.d/include/force-ssl.conf;







    

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

 

When I added these timeout settings to the advanced tab I still got the error so there might've been something else missing from my setup too. But thanks for your help still. I actually decided to switch to swag container to also benefit from the fail2ban. I also found a solution for the local access for transferring files faster. So in the end I actually changed your recommended timeout values in the nextcloud's own nginx.conf file so they should be applied when I access locally and avoid timeouts with bigger files so I wouldn't have to upload these over the Internet. So thank you, you actually made me read and learn a bit about nginx to understand what's happening.

[[Support] Linuxserver.io - Nextcloud]

Hi everyone.

 

I'm running linuxserver docker of nextcloud ver. 20 with NginxProxyManager and I have couple of issues. Since I've seen that some of you also use NginxProxyManager I hope someone can help or at least point me at the right direction. So the problems are:
1. I'm currently able to only access my nextcloud from domain address. http://localip:port gives error 400 which is kind of expected. But when going https://localip:port I'm automatically forwarded to my domain address. I'd like to access nextcloud also locally to benefit from LAN speed.
2. Uploading big files from browser and getting "Error when assembling chunks, status code 504". The files are actually getting uploaded, but error is still displayed. Not sure if this is because limits have been removed with NC 20 (file upload limit is not displayed in UI settings > basic settings) or my client_max_body_size is 0 in nextcloud/site-confs/default and nextcloud/nginx/nginx.conf. If I understood correctly the error 504 about chunks is because of a NC timeout limits, but I don't know where should i change these limits. I've seen people change timeout limits in php.ini files and nginx/apache files, but since I don't have them or their setup is totally different I'm not sure where and what should I change to avoid this error.

 

Config.php:

<?php
$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'instanceid',
  'passwordsalt' => '29t+passwordsalt',
  'secret' => 'secret',
  'trusted_domains' => 
  array (
    0 => '192.168.1.177:444',
    1 => 'nextcloud.my.server',
  ),
  'trusted_proxies' => 
  array (
    0 => 'NginxProxyManager',
  ),
  'dbtype' => 'mysql',
  'version' => '20.0.3.2',
  'forwarded_for_headers' => array('HTTP_X_FORWARDED_FOR'),
  'overwrite.cli.url' => 'https://192.168.1.177:444',
  'overwritehost' => 'nextcloud.my.server',
  'overwriteprotocol' => 'https',
  'dbname' => 'nextcloud',
  'dbhost' => '192.168.1.177:3306',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'dbuser',
  'dbpassword' => 'dbpassword',
  'installed' => true,
  'filesystem_check_changes' => 1,
  'updater.secret' => 'updater.secret',
);

NginxProxyManager/nginx/proxy_host/nextcloud.conf
 

# ------------------------------------------------------------
# nextcloud.my.server
# ------------------------------------------------------------


server {
  set $forward_scheme https;
  set $server         "192.168.1.177";
  set $port           444;

  listen 8080;
listen [::]:8080;

listen 4443 ssl http2;
listen [::]:4443;


  server_name nextcloud.my.server;


  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-5/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-5/privkey.pem;






  # Block Exploits
  include conf.d/include/block-exploits.conf;






  access_log /config/log/proxy_host-5.log proxy;







  location / {

    


    # Force SSL
    include conf.d/include/force-ssl.conf;







    

    # Proxy!
    include conf.d/include/proxy.conf;
  }


  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}

 

If anyone has any ideas or need me to post any more conf files, I would appreciate very much.