surfshack66

Is there a best practice for configuring user shares to minimize drives spinning up, etc? Specifically, how should a "downloads" or "media" folder be configured?

Interesting. Thanks for the help.

The default folder (in this template) where Radarr will look for downloads is /downloads, correct? If so, why is DownloadedMovieImportService looking in /data?

Publish it, please I think its fair to include this per https://github.com/linuxserver/docker-letsencrypt/tree/dns "This option is only for advanced users. We will not answer any questions related to this setting. If you need to ask questions, this is not meant for you." I understand it would be a huge support headache, however, the use of forums for support isn't the best either. How many times have people asked the same question because they didn't read or missed an earlier post? I'm certainly at fault for this too. In any case, I don't think its wise to withhold features just because its too hard to support.

DNS-01 challenge needs to be added to this docker per this update: https://community.letsencrypt.org/t/2018-01-11-update-regarding-acme-tls-sni-and-shared-hosting-infrastructure/50188

My ISP blocks port 80, so changing that value won't work in my situation. Subscribed to the thread..hopefully a fix is found soon.

@Frank1940 Thanks, that worked. So if I'm understanding this correctly, MS is blocking access to SMBv1, yet Unraid still uses this?

I've had windows 10 automatic updates off for a while and just decided to turn it back on. After upgrading, I'm no longer able to access shares via //tower or //ipaddress. I've tried editing group policy to allow guest access, and unraid is set to local master. Also, the windows 10 vm and unraid are both on the same workgroup. I think I'm at a lose. Any suggestions?

Fans are still working but I added two more, specifically in the front. Dust filters were clean too. As I'm typing this, temps for HDD returned to normal. Went from 47C to 36C. Amazing. I'll keep on eye on this for sure. If anyone is interested, I added two of these https://www.amazon.com/gp/product/B00CP6QLY6/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1

I'll look into getting another fan to put in front. My case is the Fractal Design R5 and I've been leaving the front door open but didn't seem to make a difference. The PC is running 24/7 but has been for over a year now and all of a sudden started running hot. I wanted to put space between each drive in the cage but the power cables wouldn't reach.

I have pushbullet configured to notify me of notifications. It seems lately I've been receiving numerous notifications that some of my drives are hot. Currently, my 6tb parity is 45C, 2tb array drive is 48c and another 2tb is 45c. I could change the range of what unraid considers hot, but I'm wondering if there's something I've misconfigured or if there are other alternatives.

@Bungy Did you ever get this working? I've been running BI for a couple days now and compared to ZM its much better.

Awesome! Thanks @dlandon.

I have a control script (PTZ) that is supposed to be placed in this folder /usr/share/perl5/ZoneMinder/Control Where would I put this script within /mnt/user/appdata/zoneminder?

Its odd that the port is open when the nginx container is started but closed when the letsencrypt container is started. I'm at a loss. Also, I removed the URL redirect but then received a different error from letsencrypt below. FYI - Port 80 is definitely blocked by my ISP, so the domain won't reach my IP then. Failed authorization procedure. sub1.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for sub1.domain.com, sub2.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for sub2.domain.com IMPORTANT NOTES: - The following errors were reported by the server: Domain: sub1.domain.com Type: connection Detail: DNS problem: NXDOMAIN looking up A for sub1.domain.com Domain: sub2.domain.com Type: connection Detail: DNS problem: NXDOMAIN looking up A for sub2.domain.com

Yes I can. I stopped letsencrypt and started an nginx container. When the letsencrypt container is started "canyouseeme.org" does not connect to 443, but the nginx container does connect.

No thats not my NAT rule. Thats my permit inbound traffic rule. The source IP (lets encrypt) is accessing my webserver. The rule allows IPs originating from North America.

Assuming the ip is correct, your router seems to be not forwarding the request on port 443 to the container properly I thought so too but I just checked my firewall logs.

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 sub1.domain.com -d sub2.domain.com E-mail address entered: 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 cert. certbot: error: argument --cert-path: No such file or directory Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Obtaining a new certificate Performing the following challenges: tls-sni-01 challenge for domain.com tls-sni-01 challenge for sub1.domain.com tls-sni-01 challenge for sub2.domain.com Waiting for verification... Performing the following challenges: tls-sni-01 challenge for domain.com tls-sni-01 challenge for sub1.domain.com tls-sni-01 challenge for sub2.domain.com Waiting for verification... Cleaning up challenges Failed authorization procedure. sub1.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Connection refused, sub2.domain.com (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Connection refused IMPORTANT NOTES: - The following errors were reported by the server: Domain: sub1.domain.com Type: connection Detail: Connection refused Domain: sub2.domain.com Type: connection Detail: Connection refused To fix these errors, please make sure that your domain name was entered correctly and the DNS A 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. /var/run/s6/etc/cont-init.d/50-config: line 127: cd: /config/keys/letsencrypt: No such file or directory [cont-init.d] 50-config: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

Yes, port 443 is open and forwarded to server.

Ok. I know this is beyond the scope of support for this docker, so any help would be appreciated. I have a domain with namecheap and an A record pointing to my IP address. Would having a URL redirect record https://mydomain.com suffice? Reason I'm asking is because I'm getting a "connection refused" error and even though my ISP blocks port 80, I thought redirecting to https would force port 443 (which is open on my server)

Has anyone been able to configure letsencrypt when ISP blocks port 80? 443 is open but unable to open 80. Any known workarounds? Is port 80 definitely needed?

thanks I'll read through the manual

thanks. so..once a connection is configured it will automatically select that connection when logging in. so i can no longer reconfigure that connection from the gui. however, the user-mapping file in appdata didnt seem to update with the connection configuration... how can I change the connection settings then?

In your successful RDP connection, do you see the following warning?