Posts by Kritta

  • Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

    https://mysite.com/onlyoffice won't work because mysite.com hosts a commercially-provided website, and I use a subdomain cloud.mysite.com to redirect traffic to a local server for NextCloud. If I browse using the IP address of the PC running OMV https://192.168.xxx.xxx/onlyoffice I get ERR_CONNECTION_REFUSED.


    I also had a look at the log from the onlyoffice docker container and It contains:

    standard_init_linux.go:211: exec user process caused "exec format error"


    Thanks for your suggestion and help... and the help you've provided to so many others too. :)

  • Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

    I have a question regarding [How-To] onlyoffice in nextcloud docker. This is an excellent guide, but does not have a Q&A, and one cannot reply to the original guide.


    I followed the guide and all went as expected other than that the system doesn't work. When browse to nextcloud.mysite.com/onlyoffice it simply redirects to nextcloud.mysite.com (the standard nextcloud default page). I suspect this has something to do with the nginx config files, but I can't work out what. I am, incidently, using a subdomain for nextcloud... I use cloud.mysite.com for nextcloud. The nginx config file in the guide appears to be appropriate for subdirectory rather than subdomain. Any thoughts? Maybe we need a separate thread for a Q&A related to this How-To.


    - Andrew


    UPDATE:

    The OnlyOffice docker image is not compatible with ARM-based single board computers. So, this will not work on Raspberry Pi, Odroid, etc. Maybe this could be added to the original guide.

  • Cannot ping other nodes from command line

    I have OMV set up on an Odroid XU4 and it's working nicely. I have SMB shares set up, and I can read and write to them from other computers on the network. I can use the web interface without problems.


    My problem is that I cannot get the OMV server to access any other computers. I cannot ping other computers from the commandline. When I try to do so I get 'Name or service not known'. I can get the OMV server to ping itself without a problem, but I cannot ping other machines.


    I don't have any network interfaces listed in the OMV web.


    Any ideas on how to tackle this?

  • Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

    Using External Storages


    I'm having trouble using external storages under this setup. I can't add external shares via the Nextcloud interface - they just keep showing up with the red icon that suggests that the host is unreachable.


    I am also unable to access the network share from within the nextcloud docker container using the command line:



    Code
    root@MYMACHINE:~# docker exec -it nextcloud bash
root@d9513a28f349:/# smbclient -L TARGETPC
do_connect: Connection to TARGETPC failed (Error NT_STATUS_UNSUCCESSFUL)
root@d9513a28f349:/#

    From outside of the nextcloud container, I cannot use the smbclient command at all - command not found.


    I'm not sure if this is an issue specific to this nextcloud setup, or if it is about networking or the broader OMV environment.


    Any tips would be appreciated.


    - Andrew

  • Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

    I've noticed that with this setup I cannot use SMB/CIFS as port 445 is already in use (by the nextcloud docker container, I think). After starting SMB/CIFS the syslog shows:


    Code
    smbd[28610]: Error = Address already in use
smbd[28610]: bind failed on port 445 socket_addr = ::.

    Is it possible to use SMB with this configuration? How can I change that port after I have this whole setup up and running? If I stop the docker container (via the OMV interface), modify the port number, and then re-start it, would nextcloud continue to run okay? Or would that cause trouble?



    Thanks in advance to anyone who can help.


    - Andrew

  • Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

    If you're using a subdomain other than "nextcloud" then you will also need to:


    Edit nextcloud.subdomain.conf which is found in /srv/dev-disk-by-label-disk1/appdata/letsencrypt/nginx/proxy-confs (Change 'disk1' in the path to match your disk name.)


    Change server_name nextcloud.*; to server_name yoursubdomain.*; where "yoursubdomain" is whatever subdomain you've chosen.


    For example, I wanted NextCloud to be accessible at cloud.mysite.com, so I changed the line to become server_name cloud.*;. You can use whatever subdomain you like as long as you have the appropriate CNAME set up on your DNS records and you edit the server_name property in the file as mentioned above.


    I also had to comment-out proxy_max_temp_file_size 2048m; in the above-mentioned file. Prior to doing that I was seeing nginx: [emerg] "proxy_max_temp_file_size" directive invalid value in /config/nginx/proxy-confs/nextcloud.subdomain.conf:29 appear repeatedly in the letsencrypt docker log file. I don't know why this is.

  • Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

    Firstly, I have to say this is an excellent guide. Thanks very much for putting it all together and posting it. I'm impressed and grateful.


    I followed the guide with the following modifications:

    • The URL for letsencrypt was changed to cloud.mydomain.com. I added no subdomains. This is because http://www.mydomain.com is hosted by my ISP.
    • I added the internal IP of my server to the config.php file so that I could get to nextcloud internally via xxx.xxx.xxx.xxx:445. This works okay.
    • I used the modifications in post 4 above to use the cloud.mydomain.com subdomain.

    I can now access nextcloud via the internal IP: xxx.xxx.xxx.xxx:445.
    I cannot access nextcloud via cloud.mydomain.com. This returns ERR_CONNECTION_REFUSED.
    I can ping to cloud.mydomain.com and it returns the correct IP. Ports are forwarded as described in the guide.


    If I clear the letsencrypt docker container log and restart the letsencrypt docker I get: