H2O_King89

Been ask many many times. Read first post Sent from my Pixel 4 XL using Tapatalk

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; } }

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

You'd just need to change the proxy pass line to http://vmip:port Sent from my Pixel 4 XL using Tapatalk

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

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

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

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

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.

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

I think SI1 needs to remake a video. I love them but needs a slight update. Sent from my Pixel 4 XL using Tapatalk

Dutch the duck and buy a domain they're like seven bucks a year Sent from my Pixel 4 XL using Tapatalk

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

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;

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

https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=773685 Sent from my Pixel 4 XL using Tapatalk

Post your nextcloud.subdomain.conf Sent from my Pixel 4 XL using Tapatalk

I would guess that's an issue how you have your reverse proxy setup. Are you using swag? What it's saying is when it appends that directory to the end of your domain it's not resolving. For example https://nextcloud.domain.com/.well-known/carddav Sent from my Pixel 4 XL using Tapatalk

If I'm reading this correctly you're asking if you should have it in both places? You only need it in one place That's why I uncommented and restarted next cloud and it worked fine. Sent from my Pixel 4 XL using Tapatalk

Yes that looks like the right directory path. My default file had the header but it was comment out "#" I removed the comment. If your file doesn't have the header you can add it there. You can also do it like this video also. There is more then one way to skin a cat [emoji74] Sent from my Pixel 4 XL using Tapatalk

How are you having the same problem if you can get to your settings and see those errors? The first error it's easy to fix. In the config file they have that header commented out in the docker. I'm not at home and trying to go off the top of the my head but it's in the next cloud app that a folder and then in the NGINX folder Sent from my Pixel 4 XL using Tapatalk

What's the new URL? Sent from my Pixel 4 XL using Tapatalk

If you get you probably don't have your SWAG NC conf setup right. Sent from my Pixel 4 XL using Tapatalk

Add it in? Sent from my Pixel 4 XL using Tapatalk

look at post 3778 and try that Sent from my Pixel 4 XL using Tapatalk