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.

H2OKing

Members
  • Joined

  • Last visited

Everything posted by H2OKing

  1. After last night's update I woke up to this. Tried force updated and can't get it fix. Is there a way to roll back? Looks like a fix has been push out by the devs. Binhex needs to update his image? Thank you!! https://www.reddit.com/r/prowlarr/comments/uge52l/error_failed_to_load_indexers_from_api/?utm_medium=android_app&utm_source=share
  2. 6.10 RC3 still broken and being replace by self-signed
  3. The line wasn’t there so I added it. Testing now Update: it says it failed but looks like it did upload Sent from my iPhone using Tapatalk Pro
  4. Is there anything more? Now when I try I get a time out error when it’s over a 1GB Sent from my iPhone using Tapatalk Pro
  5. Looking for the same answer Sent from my iPhone using Tapatalk Pro
  6. Does RC2 work with this? Sent from my iPhone using Tapatalk Pro
  7. this is broken with Version: 6.10.0-rc1 I think when I reload Nginx it's replacing the cert A self-signed SSL certificate Select Yes to enable HTTPS and redirect HTTP to HTTPS. A self-signed SSL certificate will be generated automatically.
  8. Switch to the beta channel and then try updating Sent from my Pixel 4 XL using Tapatalk
  9. Been ask many many times. Read first post Sent from my Pixel 4 XL using Tapatalk
  10. here is mine server { listen 443 ssl; listen [::]:443 ssl; server_name hass.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { proxy_pass http://10.1.60.2:8123; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location /api/websocket { proxy_pass http://10.1.60.2:8123/api/websocket; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }
  11. Am I reading this right? You are running hass.io in a VM? If so you need to change the proxy config line proxy_pass to https://192.168.0.12:8123 Sent from my Pixel 4 XL using Tapatalk
  12. You'd just need to change the proxy pass line to http://vmip:port Sent from my Pixel 4 XL using Tapatalk
  13. No. It just makes it easier to use out of the box like plug and play. You just need to change the proxy pass to the IP and port Sent from my Pixel 4 XL using Tapatalk
  14. When I checked for updates when I was on version 18 it did not show version 20 for some reason but if I switch the beta it did show 20 once I got up to 20 on updates I switched back to stable Sent from my Pixel 4 XL using Tapatalk
  15. What you do is change the channel to beta inside of next cloud and then run the manual update through the docker console. It's super easy and I trust it more than the gui update Sent from my Pixel 4 XL using Tapatalk
  16. When I did my updates it forced me to go through all of them before I hit 20. Also ran into an issue where I was updating to the new update. During the manual update my unraid did auto update on Dockers. I was on part 6. When the docker came back up it would not get off of 6 and finish. After hours of troubleshooting even nuking NC and the DB and using appdata back up it was still stuck in the update. Then I finally found the update folder. It wasn't located in the appdata it was in the Nextcloud share. After deleting the folder I was able to restart the update process with success. Sent from my Pixel 4 XL using Tapatalk
  17. I think the whole point of duck is you can get a free subdomain. Yes you can use duck for DDNS to update your domains. Or you can have your domain use CF name servers and use the CF docker to update as a DDNS I feel CF is better and easier to work with. Also you can by domains from CF. I moved mine from google to CF Sent from my Pixel 4 XL using Tapatalk Edit: I did a quick search and apparently you cannot buy a domain directly from cloud flare yet. You can only transfer your existing domain.
  18. I'd buy a domain from cloudflare. There's two ways to go about this depending how the cloudflare DDNS docker works. For clarifications I don't use DDNS due to having a static IP from my ISP. First way is make a records and the cf docker updates them all. Don't know if the is possible. Or make one a record and use CF docker to update it then make c names for the other subdomain's. This way should be alot easier then dealing with duck [emoji1658] Sent from my Pixel 4 XL using Tapatalk
  19. I think SI1 needs to remake a video. I love them but needs a slight update. Sent from my Pixel 4 XL using Tapatalk
  20. Dutch the duck and buy a domain they're like seven bucks a year Sent from my Pixel 4 XL using Tapatalk
  21. I was wondering the same thing. So I went with 11 and changed Repository to postgres:13 as a guess and work. Sent from my Pixel 4 XL using Tapatalk
  22. go to each proxy.conf and # out # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd;
  23. If you get swag web loading page the the proxy config isn't setup right passing NC. Be best to post pictures of swag proxy config Sent from my Pixel 4 XL using Tapatalk
  24. https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=773685 Sent from my Pixel 4 XL using Tapatalk
  25. Post your nextcloud.subdomain.conf Sent from my Pixel 4 XL using Tapatalk

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.