plantsandbinary

It seems that after a time for some reason using the current container: ghcr.io/alexjustesen/speedtest-tracker:latest I am getting 500 internal server errors. After a few days. I had removed the internal port mapping because I was using Cloudflare tunnel. So I didn't need any port mapping but it might be that this somehow breaks the container (as I just deleted the mappings from docker-compose). In any case. I reinstalled the container and kept the port mapping. Let's see if it works now. So far though, without that issue this version of the container works fine and it was last updated 16 days ago. I don't think anyone should be using any other version of this.

Has anyone else experienced the scenario where for some reason the database becomes 'read-only' after a few days of running non-stop and all gravity updates or individual additions to the whitelist fail?

Thanks I came here to ask this and I am following the exact same video lmao trying to get Authelia to work with Cloudfare Tunnels.

Any tip on how to use this with Cloudfare Tunnel? Both the tunnel and the docker container are running on the same network. I keep getting this error in the Cloudfare Tunnel log: 2023-06-18T12:37:55Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp xxx.18.0.xx:80: connect: connection refused" connIndex=3 dest=https://qbt.xtu.icu/favicon.ico event=0 ip=198.41.200.43 type=http Heimdall docker works fine with the following (it's the first one): EDIT: Fixed my problem 30 seconds after making this post by adding: :8080 at the end of my service URL in Cloudflare.

Can I please get some help in using LuckyBackup container to sync my files to Google Drive? I'm trying to set up a "remote" destination but nothing seems to be working and LuckyBackup is just hanging... I've tried following this too but this is for using SSH with another machine: https://www.spxlabs.com/blog/2022/1/3/backup-unraid-with-luckybackup I'm trying to use Google Drive as the destination.

Actually it seems to kill itself any time it does an HTTP challenge: [app ] Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0 [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf" [app ] } [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf" [app ] } [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf.err [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf.err" [app ] } [app ] [6/1/2023] [11:22:03 PM] [Nginx ] › ℹ info Reloading Nginx [app ] [6/1/2023] [11:24:14 PM] [SSL ] › ℹ info Testing http challenge for xtu.icu [app ] Uncaught SyntaxError: Unexpected end of JSON input [app ] FROM [supervisor ] service 'app' exited (got signal SIGILL). [supervisor ] service 'app' exited, shutting down... [supervisor ] stopping service 'nginx'... [supervisor ] service 'nginx' exited (with status 0). [finish ] executing container finish scripts... [finish ] all container finish scripts executed. ** Press ANY KEY to close this window **

I just tried to generate a wildcard cert using Cloudfare API token DNS challenge and the app spontaneously killed itself completely whilst doing it: [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] Let's Encrypt certificates cleanup - 2023/06/01 23:16:59 [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] 0 file(s) kept. [cert_cleanup] 0 file(s) deleted. [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info Current database version: none [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] auth Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] user Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] user_permission Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] proxy_host Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] redirection_host Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] dead_host Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] stream Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] access_list Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] certificate Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] access_list_auth Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [initial-schema] audit_log Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [websockets] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [websockets] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_host] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_host] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [http2_support] dead_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_scheme] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [forward_scheme] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] dead_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [disabled] stream Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [custom_locations] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [custom_locations] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] proxy_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [hsts] dead_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [settings] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [settings] setting Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client] access_list_client Table created [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client] access_list Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client_fix] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [access_list_client_fix] access_list Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [pass_auth] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [pass_auth] access_list Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_scheme] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_scheme] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_status_code] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [redirection_status_code] redirection_host Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [stream_domain] stream Table altered [app ] [6/1/2023] [11:16:59 PM] [Migrate ] › ℹ info [stream_domain] Migrating Up... [app ] [6/1/2023] [11:16:59 PM] [Setup ] › ℹ info Creating a new JWT key pair... [supervisor ] all services started. [app ] [6/1/2023] [11:17:01 PM] [Setup ] › ℹ info Wrote JWT key pair to config file: /opt/nginx-proxy-manager/config/production.json [app ] [6/1/2023] [11:17:01 PM] [Setup ] › ℹ info Creating a new user: [email protected] with password: changeme [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Initial admin setup completed [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Default settings added [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Logrotate Timer initialized [app ] [6/1/2023] [11:17:02 PM] [Setup ] › ℹ info Logrotate completed. [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [app ] [6/1/2023] [11:17:02 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [app ] [6/1/2023] [11:17:02 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [app ] [6/1/2023] [11:17:02 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [app ] [6/1/2023] [11:17:02 PM] [Global ] › ℹ info Backend PID 417 listening on port 3000 ... [app ] [6/1/2023] [11:17:02 PM] [Nginx ] › ℹ info Reloading Nginx [app ] [6/1/2023] [11:17:02 PM] [SSL ] › ℹ info Renew Complete [app ] [6/1/2023] [11:18:01 PM] [SSL ] › ℹ info Testing http challenge for *.xtu.icu [app ] Uncaught SyntaxError: Unexpected end of JSON input [app ] FROM [supervisor ] service 'app' exited (got signal SIGILL). [supervisor ] service 'app' exited, shutting down... [supervisor ] stopping service 'nginx'... [supervisor ] service 'nginx' exited (with status 0). [finish ] executing container finish scripts... [finish ] all container finish scripts executed. ** Press ANY KEY to close this window ** Obviously this is not supposed to happen...

I also just tried bypassing using Cloudfare's free SSL, and I tried to make a wildcard via NPM. Instead I now got this error: Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-6" --agree-tos --email "[email protected]" --domains "*.xtu.icu" --authenticator dns-cloudflare --dns-cloudflare-credentials "/etc/letsencrypt/credentials/credentials-6" 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: unrecognized arguments: --dns-cloudflare-credentials /etc/letsencrypt/credentials/credentials-6 at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) Looks like it's running the wrong command. So it seems like this container isn't configured properly.

Now onto the real issue. The one which is completely breaking my NginxProxyManager container. Remember this is a fresh installation. I am trying to add this custom cert to NPM. I've done that successfully. You can see here in the logs: [app ] [6/1/2023] [10:55:43 PM] [SSL ] › ℹ info Writing Custom Certificate: { [app ] id: 3, [app ] expires_on: '2038-04-01 15:40:00', [app ] domain_names: [ '"CloudFlare,' ], [app ] meta: { [app ] certificate: '-----BEGIN CERTIFICATE-----\r\n' + [app ] blah blah blah [app ] '-----END CERTIFICATE-----', [app ] certificate_key: '-----BEGIN RSA PRIVATE KEY-----\r\n' + [app ] blah blah blah [app ] '-----END RSA PRIVATE KEY-----' [app ] }, [app ] modified_on: '2023-06-01 22:55:43', [app ] created_on: '2023-06-01 22:55:43', [app ] owner_user_id: 1, [app ] provider: 'other', [app ] nice_name: 'Cloudfare - xtu.icu' [app ] } [app ] Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0 [app ] [6/1/2023] [10:56:02 PM] [Express ] › ⚠ warning Command failed: /usr/sbin/nginx -t [app ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) [app ] nginx: configuration file /etc/nginx/nginx.conf test failed [app ] [6/1/2023] [10:56:03 PM] [Express ] › ⚠ warning Command failed: /usr/sbin/nginx -t [app ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) [app ] nginx: configuration file /etc/nginx/nginx.conf test failed [app ] [6/1/2023] [10:56:05 PM] [Express ] › ⚠ warning Command failed: /usr/sbin/nginx -t [app ] nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) [app ] nginx: configuration file /etc/nginx/nginx.conf test failed You can see the errors here in color: This causes my entire container to crash continuously. This happens specifically when I go to a site on my list in NPM and select to use the custom cert I just added. I instead get those errors and this in the GUI: (excuse the blown out HDR screenshot) I have no idea what is causing this at all... Container is using just the normal settings... it seems the problem is that the certs are not being written to: "/etc/letsencrypt/live/npm-2/fullchain.pem" but I have no idea why... that's just my normal \\TOWER\appdata\NginxProxyManager-CrowdSec\letsencrypt folder... except for some reason it's completely empty??? This problem will allow me to start the container but it won't do anything and will just spam the logs with the errors in yellow.

I just installed Nginx-Proxy-Manager-Crowdsec and I am getting this in the logs when adding/removing SSL certs: [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] Let's Encrypt certificates cleanup - 2023/06/01 22:44:04 [cert_cleanup] ---------------------------------------------------------- [cert_cleanup] 0 file(s) kept. [cert_cleanup] 0 file(s) deleted. [app ] [6/1/2023] [10:44:04 PM] [Migrate ] › ℹ info Current database version: none [app ] [6/1/2023] [10:44:04 PM] [Setup ] › ℹ info Logrotate Timer initialized [app ] [6/1/2023] [10:44:04 PM] [Setup ] › ℹ info Logrotate completed. [app ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [app ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [app ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [app ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [app ] [6/1/2023] [10:44:04 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [app ] [6/1/2023] [10:44:04 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [app ] [6/1/2023] [10:44:04 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [app ] [6/1/2023] [10:44:04 PM] [Global ] › ℹ info Backend PID 451 listening on port 3000 ... [supervisor ] all services started. [app ] [6/1/2023] [10:44:05 PM] [Nginx ] › ℹ info Reloading Nginx [app ] [6/1/2023] [10:44:05 PM] [SSL ] › ℹ info Renew Complete [app ] Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0 [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf" [app ] } [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf" [app ] } [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf.err [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ⬤ debug Could not delete file: { [app ] "errno": -2, [app ] "syscall": "unlink", [app ] "code": "ENOENT", [app ] "path": "/data/nginx/proxy_host/1.conf.err" [app ] } [app ] [6/1/2023] [10:44:49 PM] [Nginx ] › ℹ info Reloading Nginx I'm having numerous issues with this container. The above logs pertain to me using my own cert given to me by Cloudfare. I am not sure if it's a problem getting an error that it cannot delete those files.

So I have to say, this container is set up in an extremely ....... bad way... When I installed this, I noticed later I have 2 folders in my /appdata... Pihole-Dot-Doh and pihole-dot-doh I removed the latter, second one. As I expected it was a left-over folder from another docker container that didn't work/was from an older docker image or repository. It's name didn't match case-sensitive the name of this docker container either. Welp. I just lost all of my settings. Now obviously I should have double checked, but ugh... due to the default spelling this container is making TWO directories with the SAME names in my /appdata directory... those above 2 I just listed. Now I bet 99% of people will not notice when creating or editing the container and checking the mapped directories... Gonna be great fun to completely remake my entire config... and add all those whitelisted domains again.. FFS! I highly recommend you change this. I have 41 containers on my system and none of them have ever made 2 directories in /appdata ever.

Is there anything I have to do with my router to ensure that qBittorrent-VPN is port forwarding properly that I am able to seed correctly?

I don't have this container, but I do have the Cloudfare-DNS container which updates the A Record automatically. I've since not got this error after removing the following containers: Nextcloud Cloudreve MariaDB

Agreed.

I figured it out. I had DHCP on my phone. It was set to use 192.168.1.1 as DNS 1 which is my router (blank for DNS 2). I changed from DHCP to static and 192.168.1.51 for DNS 1 which is my PiHole. I also enabled DNSSEC on my PiHole because it was enabled on my router. PiHole > Tools > Network was showing that not a single query had been made from my phone to the PiHole. As soon as I changed these settings it worked fine. Now it shows green for my phone in the PiHole that it is using the PiHole.

All apps on my Android phone are not receiving connections after installing the PiHole. The strange thing is that the PiHole log isn't showing any blocked connections at all. Apps like Supercell's Boom Beach aren't connecting to servers, and neither is another package tracking app Aftership. Both apps just report no connection at all. Taking them off my Wifi network which I am using the Pihole on, they work immediately. I think this is something to do with DoT/DoH. Does anyone have any ideas? I haven't changed any PiHole settings at all. Just installed it, set it as my default DNS etc. on my router. Nothing more.

I'm still offering a cash bounty for this. The problem does not occur if I don't proxy a url through Cloudfare but then I am exposing my IP address.

Traceback link: https://forums.unraid.net/topic/84681-odd-ngnix-error-filling-up-my-syslog/page/3/

This is why: It's an issue with Unraid still present in the latest version which the team hasn't commented or acknowledged it seems.

Yeah it's still happening on the latest version 6.11.5. I think some of us really need to push this issue and ask Unraid to drop nchan which is what is causing this error. It's been happening now for at least 3 years... I'm quite certain this is what caused some serious instability for me in previous versions of Unraid where my log would fill up and crash my entire server like many other people were reporting. I just had no idea why or where this problem was. As it's an issue specifically with Unraid and not with some Docker container, I really think it needs more eyes on it.

This is absolutely still a problem in 2023. Getting this on version 6.11.5. Is it possible for Unraid to move away from nchan? Seems ridiculous that this bug has existed for 3 years now.

Same here, just noticed. It's polluting my logs really badly. Please someone? EDIT: Seems this is why: It's an issue with Unraid still present in the latest version which the team hasn't commented or acknowledged it seems.

That's what I did. Put ghcr.io/alexjustesen/speedtest-tracker:latest in the repository box when making a container. You can just swap the current speedtest-tracker one with this one. Then check instructions here: https://docs.speedtest-tracker.dev/settings/authentication

Here's some more information because I am serious about getting this fixed: An example of resources that failed to load. A more deep example of the request: Proof that it's the "waiting for server" issue. So some Firewall problem, but where? Some of the images loaded, some did not? Why? This shows that it's text/html requests which are being blocked. Websocket requests and direct image requests seem to be fine? Same problem on Firefox btw, so it's not Chrome. Here's the plain request preview, so this is the response it's getting:

I am adding a bunch of images here to show my current setup, it should be super basic and nothing out of the ordinary at all: 1. LAN and WAN DNS pages on my router = Blank/use ISPs 2. NginxProxyManager Portforward for: 2086 (HTTP) and 2087 (HTTPS) [both these ports are accepted when proxying your connection in Cloudfare] 3. All my Docker containers on a separate network called "Public" which I made via one of the Youtube SpaceInvaderOne videos 4. Cloudfare set up as my site's DNS with all of my subdomains and host domain proxied through Cloudfare. 5. I am still getting the Cloudfare HTTP 522 errors on images etc. on my site... the weird thing is that they do load and a few refreshes of the page will generally make things work but something super weird is going on. I'll now PayPal the person who has the solution which fixes this issue $100 USD.