sampla

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by sampla

  1. On 4/23/2020 at 10:06 PM, afsilver said:

    i did edit my first post, axplaining that i "fixed" mariadb by deleting the mariadb folder in appdata. you must have missed it 😃
    it now works. but onto nextcloud which is also f'd.

     

    thanks for the help anyways :D

    I'm also suffering from a missing mysql.sock. The problem emerged after a docker update. Before I delete my own mariadb folder from appdata I'd like to know what problems you had with Nextcloud.

  2. 5 hours ago, amadnei said:

    well after a few hours It seem to be working!

     

    Only error I got is

    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
    nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

     

     

    edit : well the error seem to cause nextcloud to not work ( cant even connect to it ), even if people online say it should cause any issue :(

    I also got the error you mention and it's not a problem. Your problem is elsewhere.

     

    Did you go through with Nextclouds initial installation with the database etc? Can you open Nextclouds webUI by clicking the Docker icon? Check your port forward at https://www.yougetsignal.com/tools/open-ports/

  3. 3 minutes ago, amadnei said:

    I did follow spaceinvader, aswell as techcoreduo and linuxserver written guide !

     

     

    Waiting for verification...
    Challenge failed for domain amadnei.duckdns.org.duckdns.org

    In letsencrypt docker settings write only "duckdns.org" for domain name. For subdomain write only "amadnei".

  4. 4 minutes ago, amadnei said:

    hopefully someone can help me, Im stuck at doing the Letsencrypt reverse proxy.

     

    Seem to be unable to port foward on asus router, wich I suspect why letsencrypt cannot reach my duckdns domain ?

    thanks!

    What errors are you getting? Are you following spaceinvaderone's youtube guide?

  5. Alright, so I managed to change my reverse proxy to letsencrypt as suggested and I also realized that I'm better off ignoring what Nextcloud's log in the webUI says and look at nginx's error log instead. I'm getting

    [error] 322#322: *1832 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.18.0.3, server: _, request: "PUT /remote.php/webdav/Photos/pic.jpg HTTP/HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.mywebsite.com:443"

    Some Googling suggests adding

    proxy_read_timeout 3600;

    to my conf file, but when I do my letsencrypt log tells me

    nginx: [emerg] "proxy_read_timeout" directive is duplicate in /config/nginx/proxy-confs/nextcloud.subdomain.conf:28

     

    Suggestions?

  6. I've got two problems going on. I'm connecting to nextcloud using a reverse proxy provided by NginxProxyManager. The guide by spaceinvaderone didn't work out for me so I didn't go with his reverse proxy suggestion.

     

    Problem nr 1:

    whenever I try to upload either a single larger file (test file is 5gb) or multiple files totaling a few Gb I get

    error assembling chunks, error 504

    The log doesn't show anything for this error. The upload usually goes through, but not if I refresh the page too soon after receiving the error.

     

    Problem nr 2:

    When I try to upload a larger number of files (tested with 100+) my log shows the following:

    Sabre\DAV\Exception\BadRequest: Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 7372800 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.
    
        /config/www/nextcloud/apps/dav/lib/Connector/Sabre/Directory.php - line 156:
    
        OCA\DAV\Connector\Sabre\File->put(null)
    
        /config/www/nextcloud/apps/dav/lib/Upload/UploadFolder.php - line 45:
    
        OCA\DAV\Connector\Sabre\Directory->createFile("251658240", null)
    
        /config/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php - line 1096:
    
        OCA\DAV\Upload\UploadFolder->createFile("251658240", null)
    
        /config/www/nextcloud/3rdparty/sabre/dav/lib/DAV/CorePlugin.php - line 525:
    
        Sabre\DAV\Server->createFile("uploads/sam ... 0", null, null)
    
        <<closure>>
    
        Sabre\DAV\CorePlugin->httpPut(Sabre\HTTP\R ... "}, Sabre\HTTP\Response {})
    
        /config/www/nextcloud/3rdparty/sabre/event/lib/EventEmitterTrait.php - line 105:
    
        call_user_func_array([ Sabre\DAV\ ... "], [ Sabre\HTTP ... }])
    
        /config/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php - line 479:
    
        Sabre\Event\EventEmitter->emit("method:PUT", [ Sabre\HTTP ... }])
    
        /config/www/nextcloud/3rdparty/sabre/dav/lib/DAV/Server.php - line 254:
    
        Sabre\DAV\Server->invokeMethod(Sabre\HTTP\R ... "}, Sabre\HTTP\Response {})
    
        /config/www/nextcloud/apps/dav/lib/Server.php - line 317:
    
        Sabre\DAV\Server->exec()
    
        /config/www/nextcloud/apps/dav/appinfo/v2/remote.php - line 35:
    
        OCA\DAV\Server->exec()
    
        /config/www/nextcloud/remote.php - line 163:
    
        require_once("/config/www ... p")

    Googling the error shows others with the same problem on OwnCloud. All solutions however are related to Apache, whereas I'm using nginx and they don't directly apply.

     

    Solutions I've tried:

    Modifed nginx.conf (/appdata/nextcloud/nginx/nginx.conf)

    - increased client_max_body_size to 16G

     

    Modifed php.ini (/etc/php7/php.ini)

    - increased max_input_vars to 1000

    - increased memory_limit to 1024M

    - changed temp folder

    - increased upload_max_filesize to 16G

    - increased max_file_uploads to 1000

    - increased max_execution_time to 7200

    - increased max_input_time 7200