CoZ

Members
  • Posts

    159
  • Joined

  • Last visited

About CoZ

  • Birthday November 17

Converted

  • Gender
    Male
  • Location
    NY, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

CoZ's Achievements

Apprentice

Apprentice (3/14)

17

Reputation

  1. Fixed! No more "bootloop" and I was able to join on my own LAN. Whatever you did - thanks.
  2. Hey @ich777, you just pushed an update out to the Valheim docker. I applied the update and was unable to connect. Checking the logs, it seems to be stuck in some sort of "boot loop". EDIT: Seems to be everyone's server having issues. No servers are coming up in the server browser at all, much less mine.
  3. So strange things are happening now; the Docker is now encoding files that it has previously encoded. I have two TV shows in the watch folder and even though they have already been encoded, the app is encoding them again to HEVC. This is quite puzzling. Ok, I am an idiot. I had both plugins installed and running: Video Encoder H264 - h264_nvenc (NVIDIA GPU) Video Encoder H265/HEVC - hevc_nvenc (NVIDIA GPU) This is not the containers fault but, my own. Initially upon configuring everything I was in such a rush to get it back up and running I wasn't paying attention and just installed everything with NVIDIA GPU in it. So it seems as though I put the container into a vicious cycle, converting the same files to x264 and then x265. This would also explain why my RAM filled to capacity yesterday and my Dual Xeons spiked to 100% on all cores. I am leaving this post up for posterity in case anyone else has this issue. Check the plugins! lol
  4. Everything is a Plugin now. You're like Oprah now; "You get a plugin — you get a plugin — you get a plugin!" I am actually liking it the more I mess with it. At first, I thought "why have all the functionality taken out by default" but now I realize why you've gone that route; much easier to customize, much easier to nail down errors. Great Job on this Sir. I thought this container was a must-have installation for any Unraid build but now, this certifies it!
  5. That's the first place I went too (well after installing all the HEVC plugins) and it's just blank. I'll re-watch the video to see what I missed. I skimmed through it to get the container up and running again and that was priority 1.
  6. So THIS is why none of my files were being automatically compressed — there was a major update and everything has to be reconfigured. LoL! This shows you how bulletproof this docker was. I set it up once and never again had to look at it. Thanks for the video @Josh.5 - that helped. It did however take a few start / stop / restart of my docker container before it actually started to do anything. Not sure why that happened? Strangely that old container seemed to have skipped some files(?) because now I've got an entire season of a watched series undergoing a conversion. Perhaps now there is subtitle support as before there was not? EDIT: Just noticed that it no longer reports how much the file was "shrunk" like it did previously. Has that moved somewhere else?
  7. Started tinkering with this. I'm familiar with Nginx Proxy Manager and have a purchased domain. However, no matter what I do it will fail to connect via the FireFox Plugin. Any ideas? EDIT: I think I got it working. Apparently the "v2" after your domain name is VERY important.
  8. I know you're busy answering all sorts of questions and I've honestly stared at this for a good 10 minutes and still just dont' get it. I was going to backup my 'worlds' since my original friends have lost interest in the game and start fresh and then restore the world at a later point once more content drops. Then I thought why do that when I can just create another world/container so decided to come here and check before I tried to do something stupid. Someone already asked the question how to run two instances of a dedicated Valheim server and you referenced this post. I'm looking at your graphic which probably an idiot would understand but I guess I'm lower than idiot status because I don't understand what I'm supposed to do here to create a "new world" or "new server"...... Help? (and sorry for not understanding this)
  9. Ok, thanks for trying to help. I can't even find the certs to copy over to DS anywhere from the NGINX proxy/appdata - oh well. Every Google search for NGINX + OnlyOffice + Docker + DocumentServer doesn't really return much so this was the last hope.. LoL
  10. You just confused me. So you're saying I should be using THAT SSL cert for both the office.mydomain and the documentserver.mydomain or the other SSL cert for both office.mydomain & documentserver.mydomain? I'll uncheck the HSTS EDIT: Still the same error: Error when trying to connect (cURL error 60: SSL: no alternative certificate subject name matches target host name 'documentserver.MYDOMAIN.com' (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://documentserver.MYDOMAIN.com/healthcheck) Using the SSL for the Nextcloud reverse proxy Using the SSL for OnlyOffice proxy I get this error: Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 6.2.1.24) So not sure where to go from here... both result in completely different error messages.
  11. Found it! I thought it was "gone" since I removed it and placed the CERT from the Nextcloud SSL into the DocumentServer Proxy to try and fix this whole mess but it's still present on the system since I never deleted it, just selected the "office.mydomain.com" SSL # ------------------------------------------------------------ # documentserver.MYDOMAIN.com # ------------------------------------------------------------ server { set $forward_scheme http; set $server "192.168.1.102"; set $port 9090; listen 8080; listen [::]:8080; listen 4443 ssl http2; listen [::]:4443; server_name documentserver.MYDOMAIN.com; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-24/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-24/privkey.pem; # Block Exploits include conf.d/include/block-exploits.conf; # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years) add_header Strict-Transport-Security "max-age=63072000;includeSubDomains; preload" always; access_log /config/log/proxy_host-25.log proxy; location / { # Force SSL include conf.d/include/force-ssl.conf; # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years) add_header Strict-Transport-Security "max-age=63072000;includeSubDomains; preload" always; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; }
  12. I see no way to edit the cert that NGINX assigns to the subdomain. You just add a new certificate for the subdomain you're trying to forward and it assigns the cert. There are no options or configurations for the cert. I can only renew now or delete the cert. The only option to do anything at all is under the proxy host: Nginx variables available to you are: $server # Host/IP $port # Port Number $forward_scheme # http or https I went into appdata/NginxProxyManager/letsencrypt/keys and that directory is blank. I then took a look into NginxProxyManager/nginx/proxy_host and found a bunch of randomly titled files in there finally found one that points to something: # ------------------------------------------------------------ # office.MYDOMAIN.com # ------------------------------------------------------------ server { set $forward_scheme https; set $server "192.168.1.102"; set $port 444; listen 8080; listen [::]:8080; listen 4443 ssl http2; listen [::]:4443; server_name office.MYDOMAIN.com; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-24/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-24/privkey.pem; It continues on and I don't want to clutter up the thread any more by posting the whole thing if this isn't relevant.
  13. When I check the box that says Disable Certificate verification I get this message (When using the CERT from the nextcloud proxy): Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 6.2.1.24)
  14. I just tried to assign the same CERT that nextcloud uses to the document server and now I've gotten a new error message: Error when trying to connect (cURL error 60: SSL: no alternative certificate subject name matches target host name 'documentserver.MYDOMAIN.com' (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://documentserver.MYDOMAIN.com/healthcheck) so I don't think that's going to work that way either.