Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Dimtar

Members
  • Joined

  • Last visited

Everything posted by Dimtar

  1. How are you trying to access the site, via the IP or the URL?
  2. Do an 'ls -lah' on the directory and make sure the user/group on those files is correct? Also check permissions.
  3. Do you want to post a copy of the nginx config file?
  4. Updated and running the new version of the Docker without issue. Thanks Sparkly and LSIO team!
  5. It needs to be stable, something that isn't going to break every five minutes (either for the end-user or with every little update from upstream), that is robust enough that end-users can't break it every five minutes otherwise support becomes an even bigger headache... Makes sense. From my side this Docker has been very stable, any problems I've had can be put down to me or load on the server at the time. Just my two cents, thanks for everyones work on this.
  6. Do you guys have an internal criteria for what needs to happen to have a beta docker be made into a full time docker?
  7. So next2wire's post is good but here is a rough guide on how I modified mine using what he wrote. For reference I bought a 3 year SSL certificiate off ssls.com for the below. This is a rough guide on how to setup SSL for the Nextcloud Docker and get a A+ rating on ssllabs.com Commands/directories are bolded below. Stop the nextcloud docker. Navigate to the nextcloud keys folder, in my case: /mnt/user/appdata/nextcloud/keys Remove/rename the current cert.key and cert.crt files. Run this command: openssl req -nodes -newkey rsa:2048 -keyout cert.key -out cert.csr Follow the wizard through to generate your cert.csr and cert.key. Use the cert.csr to activate your newly purchased SSL cert with ssls.com Using the SSL cert information make a file called cert.crt using the SSL cert and another called inter.crt with the intermediate CA. Run this command to concatenate the two new files: cat cert.crt inter.crt >> cert.pem Now run this command as well: openssl dhparam -out dhparam.pem 2048 Now navigate to the Nginx configuration for the Nextcloud site, in my case: /mnt/user/appdata/nextcloud/nginx/site-confs Modify the file simply called: default Below is a copy of the first 46 lines of my Nginx file, the parts bolded are one I have added to the config file or changed. Matching yours should work: upstream php-handler { server 127.0.0.1:9000; # server unix:/var/run/php/php7.0-fpm.sock; } server { listen 80; server_name _; # enforce https return 301 https://$server_name$request_uri; } server { listen 443 ssl; server_name _; ssl_certificate /config/keys/cert.pem; ssl_certificate_key /config/keys/cert.key; ### Add Diffie–Hellman key exchange ### ssl_dhparam /config/keys/dhparam.pem; ### Disable SSL by enforcing TLS ### ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ### Add some ciphers and reject weaker ones ### ssl_ciphers "EECDH+AESGCM:EDH+AESGCM:ECDHE-RSA-AES128-GCM-SHA256:AES256+EECDH:DHE-RSA-AES128-GCM-SHA256:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ssl_session_timeout 10m; ssl_verify_depth 2; # Add headers to serve security related headers add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; add_header X-Content-Type-Options nosniff; add_header X-Frame-Options "SAMEORIGIN"; add_header X-XSS-Protection "1; mode=block"; add_header X-Robots-Tag none; add_header X-Download-Options noopen; add_header X-Permitted-Cross-Domain-Policies none; # Path to the root of your installation root /config/www/nextcloud/; # set max upload size client_max_body_size 10G; fastcgi_buffers 64 4K; Now start the docker and verify its working, once this is complete check your URL on https://www.ssllabs.com
  8. I can get it from my web address just fine its the sync client that wont connect. i not sure its because i am using DDNS or what. i'll post on the nextcloud forums, just happy its up and running. Can you get to the web address from outside your house?
  9. I assume the Owncloud Sync client for desktop systems.
  10. I meant the container, wrong terminology sorry.
  11. Hey CHBMB, I appreciate you taking the time to help. I changed that line to binlog_format=mixed and also binlog_format=row but neither worked. It is as if that custom.cnf file is being ignored by mariadb. Sorry to ask this question but you're restarting the docker after changes right?
  12. I believe I removed a line but I cannot be 100% sure. Here is a copy of my custom.cnf, maybe backup your current one and try mine? http://pastebin.com/xSxjff9L
  13. So I could be wrong but I believe this to be the potential issue the first post referred to. I had that issue too and I fixed by adding a line to the custom.cnf file inside the mariadb config folder. The following line: skip-log-bin
  14. What does the log for the Nextcloud Docker say after you click the "finish setup" button?
  15. Restart the docker and it'll pull the latest version.
  16. Inside the appdata folder or (/config) there is a folder calls "keys", inside that is two files cert.crt and cert.key, those need to be replaced by equivalent certs. I am not sure if you can use a Lets Encrypt cert here but as an example I just got the $9 cert from ssls.com and it works fine.
  17. there is no "issue" and there never was any "issue" with the lsio owncloud beta either, change the location during setup. http://imgur.com/8Pus7FT Noted, thanks. Can something be put in the description of the docker to maybe avoid this for others? I assumed that the docker would default to using /data because it was part of the default mapping but I understand why its not.
  18. It looks like this suffers from the same issue that the OwnCloud beta did. That is, it stores files in the /config folder not the /data mapping.
  19. 1+ yeah i like to try NextCloud also, have read the split up hope they put a good product out. I've added it here, if you want to vote as well: http://feathub.com/linuxserver/linuxserver.github.io/+55
  20. Also running the OwnCloud beta, seems quite solid so far. Going to be requesting a NextCloud docker though.
  21. I don't think the time is right on this Docker, does anyone know if there is a way to correct this?
  22. Have the issue as well.
  23. Does anyone have a script working that converts downloads on completion to MP4?
  24. Working ok here. Tried a browser cache clear? It didn't work, probably gonna need to wipe and redo the config.
  25. My hydra is now giving me a 500 "internal server error" even after a restart, anyone else?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.