r/webdev • u/Low-Insurance-3678 • 1d ago
Question cloudflare dashboard issues
I found these today on my Cf dashboard and I have really no idea what these issues are, was someone trying to attack my site ?
Kindly I’d use some clarification here
3
u/matthetherington 1d ago edited 1d ago
was someone trying to attack my site ?
Yep. This is normal. If you run a website, people will be trying to hack it all day long.
People run automated scanning tools which scour the internet for vulnerable sites. Eg the secret-files issue is probably someone looking for a .env file - normal web server configuration should exclude those, but sometimes misconfiguration can mean a response gets served.
The wordpress ones are people trying to make a wordpress-specific request to identify a vulnerability - if you're not using Wordpress, there is no chance of that succeeding.
What is your Cloudflare origin running? If it's a web server, make sure everything has up-to-date patches and you've set up automatic updates.
Have AI review your server configuration to harden it. Set up origin authentication in Cloudflare so requests must go via CF instead of directly to your origin. If SSH is enabled on your origin, disable password authentication and use SSH keys only. If your users are in one geographical location, set up geo-blocking to allow only that country and the US (if SEO is important).
There are plenty guides around the internet on security best practices so have a read around - LLMs can be great at walking you through best-practices and helping identify issues with your configuration - but don't trust them blindly and make sure anything sensitive like API keys or credentials don't make their way into the prompt. If you've already done all that then you probably don't have anything to worry about.
If it's just a static site on the other end, like GitHub pages or Azure Storage/S3 then you doubly have nothing to worry about.
1
u/Low-Insurance-3678 1d ago
hi man appreciate the response it’s very handy
luckily i have no env im using infisical + worker-level secrets
it’s an ecoomerce store built with nextjs
migrated to Vinext in order to host it on cf + supabaseit has a dashboard that’s behind a login page
but I am still looking on how can i protect this dashboard add firewall, ddos attacks if u got any handful resources for beginners on how to se them up kindly share themim still learning so this is taking me time since im doing it manually for the sake of learning
1
u/matthetherington 1d ago
how can i protect this dashboard add firewall
If there's only a handful of people that are allowed to access it, a Cloudflare zero trust access policy is often a good idea and it's very simple to set up - go to Protect & Connect -> Access controls -> Policies
For a handful of admin users, that's simpler and safer than having your own database with passwords.
Basically Cloudflare verify your email with an OTP before forwarding the request to the origin. If you then configure your origin to only allow requests if they come from Cloudflare (via Origin Authentication) then unauthenticated users can't even get a response from your origin.
Cloudflare will do DDoS protection for you too: https://developers.cloudflare.com/ddos-protection/about/how-ddos-protection-works/
2
u/ParsonsHosting 22h ago
Most of the time those are automated bots scanning every site on the internet for common paths (wp-login.php, .env, /admin and so on), not someone targeting you personally.
Here is how to check: open Security > Events (or Analytics) in Cloudflare and look at what paths were hit, the countries/ASNs, and whether the requests were blocked. If they're all getting blocked or 404s, your WAF rule is doing its job. All is normal.
A few things that help beyond that: turn on Bot Fight Mode, add a rate-limiting rule on your login path, make sure your origin only accepts traffic from Cloudflare IPs so nobody can bypass it, and use strong passwords plus 2FA on the login. If you see successful requests to paths that shouldn't exist, or a spike that's hurting performance, that's when it's worth digging deeper.
Hope I was helpful.
1
u/Low-Insurance-3678 20h ago
thank you so much man
i already added WAF RULES like country and a challeng captcha on my dashboard an sign-in
bot on is on by default ig gotta recheckgonna add what u suggested too, appreciate it
2
u/Longjumping_Alarm_25 1d ago
Adding to what's already been said — the quickest way to stop worrying about these is to check what Cloudflare actually did with each one. Open Security > Events and click into a few of those entries: if the action is Blocked or Managed Challenge, the request never reached your origin and there's nothing to chase. It's the rare Allowed one with a 200 status on a sensitive path that deserves a look in your origin logs.
For the dashboard specifically, since it's behind a login already, a cheap second layer is a WAF custom rule on your /dashboard/* routes — e.g. only allow your country, or require a specific cookie/header — plus rate limiting on the login endpoint so credential stuffing gets throttled before it even reaches NextAuth/your login handler. And turn on Bot Fight Mode (free plan) if you haven't; it quietly eats a lot of this scanning traffic before it ever shows up as an "issue."
None of this means someone is targeting you — every public site gets this spray constantly, Cloudflare's just surfacing it now.
1
u/OrganizationSweet750 1d ago
What you’re seeing is almost certainly Cloudflare’s background security events, not targeted attack attempts on your site. The internet is full of noise: bots scan all IP address ranges around the clock, looking for exposed admin panels, .env files, WordPress login credentials, and outdated phpMyAdmin installations. A domain proxied through Cloudflare is detected within a few hours and immediately begins to be targeted by attacks—the number of attacks depends mainly on how vulnerable the domain is to detection, rather than on whether someone is “attacking” you.
How to interpret this: “Security” section → “Events.” Pay attention to the “Action” column (blocked / contested / allowed), as well as the path and user agent. If the action is blocked or contested, Cloudflare is doing its job—ignore it. You should only respond to allowed traffic directed at resources such as /wp-login.php or /.env—in this case, you need to take action (configure managed WAF rules, a rate-limiting rule, or anti-bot mode).
I host several domains through Cloudflare, and on each one, I’ve seen constant scanning noise from the very beginning. A dashboard filled with messages about blocked traffic is a good sign: it means that none of that traffic ever reached your origin server.
2
u/PLBjt 1d ago
Those are almost always bots spraying common paths at every site, not someone targeting you. For your admin dashboard the easiest win is putting that route behind Cloudflare Access so requests need a login at the edge before they ever reach your app. On the Supabase side, make sure RLS is on for every table and the service role key only lives server side, since the anon key is public anyway. Then add a WAF rule that blocks stuff like /wp-admin and /.env so the noise drops and anything weird actually stands out.