CHBMB
-
Posts
10,620 -
Joined
-
Days Won
51
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by CHBMB
-
-
I do the same, I build all the Nvidia and DVB builds on a Unraid VM running on my main Unraid server. Dedicate 24 threads to it and 32GB. Power it off when I'm not doing anything with it though.
That was the whole reason I spent so damned long getting it working originally was so I didn't interrupt my wife's TV/Music. The restarts required were unacceptable to her.
It has to be said it's a **lot** easier now, @itimpi didn't you post some updated instructions somewhere after V6.2 which made it a whole lot easier?
-
TL:DR I remoted in, fixed it.
-
1
-
-
Personally I wouldn't, but I spend enough time here to kind of have my finger reasonably on the pulse without having to resort to RSS. Plus, I don't read the blog posts, but I don't feel I need to to as they tend to be about what Unraid can do, and I kind of know what it can do, and do everything I need it to, and there's nothing I want it to do that it doesn't do, if that makes sense.
And if there's something new I want it to do, I can generally get it to do it......
In fact, I should have married my Unraid server instead of my wife, she does none of the above and costs more money......
🤣
-
2
-
-
-
2 minutes ago, blaine07 said:
Sorry...
Sent from my SM-G975U using Tapatalk
The issue is that the docker command being run (repeatedly) is wrong and they're trying to grab a cert for www.
Maybe pics will work better. Delete this....
-
Just now, blaine07 said:
No cname a record set? Or with ddns is that not required?
Sent from my SM-G975U using Tapatalk
Dude, don't complicate things. It's not a Cname issue
-
Would help if you actually did what I asked.....
From your logs:
URL=nextcloud-eleanor.ddns.net SUBDOMAINS=www, EXTRA_DOMAINS= ONLY_SUBDOMAINS=falseAnd shown on your screenshot. Look, I'm not being funny here, but it would help if you actually read things properly. STOP POSTING screenshots
-
Actually ignore me.
It should be:
URL=nextcloud-eleanor.ddns.net SUBDOMAINS= EXTRA_DOMAINS= ONLY_SUBDOMAINS=false-
1
-
-
URL=ddns.net SUBDOMAINS=nextcloud-eleanor EXTRA_DOMAINS= ONLY_SUBDOMAINS=trueThis is how it should be configured.
You don't own the www.ddns.net url so you can't grab a cert for it.
-
-
@ijuarez Yeah, I know, problem is there's errors at every point in the chain and first principles have long been forgotten. If it doesn't grab a cert, then Nginx doesn't start, and then Nextcloud isn't going to work.
Until he/she gets LetsEncrypt working it's just wasting everyones time with a load of noise about Nextcloud.
@Tucubanito07 Here's what happens
1. You open the relevant ports on your router - you now have that correct
2. You start the LetsEncrypt container and it tries to grab certs
3. If certs are grabbed successfully Nginx starts up
4. Then you can setup Nextcloud and the reverse proxy side of things
5. Then once that's setup it should all work.
Problem is you're failing at step 1 and 2 and keep looking to step 5 to see if it's working.
-
1
-
-
Your port forwarding is now correct, it looks to me as though your nextcloud config is wrong.
Right, this is getting out of control. Lets stop for a moment, and forget about Nextcloud. Because unless LE is setup properly it isn't going to work.
I want you to remove the LetsEncrypt container, then recreate it and post the logs and for the love of God, please paste text and wrap it with code tags rather than post screenshots, reason being, if something then needs changing, we can copy and edit, whereas with screenshots we have to type it out.
I suggest you read this as well so you can post a docker run command and logs rather than screenshots.
-
2
-
-
2 hours ago, seer_tenedos said:
@CHBMB thanks for all the help on this and sorry to take so long to get a chance to test it.
Firstly i will point out how i am testing it incase other interested people want to try or can spot my mistake.
1. create a single node docker swarm (docker swarm init)
2. follow connectivity tests from https://gist.github.com/alexellis/8e15f2ea1af7281268ec7274686985ba
Sadly the latest patch above did not quite work for me. The network create and service create looks like they work
$ docker network create --driver=overlay --attachable=true testnet $ docker service create --network=testnet --name web --publish 80 --replicas=5 nginx:latest
but when i used curl below to test it could not connect
docker run --name alpine --net=testnet -ti alpine:latest sh / # apk add --no-cache curl fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz (1/5) Installing ca-certificates (20190108-r0) (2/5) Installing nghttp2-libs (1.35.1-r0) (3/5) Installing libssh2 (1.8.2-r0) (4/5) Installing libcurl (7.64.0-r1) (5/5) Installing curl (7.64.0-r1) Executing busybox-1.29.3-r10.trigger Executing ca-certificates-20190108-r0.trigger OK: 7 MiB in 19 packages / # curl web curl: (7) Failed to connect to web port 80: Host is unreachable / # ping web PING web (10.0.0.2): 56 data bytes
either something is still missing or i have set something up wrong.
I don't think the problem is with the kernel and docker, but I can't help you as I don't use swarm. Here's a reference to a working .config for swarm and as you can see with the last patched version there are all the same kernel modules present and some that aren't present in their config.
https://blog.hypriot.com/post/verify-kernel-container-compatibility/
-
2 hours ago, BLKMGK said:
Another big thanks! Loaded it up and it's running stable as an unRAID server. I'm still seeing Swarm issues with our project though and at this point I'm starting to suspect something else could be amiss so it would be helpful if someone else could test as well.
Same error about a route to host not being found.😣 I have spun up another standard Linux host as a VM and am waiting for my more knowledgeable friend to lend a hand adding it to our swarm and testing in case I screwed something up previously. Docker DNS seems pretty weird so diddling with it is confusing for me trying to troubleshoot it. The suggestion of a single host swarm seems like a good one and maybe we can try that on this test system. Unfortunately I'm about to take a trip away from home for a few weeks. I'll have a laptop and VPN access at least and my partner in crime will be coming along too so hopefully there will be some downtime to better troubleshoot this together. I'll update as I figure things out, I suspect my server will be getting a 12core Ryzen soon so I'd love to be able to utilize it fully
BTW it's pretty weird seeing the container appear and disappear as the swarm comes up and down let me tell you! unRAID currently doesn't have an XML file for it so it's being loaded at the CLI. I'll figure out how to more normally load it in the future once the silly thing works. A big THANK YOU to @CHBMB!
The only thing missing from that last build was filesystem stuff that isn't relevant to Unraid and
CGROUP_HUGETLBWhich I tried to activate, but couldn't.....
Disclaimer: I have no real idea what HUGETLB is and only a rudimentary understanding of C Groups.
Might take another look tonight.
-
2 hours ago, Squid said:
I don't know about you, but my wife does this all the time (usually in anger) and expects me to remember everything...
Oh yeah, and it always starts with the words
"Can we talk about something....."
It might be phrased as a question, but it's not, it's very much a statement, those words make my blood run cold as soon as I hear them, as my mind starts going over what it is I may (or may not) have done that I was supposed to (or not supposed to).
Last week it was a whole conversation about my driving..........
6 weeks previously.
I mean I love my wife, but really?!
-
@Lynxphp Use the preconfigured reverse proxy conf for Nextcloud and see if that works before you do anything else.
-
Try this one.....
root@matrix:/mnt/disk1/dvb# check-config.sh .config-swarm info: reading kernel config from .config-swarm ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: enabled (as module) - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_PROTO_TCP: enabled - CONFIG_IP_VS_PROTO_UDP: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT4_FS: enabled (as module) - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: missing enable these ext4 configs if you are using ext3 or ext4 as backing filesystem - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: enabled (as module) - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: enabled (as module) - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: enabled (as module) - CONFIG_NF_CONNTRACK_FTP: enabled (as module) - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000-
1
-
-
Yeah, exactly what@xaero says, you've got to understand that we're installing what are essentially desktop drivers onto a server.Is it by design that libXxf86vm.so.1 is missing?
It prevents use of nvidia-settingsnvidia-settings: error while loading shared libraries: libXxf86vm.so.1: cannot open shared object file: No such file or directory
To do so I did remove one bit that wouldn't compile without a full GTK and X11 stack iirc.
libnvidia-gtk I believe it was.
Sent from my Mi A1 using Tapatalk
-
Try again, I've deleted it from our repository,I did, but if I restarted the letsencrypt container, the container created another file without the .sample
Sent from my Mi A1 using Tapatalk
-
Then just rename it .sample
Hello CHBMB,
The thing is I don't even use the Docker container quassel-web. I don't even know what this app is. I am not sure how long this quassel-web-sub* in the proxy-confs directory to begin with. It is just all of a sudden, I have the quassel-web-subdomain.conf.sample and quassel-web-subfolder.conf. The subfolder doesn't have the extension of .sample.
This is the content:# Set base-url with docker run command env variable -e 'URL_BASE'='/quassel' and make sure Quassel-Web is running on http# with -e 'HTTPS'='false' or if you're using -e 'ADVANCED'='true' by editing config.json appropriatelylocation ^~ /quassel { # 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, also customize and enable ldap.conf in the default conf #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_quassel_web quassel-web; proxy_pass http://$upstream_quassel_web:64080;}
Sent from my Mi A1 using Tapatalk
-
On mobile at the moment. Post the contents of the quassel-web.subfolder.conf fileHas anyone started getting this log ?
nginx: [emerg] "location" directive is not allowed here in /config/nginx/proxy-confs/quassel-web.subfolder.conf:4
I had to remove the quassel-web.subfolder.conf file located in /mnt/cache/appdata/letsencrypt/nginx/proxy-confs/quassel-web.subfolder.conf
Sent from my Mi A1 using Tapatalk
-
Thanks man, much appreciated, it wasn't a dig at you at all. But I think now we have a degree of separation it should be easier to support for both of us.I've mentioned, at the top of my script to post any issues using it on the gist itself, rather than reporting them to Plex, Unraid, LSIO, or Reverend (the guy who's wrapper my script downloads.) So that I can filter issues that are caused by error on my part, or the end user's part. My apologies since this is apparently insufficient.
I'll go ahead and make a thread, though my ability to provide support will be limited as I am currently without a PC until its unpacked.
You can have as many notices telling people where to get support, they still ignore them, I know that.
Sent from my Mi A1 using Tapatalk
-
1 minute ago, ramblinreck47 said:
The decode script should become unnecessary here in the next couple of months. The Plex team has mentioned on their forum that they are working on adding the decode function.
That may well be the case, but the matter stands.
-
Don't take this the wrong way, but I don't need the hint.....I really meant to send that to you when I quoted. So you knew what that error was and get an idea on how to go from there.
Like I said, I know what I'm doing here.
Sent from my Mi A1 using Tapatalk
[support] limetech's docker repository
in Docker Containers
Posted
I don't think you understand how this works.
LimeTech maintain their own docker containers and publish templates for them.
What you're asking is you want a template making for an application you want to use, which is a common request, but what you probably don't realise is that a template is just an XML file, anyone can make one for any application.
Then just add the ports, variables and volumes you need to run the container. Takes like 5 minutes once you get used to it.