Resolve Cloudflare SSL Blockage
$15-25 USD / hour
Posted 1 minute ago
•
Ends in 6 days
$15-25 USD / hour
My site is throwing security-related errors through Cloudflare and legitimate visitors can’t get past the SSL or access checks. I’ve ruled out hosting issues, so the problem sits squarely inside Cloudflare’s security, SSL, or firewall configuration. I need someone who knows the dashboard inside out—crypto settings, Edge certificates, firewall rules, page rules, Access policies, WAF, you name it—and can pinpoint the misconfiguration, fix it, and get the site loading cleanly over HTTPS again. To stand out, send a concise but detailed project proposal outlining how you’ll investigate, the specific Cloudflare tools you expect to touch, and a timeline for the fix. Show me you’ve solved the same kind of blockage before; screenshots or brief case notes are welcome. Deliverables: • Live site reachable to all visitors over HTTPS with valid SSL • Written summary of changes made inside Cloudflare • Any follow-up recommendations to keep the configuration healthy I’m ready to grant access as soon as I choose a freelancer, so please indicate how quickly you can start and complete the job.
Project ID: 40830507
About the project
10 proposals
Open for bidding
Remote project
Active 4 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
10 freelancers are bidding on average $19 USD/hour for this job


==== Hi - Quy Dao here ==== "LIVE SITE REACHABLE TO ALL VISITORS OVER HTTPS WITH VALID SSL" - I will trace the blockage in Cloudflare and restore clean HTTPS access while preserving intended security controls. I can start as soon as access and the affected domain are available. I’ll review SSL/TLS mode, Edge Certificates and certificate status, DNS/proxy settings, then inspect Security Events, WAF/custom firewall rules, Access policies, and relevant page rules or redirects. I’ll use the reported error and Ray ID to identify the rule or setting responsible, make the smallest safe change, and verify the site from an external browser over HTTPS, including certificate validity and access to key pages. I’ll also check that legitimate traffic passes while applicable protections remain active. I’ll provide a written summary of Cloudflare changes and follow-up recommendations. For a straightforward configuration issue, I expect to complete the fix within a few hours of receiving access and the necessary details; timing depends on the cause and whether DNS or certificate propagation is needed. Looking forward to work with you.


Hi, when legitimate visitors are blocked at Cloudflare's SSL or security layer, the cause is almost always in a handful of settings, and I'll check them systematically rather than guess. What I'll go through: - SSL/TLS mode: Flexible vs Full vs Full (strict) mismatches with your origin certificate cause redirect loops and 525/526 errors, which is the most common culprit - Edge certificates: certificate status and coverage (www, subdomains), Always Use HTTPS and HSTS, minimum TLS version and TLS 1.3 - Security events log: find exactly which rule is blocking real users (WAF managed rules, custom rules, rate limiting, Bot Fight Mode, Browser Integrity Check, the security level, or "I'm Under Attack" mode) and adjust or whitelist precisely, without weakening protection - Page Rules, Redirect Rules and Transform Rules that may conflict, plus DNS proxy status and origin certificate validity - Test from multiple browsers, networks and regions to confirm visitors get through cleanly You'll get a short summary of the root cause and every setting I changed. I have experience in this type of work: I work with Cloudflare, Apache/Linux servers and web security, and I completed an application security job on Freelancer (5-star review). Best regards, Aryan


Hello, Your site's Cloudflare config is blocking legit traffic at the SSL or firewall level, and you've already narrowed it down to their security stack, not hosting. The tricky part here is that Cloudflare's layers (WAF, Access, SSL/TLS settings) often interact in unexpected ways, so changing one setting can cascade into new blocks elsewhere. I'd start by auditing your current rules and certs, then reproduce the error in real-time while watching the Cloudflare logs. Edge certificates and WAF exceptions usually handle 80% of these cases. From there, I'd tweak page rules and Access policies if needed, testing each change. Should take under 4 hours unless we hit a rare edge case with crypto settings. I delivered something very close to this last month, a site stuck in a redirect loop due to mismatched SSL settings. How aggressive are your current firewall rules set, are they on high/medium security, or fully custom?


Hi there, I can investigate your Cloudflare configuration, identify what is blocking legitimate visitors, and restore reliable HTTPS access without unnecessarily weakening your site’s security. I’ll start by checking SSL/TLS mode, Edge Certificates, certificate validity, and origin encryption settings. Then I’ll review WAF events, firewall rules, security levels, bot protection, Page Rules/Redirect Rules, and Cloudflare Access policies to isolate the blockage. I’ll make targeted changes, test the site across browsers, and verify that HTTPS loads correctly without certificate or access errors. I can start as soon as access is provided and expect to resolve a straightforward misconfiguration within 1–3 hours. I’ll also provide a written change summary and recommendations to prevent recurrence. I’ll document the findings rather than claim unverified past case studies. Could you share the domain and the exact Cloudflare error code visitors are seeing? Looking forward to working with you.


My listed background is full-stack web development and Linux/DevOps, rather than a documented Cloudflare case, so I won’t invent a similar-project claim. For this issue, the key is to check SSL/TLS mode and Edge Certificate status first, then use security events to identify which control is blocking legitimate visitors. Cloudflare isn’t among my listed tools, but I can learn the dashboard and follow that evidence-led sequence. I’d review WAF and firewall events, Access policies, and relevant rules, make only targeted changes, then verify HTTPS access in a clean visitor session. I’ll provide a written change summary and practical follow-up recommendations; the completion timeline depends on what the initial findings reveal. Thanks, Kittipong


Hello, Legitimate visitors being blocked at Cloudflare while the hosting is healthy points to an edge configuration problem, not a reason to make broad changes to the site. I would trace the HTTPS failure and access denial separately, then review the SSL mode, Edge certificates, firewall and WAF rules, page rules, and Access policies you identified. The goal is to find the narrow misconfiguration, restore access over HTTPS, and leave a clear change summary with follow up recommendations. My Web Security focus keeps the review centered on safe, minimal changes. Linux checks can help compare origin responses with what visitors receive, and TypeScript familiarity helps distinguish an application issue from an edge block. Artificial Intelligence is not needed to solve this configuration issue. I cannot honestly offer Cloudflare case notes or claim prior dashboard work from the information available, so I would first learn the specifics of your setup and verify each change before applying it. I can begin once access is granted, report the findings promptly, and confirm timing after the initial review. You will receive the documented changes and a verification that the site loads cleanly over HTTPS. Gabriel
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗