H2O_King89
-
Posts
337 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by H2O_King89
-
-
Been ask many many times. Read first postHello,
How can I update from 19.0.1 to 20.0.1 ?
The docker version seems "up to date".
Thanks !
Sent from my Pixel 4 XL using Tapatalk
-
7 minutes ago, casperse said:
Yes its the same thing.... 🙂
set $upstream_app 192.168.0.12; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port;I just used the variable in the last line
proxy_pass http://192.168.0.12:8123;
But I can see that it is sort of working seem to be some difference between this reverse proxy and the one Synology sets up I get to the webpage
Looking at the log from my app I can see a new error message: shared.webhookError 1
Very strange?
I made this for the Synology VM:
server { listen 443 ssl; listen [::]:443 ssl; server_name mydomain.dk; include /config/nginx/ssl.conf; # add_header X-Frame-Options "SAMEORIGIN" always; add_header Strict-Transport-Security "max-age=15768000; includeSubDomians; preload;"; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_pass https://192.168.0.10:5001; proxy_max_temp_file_size 2048m; } }Synology domain looks to be working perfectly, any changes that I need to make?
Its for a domain not a sub domain and I used the template for NextCloud as a base
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; } }-
1
-
-
Yes I see the docker name should be the IP (Making this to complicated)
I tried but it doesn't seem to workinclude /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.0.12; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port;
I tested and its working accessing: http://192.168.0.12:8123/lovelace/default_view
(The domain is getting cert. log file and I tried doing the mysub.* wildcard but with no effect
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:portHi All
I am moving my last reverse proxy from my Synology box (Built in funct. with lets encrypt)
Already have it working for all my dockers! and the instruction to setup and use the special "Proxynet" in Docker
But my last servers are running as VM's not dockers so I cannot use the Network type: "Proxynet"
I have two servers running as VM left with fixed IP's (Both virtual lan on Br0)
Found the template for Home assistant:
# make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base urlserver { listen 443 ssl; listen [::]:443 ssl; server_name home.mydomain.dk; 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; # enable for Authelia #include /config/nginx/authelia-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app homeassistant; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; }}But not sure how to point it to a specific mysub.mydomain.dk?
Or adding the IP (I would prefer not to have any mysub.* as wildcard have 4 different domains added (The work fine)
Tried looking through the posts but so far have not succeeded getting this working (Trial & Error)
Hooping to adjust the above to work with Synology port 5001 https running as a VM
Thanks!
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 porti have problems with letsencrypt and emby. Is it acually REALLY nessesary to make a user defined docker bridge network??
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 stableIsn't the 20.0.1 supposed to be stable? Why should i go to beta first? Just curius!
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 updateWill be the updated offered later? I' dont feel much confident doing the update manually. Not yet atleast!
Is the updates roll out gradually? Do you know how they select to which the update rolls?
Thanks!
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.Do the manual update using the command line. Be sure to update to the latest version of 19 before going to 20.
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.This part makes me think DuckDNS isn't required for your own domains, but my domain registrar doesn't have their own API to update & I also can't get a static IP off my ISP.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.
I'm a total newbie to these things so I'm trying to figure this stuff out.....
How would you go about ditching dynamic DNS (duck dns)? Are you saying it's better to create a static wan IP and use A records instead of cnames that point to the dynamic dns? If so, what are the benifits?
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.Most people are still going to use duckdns even if they buy a domain, unfortunately, as space invader says so...
Sent from my Pixel 4 XL using Tapatalk
-
Dutch the duck and buy a domain they're like seven bucks a yearok, as i said in the post before, the problem is the same. I have tried to make the config as you suggest, and i got the same error.
I have made a check on the ports, they are open.
docker log swag rev. 1.txt
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.Which docker did you used? Did you instal from cli? On Community apps i can see up to v11. Also which redis docker.
Thanks!
Sent from my Pixel 4 XL using Tapatalk
-
11 minutes ago, madaroda said:
Latest update to swag appears to have blocked secure access to all my installed dockers. I can access the dockers locally via http://IP address:port, but https://anydocker.mydomain.com asks for a user name and password, none of which are accepted and result in a "403 forbidden" error. Thinking it may be related to a previous htpasswd configuration, I reinstalled swag (copying over only the proxy-conf files I am using and the entire dns-conf directory to the new installation). Still no access. I don't have an .htaccess file in config/nginx. Where do I being to look for a fix? I am stumped.
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 configI am trying to setup NextCloud with a domain name (I would prefer not using subdomains). I followed the spaceinvader one tutorial where he mentions using a domain name and I couldn't get Swag to redirect to nextcloud. I then tried following the linuxserver.io letsencrypt-nginx-starter-guide and had the same problem. Both times I inserted the domain name into where the subdomains would go and I would get the defaulting to a landing page created by the docker. Tried using NginxProxyManager and was able to get everything working but ran into other compatibility issues with setting up windows clients for nextcloud.
Is there anything in particular I need to do differently with just the domain name?
Sent from my Pixel 4 XL using Tapatalk
-
https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/?do=findComment&comment=773685make sure that your dns has a cname set for nextcloud# assuming this container is called "swag", edit your nextcloud container's config# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":# 'trusted_proxies' => ['swag'],# 'overwrite.cli.url' => 'https://nextcloud.your-domain.com/',# 'overwritehost' => 'nextcloud.your-domain.com',# 'overwriteprotocol' => 'https',## Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this:# array (# 0 => 'xxx.xxx.0.1:444', # This line may look different on your setup, don't modify it.# 1 => 'nextcloud.your-domain.com',# ),server { listen 443 ssl; listen [::]:443 ssl; server_name nextcloud.*;include /config/nginx/ssl.conf;add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;"; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app nextcloud; set $upstream_port 443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; }}
Sent from my Pixel 4 XL using Tapatalk
-
Post your nextcloud.subdomain.confI'm using swag. How do I fix that?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?Ayye it worked. How about the other two issues?Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation.
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."add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;" This is the one right? It's saying waring to only add the preload option once you read about the consequences. I add the header with the other header blocks or does it matter?
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.nextcloud\nginx\site-confs\default ? Add the codes from this video? This is all spanish to me. I'm a hardcore noob.
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 do I fix these 3 warning alerts? The Space Invader Tutorial is no longer valid with Swag. I need help. I'm losing my mind trying to figure this out.
"
The "Strict-Transport-Security" HTTP header is not set to at least "15552000" seconds. For enhanced security, it is recommended to enable HSTS as described in the security tips [emoji658].
Your web server is not properly set up to resolve "/.well-known/caldav". Further information can be found in the documentation.
Your web server is not properly set up to resolve "/.well-known/carddav". Further information can be found in the documentation."
Also bonus points if someone can tell me how to change the temp in the dashboard to F instead of C.
How are you having the same problem if you can get to your settings and see those errors?I'm having the same problem let me know if you get it fixed.
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?The node red team changed their URL..... I changed the template but existing users of a template do not get automatically changed by community applications app to avoid overriding existing parameters
Sent from my Pixel 4 XL using Tapatalk
-
If you get you probably don't have your SWAG NC conf setup right.Tried that, didn't do anything. Still get this error:
Sent from my Pixel 4 XL using Tapatalk
-
Add it in?Any thoughts on this? [emoji4]
Sent from my Pixel 4 XL using Tapatalk
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted
Sent from my Pixel 4 XL using Tapatalk