[Pinhole/Adguard cause cloudflare error 522 when enabled]

I hope someone can help me.

 

My setup includes pihole, nginx proxy manager, and my various tools (nextcloud, sonarr, radarr, organizer etc) and I use cloudflare. I also recently moved to a .ovh domain name.

 

I've been using my setup for years, however after upgrading to 6.12.4 when I try to connect to my various applications via domain name I get a cloudflare error 522. I have tried removing the proxy/ changing the security on cloudflare with no joy. I finally found if I disable pihole it works fine. I tried deleting pihole and reinstalling it thinking the problem was a rouge setting that I couldn't find. That didn't work. So I tried an alternative Adguard and was also getting the 522 error when it was enabled.

 

I have searched google and various forums with no success.

 

I'm at a loss and don't know what to try next any suggestions would be welcome. YouTube videos etc helped me to get my setup to were it was, so I'm a novice with regards terminal etc so please be gentle 🙂

 

Thanks 

[[Support] binhex - qBittorrentVPN]

Hi Guys,

I hope someone can help. All was working yesterday on my install of binhex-qbittorrentvpn. This morning when I try to log in I get a log in error. I check the logs and I see the below, I have changed nothing recently. Any help would be appricated. I'm using the binhex/arch-qbittorrentvpn repository and am on the latest version. Thanks
 

Quote

(N) 2022-06-27T10:24:39 - Using config directory: /config/qBittorrent/config
(N) 2022-06-27T10:24:39 - qBittorrent v4.4.3.1 started
(N) 2022-06-27T10:24:39 - Using config directory: /config/qBittorrent/config
(I) 2022-06-27T10:24:39 - Trying to listen on: 0.0.0.0:20893,[::]:20893
(N) 2022-06-27T10:24:39 - Peer ID: -qB4431-
(N) 2022-06-27T10:24:39 - HTTP User-Agent is 'qBittorrent/4.4.3.1'
(I) 2022-06-27T10:24:39 - DHT support [ON]
(I) 2022-06-27T10:24:39 - Local Peer Discovery support [ON]
(I) 2022-06-27T10:24:39 - PeX support [ON]
(I) 2022-06-27T10:24:39 - Anonymous mode [OFF]
(I) 2022-06-27T10:24:39 - Encryption support [ON]
(I) 2022-06-27T10:24:39 - UPnP / NAT-PMP support [ON]
(I) 2022-06-27T10:24:39 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Wed Jun 1 01:25:04 2022.
(N) 2022-06-27T10:24:39 - Using built-in Web UI.
(N) 2022-06-27T10:24:40 - Web UI translation for selected locale (en) has been successfully loaded.
(N) 2022-06-27T10:24:40 - Web UI: Now listening on IP: *, port: 8080
(I) 2022-06-27T10:24:40 - Successfully listening on IP: 127.0.0.1, port: TCP/20893
(I) 2022-06-27T10:24:40 - Successfully listening on IP: 127.0.0.1, port: UTP/20893
(I) 2022-06-27T10:24:40 - Successfully listening on IP: 10.11.159.222, port: TCP/20893
(I) 2022-06-27T10:24:40 - Successfully listening on IP: 10.11.159.222, port: UTP/20893
(I) 2022-06-27T10:24:40 - Successfully listening on IP: 172.17.0.3, port: TCP/20893
(I) 2022-06-27T10:24:40 - Successfully listening on IP: 172.17.0.3, port: UTP/20893
(I) 2022-06-27T10:25:05 - Detected external IP: 181.214.206.222
(W) 2022-06-27T10:25:26 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:25:27 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:25:37 - WebAPI login failure. Reason: invalid credentials, attempt count: 1, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:25:58 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:26:13 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:26:26 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:26:38 - WebAPI login failure. Reason: invalid credentials, attempt count: 2, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:26:40 - WebAPI login failure. Reason: invalid credentials, attempt count: 3, IP: ::ffff:172.17.0.1, username: 
(W) 2022-06-27T10:26:42 - WebAPI login failure. Reason: invalid credentials, attempt count: 4, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:26:49 - WebAPI login failure. Reason: invalid credentials, attempt count: 5, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:26:49 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:26:50 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:26:53 - WebUI: Invalid Host header, port mismatch. Request source IP: '::ffff:172.17.0.1'. Server port: '8080'. Received Host header: '192.168.68.249:8585'
(W) 2022-06-27T10:26:53 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:172.17.0.1, username: 
(W) 2022-06-27T10:26:55 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:26:59 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:172.17.0.1, username: admin
(C) 2022-06-27T10:27:15 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP[10.11.159.222]: no router found
(C) 2022-06-27T10:27:15 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP[10.11.159.222]: no router found
(C) 2022-06-27T10:27:15 - UPnP/NAT-PMP: Port mapping failure, message: could not map port using UPnP[10.11.159.222]: no router found
(W) 2022-06-27T10:27:36 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:28:37 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:172.17.0.1, username: admin
(W) 2022-06-27T10:28:54 - WebAPI login failure. Reason: IP has been banned, IP: ::ffff:172.17.0.1, username: admin
(N) 2022-06-27T10:30:59 - qBittorrent v4.4.3.1 started
(N) 2022-06-27T10:30:59 - Using config directory: /config/qBittorrent/config
(N) 2022-06-27T10:30:59 - qBittorrent v4.4.3.1 started

 

[Remote Access]

I'm having a similar problem, followed Spaceinvaderone's video, however when I check the port I get the can't connect error. I have opened the port on my router. I am using nginx proxy manager (NPM) and cloudflare not sure if these would have an effect. not sure what else to try. I this this is because NPM and unraid.net both need to use port 443, however I could be wrong.