Hey all, been reading through the docs regarding the Bot Fight Mode. It's currently blocking all my Mailgun email webhooks. I submitted the details as a 'verified bot' but for some reason I don't see any action being taken on that any time soon, pretty sure it's just feedback that's gone into a huge backlog....
I'm currently on the free plan, and the docs say you 'get more control' over the bot fight mode. -- I just want to confirm, if anybody knows or has experience, will this actually allow me to skip the bot fight mode against the variables I input?
I already set up a WAF rule AND a Configuration Rule to attempt to skip it. But yea.. the docs DO say that you can't modify, just turn it off... Turning it off entirely is just not an option, but I'm missing out on crucial data that I need to react to.. but hesitant to upgrade right now just in case it doesn't allow me to simply just skip the 'Managed Challenge' (not even a block, but the traffic still doesn't reach origin).
Just wondering, would it be a better idea to place the rule to skip the bot detection in the 'Custom Rules' section, or 'Add exception' in the 'Managed Rules' section??
Hello all, I am having an issue getting a cloudflare tunnel working for my Proxmox management console. I have cloudflared running on a raspberry pi on my network and I just did a fresh install of proxmox on a mac pro. I am able to hit the management console with the socket: 10.10.10.202:8006 in a browser, and my raspberry pi is able to ping that host. Tunnel is setup to route pve.n3rd-lab.net to 10.10.10.202:8006 over HTTPS. I have disabled TLS Verification but am getting a 502. Let me know if this is not the place to ask about this. Thanks!
I was having some trouble with the cloudflared tunnels the other day, I had to fiddle with the Virtual Network settings from Settings > Warp Client > 'Manage' button at the bottom of the page, to set up a virtual network
And just triple check that cloudflared is running and the service is installed properly with the token given in the dashboard (if you're configuring remotely that is)
I was having issues getting things to work because I was attempting to use Warp client as well, but pure cloudflared was so much simpler, and actually worked after I disabled everything Warp related
Token does look good and cloudflared is definitely running. I just added a private network. I didn't have one previously. Have not messed with WARP at all. I previously tested tunneling w/ my OPNsense management page without issue so I didn't want to deal with anything else. There is a warning on the tunnels page I missed that there are DNS update issues rn which is probably the culprit
I will give the cloudflare team a while to figure their stuff out. If I'm still having issues after the status page gives me the OK, I will reach back out. Thanks Druppy for the quick response!
I've got a meshnet set up with my work machine, and my mobile. So now can ssh into my macbooks terminal (or even vnc if I'm feeling exotic) and from there hope straight through another ssh shell proxied through cloudflared into the origin server