jang430

@CHBMB, ok, looks like all I can do is wait now.

Forgot my password for Nextcloud. Since it's a recently installed docker app, I chose to delete it. Upon selecting it once again for reinstallation, I get the following error: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nextcloud' --net='bridge' -e TZ="Asia/Shanghai" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -p '443:443/tcp' -v '/mnt/user/nextcloud/':'/data':'rw' -v '/mnt/cache/appdata/nextcloud':'/config':'rw' 'linuxserver/nextcloud' Unable to find image 'linuxserver/nextcloud:latest' locally /usr/bin/docker: Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate signed by unknown authority. See '/usr/bin/docker run --help'. The command failed. Any ideas?

@Fma965, Actually, restarted everything, except for letsencrypt docker app It was a gross oversight! After restarting, Deluge is working already. Can't get Sonarr to work yet. Will keep trying. At least I know it's working already. BTW, can OpenVPN Server and Letsencrypt (with NginX reverse proxy) docker container both be up at the same time? Meaning, even with Reverse Proxy running, I can still VPN into the NAS and manage it?

Almost there, but not quite. I'm following this guide up to here: Configuring Nginx as a reverse proxy. Now that we have both DuckDNS and Letsencrypt set up it’s time to configure Nginx as a reverse proxy. The first thing we need to do is access your appdata folder on windows, for me this is \\192.168.1.3\appdata. Once in your appdata folder go to the folder called letsencrypt then nginx then site-conf (so for me this is \\192.168.1.3\appdata\letsencrypt-\nginx\site-confs). This docker is pretty good for getting the configuration right automatically, however i have configured it to work with sonarr, radarr, htpc, deluge, plex, nextcloud and even netdata. the file can be downloaded from here. (i plan on explaining this file further in the future) Now simple delete the existing default file and replace it with the one linked above, make sure to rename it to default if it’s called default.txt. you may also need to run newperms to allow you to replace it. Next open the file in notepad++ or similar and change any references to 192.168.1.3 to your UnRAID server IP and also make sure the port numbers match your services. You also need to set the settings for these services, the webdir, webroot or base directory need to be set to the relevant paths. HTPC-Manager is /htpc and the port is 8085 Sonarr is /sonarr and the port is 8989 Couchpotato is /couchpotato and the port is 5050 Radarr is /radarr and the port is 7878 Deluge is /downloads (could be changed to deluge if preferred) and the port is 8112 Plex requires the advanced setting “Server > Network >Custom server access URLs” to include “https://YOURSUBDOMAIN.duckdns.org”. Nextcloud is /nextcloud, the port is 444 and requires manual modification (see section below) Netdata is /netdata and the port is 19999 (slightly different syntax in the nginx config file) Once this is done you can restart the dockers for these services and you should be able to access your services from https://YOURSUBDOMAIN.duckdns.org/service, if you need help with additional services or having any issues at all let me know in the comments below. I downloaded file from link above, clicked on it, and selected download. It gave me a text file. Put the text file onto the folder mentioned above ....\site-confs, then renamed it to default, without any file extension. Used Notepad++ to edit all IP address from 192.168.1.3 to 192.168.1.104 (mine). Since I am using sonarr anyway, I just restarted the sonarr docker container, and accessed https://jxxxx1.duckdns.org/sonarr , and I arrived to the page that says: Welcome to our server The website is currently being setup under this address. For help and support, please contact: [email protected] I also changed radarr to couchpotato, and changed port number to 5050, upon accessing https://jxxxx1.duckdns.org/couchpotato, I also reach the same "Welcome to our server" page. Don't know what's wrong. Please help.

Still the same. Failed authorization procedure. jxxxxx1.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://jxxxxx1.duckdns.org/.well-known/acme-challenge/boKxf6D_5_zgK27HQt2LSwowiMaHcicSWgtnm12EDbY: Connection refusedIMPORTANT NOTES:- The following errors were reported by the server:Domain: jxxxxx1.duckdns.orgType: connectionDetail: Fetchinghttp://jxxxxx1.duckdns.org/.well-known/acme-challenge/boKxf6D_5_zgK27HQt2LSwowiMaHcicSWgtnm12EDbY:Connection refusedTo fix these errors, please make sure that your domain name wasentered correctly and the DNS A/AAAA record(s) for that domaincontain(s) the right IP address. Additionally, please check thatyour computer has a publicly routable IP address and that nofirewalls are preventing the server from communicating with theclient. If you're using the webroot plugin, you should also verifythat you are serving files from the webroot path you provided.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

Yup, it starts correctly. But, not accessible. Not the same as just plain Nginx

Hi. It works! I forwarded port 80 to internal port 85, and shows the same display screen above. I accessed from outside the house, via IP, and via jxxxxx1.duckdns.org, with same successful result. May I know what to do next?

I guess this means it's working. So Duckdns is having issue? Got to go, but please leave me a message if you see this.

Unfortunately, my ISP tries to block whatever they can, and no other way to get them to cooperate.

Anything I can do with it? Any other confirmation I can do? I'd really like to get this working. Did I do everything right so far from posts above? Maybe I made some slight mistake

Hi. But it is. I also restarted my duckdns docker container.

Hi. Sorry for adding so much info. BTW, inverted the order, still the same error.

Hi. I can't get this to work. Logs on letsencrypt says: Backwards compatibility check. . .No compatibility action needed2048 bit DH parameters presentSUBDOMAINS entered, processingSUBDOMAINS entered, processingOnly subdomains, no URL in certSub-domains processed are: -d jxxxx1.duckdns.orgE-mail address entered: [email protected] validation is selectedGenerating new certificateSaving debug log to /var/log/letsencrypt/letsencrypt.logPlugins selected: Authenticator standalone, Installer NoneObtaining a new certificatePerforming the following challenges:http-01 challenge for jxxxxx1.duckdns.orgWaiting for verification...Cleaning up challengesFailed authorization procedure. jxxxx1.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://jxxxxx1.duckdns.org/.well-known/acme-challenge/PwoD5ycQWe5M5Azj-oXI-x0v60wOQmwllxm-fXr4Iio: Timeout during connect (likely firewall problem)IMPORTANT NOTES:- The following errors were reported by the server:Domain: jxxxxx1.duckdns.orgType: connectionDetail: Fetchinghttp://jxxxxx1.duckdns.org/.well-known/acme-challenge/PwoD5ycQWe5M5Azj-oXI-x0v60wOQmwllxm-fXr4Iio:Timeout during connect (likely firewall problem)To fix these errors, please make sure that your domain name wasentered correctly and the DNS A/AAAA record(s) for that domaincontain(s) the right IP address. Additionally, please check thatyour computer has a publicly routable IP address and that nofirewalls are preventing the server from communicating with theclient. If you're using the webroot plugin, you should also verifythat you are serving files from the webroot path you provided.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 Hope some of you can shed some light.

yes, I see it. @vanes, thank you! The setting in the bios did it.

noted, will try vanes. What does he mean by having trouble to get /dev/dri to show up? I don't know whether mine is considered as showing up currently, or not yet. How do I check this?

this is my screenshot

@vanes, did them both. Still getting the following: I followed your go file. Is it the file in flash/config/go? Modified it using notepad.

@vanes, hi. Can I ask how you got hardware transcoding working? Are you using official embyserver docker? I have a working embyserver, and can stream from it. What I don’t have at this time is hardware transcoding. What steps did you take to get it working? What needs Ed’s to be in the go file? Where do I put —device /dev/dri/renderD128? Putting it in extra parameters gives me errors. I already selected va api in embyserver transcoding settings. I also see va api device as /dev/dri/renderD128 already.

Wow, sounds like a daunting task:-) Never studied let's encrypt yet. Is there any setup guide that's been written before? Sent from my iPhone using Tapatalk

Another question, after installing Collabora online, I went to Nextcloud settings, and set Collabora Online serverURL (and port) of the Collabora Online server that provides the editing functionality as a WOPI client. I went in to a folder, and started to create a document, presentation, spreadsheet, I got the following error. Internal Server Error The server was unable to complete your request. If this happens again, please send the technical details below to the server administrator. More details can be found in the server log. Technical details Remote Address: 192.168.1.1 Request ID: vw9L4toRNjdFS I think this is what's on the logs: Error richdocuments GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: self signed certificate How do I fix this?

Hi. I just recently tried Nextcloud. I'm so impressed, never thought it will give such functionality to my NAS. I have a concern. Mostly my files are not very important, and I use drives pulled from enterprise servers before. I created a Nextcloud share, just a single drive. Assuming Parity drive, nor Cache drive doesn't fail, is this drive (where Nextcloud share exist) still considered safe, since I am also using the parity? So If the drive fails, it can still be recovered? If for whatever reason, the Nextcloud docker app goes crazy, can all files uploaded to it still be seen directly via disk share? I've actually confirmed this already, just want to know whether there's something I'm missing.

Hi. Don't know where exactly to post, so I'll ask here. I'm using CP/ Deluge. I have CP searching for movies via magnetdl, and rarbg. When it finds one, it sends it to Deluge for download. In my Deluge, I have files downloading at /downloads/deluge/temp, and CP label of movies get moved to /downloads/couchpotato/complete upon completion. I have in my CP renamer settings to rename movies from /downloads/couchpotato/complete/ to /movies (a share on my array). The movie gets downloaded, and Movie appears in /downloads/couchpotato/complete/, CP sees it, ang moves it to /movies (share), but on an occasion or two, the main movie isn't there. All the other nfo files, that come with the folder is there, but the main movie is neither in /movies (share) nor /downloads/couchpotato/complete/. But I did see it finish download. Don't know where to start troubleshooting. Hope you can shed some light. Deluge settings: Stop seeding when ratio reaches: 0 CP Downloader settings: Deluge is checked Lablel: movies Directory: left blank Completed Directory: left blank Remove Torrent: unticked Remove Files: unticked

I have my Sabnzbd download to /downloads/, which, in my case, is /mnt/user/appdata/downloads/. So when Sonarr finds NZBs, it sends to Sab, and downloads to that folder. After which, Sonarr picks it up during post process. In Deluge, I transfer completed downloads to /downloads/ as well, using the same folder. It's still being picked up by Sonarr. I read that we have to be consistent, hence, in CP, I also use /downloads/, so it can be picked up during post process. Won't there be any chance wherein Sonarr and CP both see the same files, and there might be an occassion that it's the same title? E.g. Suits TV show, and just in case, there is another Suits The Movie. What's the best practice? Will it be possible to have CP monitor /downloads/Couchpotato? And have Deluge download all shows labelled Movies to /downloads/ Couchpotato?

@jonathanm, thanks, I indeed overthinked it @CHBMB, sorry, I didn't. Instead, I clicked on ? . Your instructions did the trick. Do I need to change write permissions if downloaded with the new username and password that I created? I used xxxxx:xxxxxx:10. Will I have problems moving files here and there? Permission issues? Last question, Sonarr currently connecting to Deluge with default admin as username, and password. Do I have to change it? Although I confirmed it's connecting as it is.

Sorry, I'm lost with @sparklyballsinstructions as to how to add a deluge user, with the deluge app being in a docker container. Kindly point out. I'd also like to let you know that deluge with Sonarr is working fine, and can communicate, and send torrents to deluge properly. CP can't see deluge. @CHBMB, sorry I totally didn't understand what you're pointing out with the link above.