gshlomi

Hi. I've had an issue with a warning in Nextcloud security & setup warnings saying "our web server is not properly set up to resolve “/.well-known/webfinger”. Further information can be found in the documentation 12." The solution was to add "rewrite ^/.well-known/webfinger /public.php?service=webfinger last;" to the /appdata/Nextcloud/nginx/site-confs/default file, in accordance with https://github.com/nextcloud/documentation/pull/877/files Personaly I hate changing nginx configuration that came with the docker itself. Is this a change that can be implemented in the container source?

Hi all. I think I've hit the same bug as reported by @phanb and at Just upgraded from a fully functioning 6.6.6 to RC4 to discover my array doesn't start. Everything worked great at 6.6.6. Disabling VT-d did the trick, but I'd like it back if possible. Any chance a patch/fix was missed in this build? Attached the diagnostics... Thanks 🙂 small-diagnostics-20190217-2117.zip

Same here... Anyone?

Hi folks. Any help would be appreciated. I'm getting this once in a while. Diagnostics file attached. small-diagnostics-20181106-0735.zip

Thanks for the quick reply. I did create the custom network (as mentioned in _readme) and doing a DNS resolution inside the letsencrypt container returns: root@2610736c55ba:/$ nslookup Transmission 127.0.0.11 Server: 127.0.0.11 Address 1: 127.0.0.11 Name: Transmission Address 1: 172.18.0.3 Transmission.docknet root@2610736c55ba:/$ nslookup transmission 127.0.0.11 Server: 127.0.0.11 Address 1: 127.0.0.11 nslookup: can't resolve 'transmission': Name does not resolve

Hi folks. Had to start over (too much messing around with the conf files and default)... So I've downloaded a new copy of LetsEncrypt (called it letsencrypt-temp, saved to an appdata folder by the same name) to create a new configuration, and noticed the sample files added for subdomains, which is a very elegant and helpful solution to what I need. The problem I'm having is with: All of my containers are defined with capitalization of their name (OCD anyone? ?) and I really want to keep it that way. I've tried for instance to change the "transmission.subdomain.conf" file to point $upstream_transmission to "Transmission" instead of "transmission", but it doesn't work. I get the error: in the error log. Any help would be appreciated.

Hi Did you solve this? Thanks

Can you access https://office.mydomain.com/loleaflet/dist/admin/admin.html ? You should receive something like: And did you setup the Collabora Online addon in Nextcloud settings?

Where did you install the container from? I've used the CLI, so my container settings looks totally different. This is the command parameters I've used: -t -d -p 192.168.1.100:9980:9980 -e 'domain=nc\\.XXXXX\\.org' -e "username=admin" -e "password=XXXXXXXXX" --restart always --cap-add MKNOD with the domain parameter points to my Nextcloud URL. This are my NGINX definitions for CODE: # Collabora Online server block server { listen 443 ssl; server_name office.*; include /config/nginx/ssl.conf; # static files location ^~ /loleaflet { proxy_pass https://192.168.1.100:9980; proxy_set_header Host $http_host; } # WOPI discovery URL location ^~ /hosting/discovery { proxy_pass https://192.168.1.100:9980; proxy_set_header Host $http_host; } # websockets, download, presentation and image upload location ^~ /lool { proxy_pass https://192.168.1.100:9980; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $http_host; } }

Hi folks Can't seem to make it work again. Changed "HTTPVAL" to "true" but I think m provider blocks port 80: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... 2048 bit DH parameters present SUBDOMAINS entered, processing Sub-domains processed are: -d www.mydomain.com -d dlg.mydomain.com -d cp.mydomain.com -d sr.mydomain.com -d sab.mydomain.com -d nc.mydomain.com -d office.mydomain.com -d plexpy.mydomain.com -d ha.mydomain.com E-mail address entered: mymail@gmail.com Different sub/domains entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created usage: certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ... Certbot can obtain and install HTTPS/TLS/SSL certificates. By default, it will attempt to use a webserver both for obtaining and installing the certificate. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for mydomain.com http-01 challenge for www.mydomain.com http-01 challenge for dlg.mydomain.com http-01 challenge for cp.mydomain.com http-01 challenge for sr.mydomain.com http-01 challenge for sab.mydomain.com http-01 challenge for nc.mydomain.com http-01 challenge for office.mydomain.com http-01 challenge for plexpy.mydomain.com http-01 challenge for ha.mydomain.com Waiting for verification... Cleaning up challenges Failed authorization procedure. ha.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://ha.mydomain.com/.well-known/acme-challenge/37kVVX3GQepKzvimZVl2ZWe9LAeWbGQHKtqriblf2eY: Timeout, cp.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://cp.mydomain.com/.well-known/acme-challenge/iblVH3jUuFK0ezr-4y8NjXmlxXc3-H7P8zzoKlKU-18: Timeout, mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://mydomain.com/.well-known/acme-challenge/-L6DgVivC4CAWB4w0P_ca32hKMlMg-TCnEQ8jOshKW8: Timeout, www.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.mydomain.com/.well-known/acme-challenge/m_urJrcV5bGi7_w_TgmtP9QFyNucA4-jegcU2sh-DMo: Timeout, dlg.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://dlg.mydomain.com/.well-known/acme-challenge/X2QMi7zQp0T2n3hyP8JGSs_rQJtTR9ly874lqvtS49g: Timeout, nc.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://nc.mydomain.com/.well-known/acme-challenge/nMZ0kONU3uVrPno4IMCs5yQbYjWmhOFSE5v7rqR-gkc: Timeout, office.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://office.mydomain.com/.well-known/acme-challenge/-q-KtpROO-cUzdDcm4oO5_84E-Lf4pA1lwmi6Akuvw4: Timeout, plexpy.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://plexpy.mydomain.com/.well-known/acme-challenge/HhpJuxmw8jg3fxgZuRKLqPjNn4QQTEvBVWg66IIGMNo: Timeout, sr.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://sr.mydomain.com/.well-known/acme-challenge/BqtOau3Gc_lu5_FsPApWjF_DoChm0ctSn8DGbnd6j14: Timeout, sab.mydomain.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://sab.mydomain.com/.well-known/acme-challenge/L6d2qCm8DXNUwlnjJW6pfKnJ484MS09u_InlLt9Jv_8: Timeout IMPORTANT NOTES: - The following errors were reported by the server: Domain: ha.mydomain.com Type: connection Detail: Fetching http://ha.mydomain.com/.well-known/acme-challenge/37kVVX3GQepKzvimZVl2ZWe9LAeWbGQHKtqriblf2eY: Timeout Domain: cp.mydomain.com Type: connection Detail: Fetching http://cp.mydomain.com/.well-known/acme-challenge/iblVH3jUuFK0ezr-4y8NjXmlxXc3-H7P8zzoKlKU-18: Timeout Domain: mydomain.com Type: connection Detail: Fetching http://mydomain.com/.well-known/acme-challenge/-L6DgVivC4CAWB4w0P_ca32hKMlMg-TCnEQ8jOshKW8: Timeout Domain: www.mydomain.com Type: connection Detail: Fetching http://www.mydomain.com/.well-known/acme-challenge/m_urJrcV5bGi7_w_TgmtP9QFyNucA4-jegcU2sh-DMo: Timeout Domain: dlg.mydomain.com Type: connection Detail: Fetching http://dlg.mydomain.com/.well-known/acme-challenge/X2QMi7zQp0T2n3hyP8JGSs_rQJtTR9ly874lqvtS49g: Timeout Domain: nc.mydomain.com Type: connection Detail: Fetching http://nc.mydomain.com/.well-known/acme-challenge/nMZ0kONU3uVrPno4IMCs5yQbYjWmhOFSE5v7rqR-gkc: Timeout Domain: office.mydomain.com Type: connection Detail: Fetching http://office.mydomain.com/.well-known/acme-challenge/-q-KtpROO-cUzdDcm4oO5_84E-Lf4pA1lwmi6Akuvw4: Timeout Domain: plexpy.mydomain.com Type: connection Detail: Fetching http://plexpy.mydomain.com/.well-known/acme-challenge/HhpJuxmw8jg3fxgZuRKLqPjNn4QQTEvBVWg66IIGMNo: Timeout Domain: sr.mydomain.com Type: connection Detail: Fetching http://sr.mydomain.com/.well-known/acme-challenge/BqtOau3Gc_lu5_FsPApWjF_DoChm0ctSn8DGbnd6j14: Timeout Domain: sab.mydomain.com Type: connection Detail: Fetching http://sab.mydomain.com/.well-known/acme-challenge/L6d2qCm8DXNUwlnjJW6pfKnJ484MS09u_InlLt9Jv_8: Timeout To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

Hi folks recently I've noticed in the Fix Common Problems plugin two new warnings after a manual scan: "Call Traces found on your server" & "irq 16: nobody cared found on your server". Attached is the diags file. Thanks small-diagnostics-20171202-0915.zip

Any update on the Origin issue? Finally installed a Win10 Gaming VM, Steam & UPlay installed easily (Steam over mapped network drive, UPlay over network share) but Origin doesn't install to mapping or share. UAC disabled, registry has EnableLinkedConnections set, yet an error everytime I try to install the Origin client. BTW - for people using VHD - why not add an additional HD to the VM itself from the unraid GUI instead? Thanks Shlomi

Thought about it. I'm in the process of creating a Win10 VM with GTX1060 passthrough for NVIDIA Gamestream to my Shield TVs, but haven't seen the Teslas support Gamestream or even Steam in-Home streaming... If you're from Israel, I've got a gift for you

Hi folks Received three used Tesla C1060 as a gift. Any thoughts on usage scenarios for these in a VM? Thanks Sent from my iPhone using Tapatalk

same here