Again the same problem. Thank you.
Saroj Kasaju On Wed, May 6, 2026 at 9:29 PM Saroj Kasaju <[email protected]> wrote: > Yes Mr. Garg. > > Thank you. > > Saroj Kasaju > > > On Wed, May 6, 2026 at 8:44 PM J.M. Garg <[email protected]> wrote: > >> I just checked. It is opening. >> >> With regards, >> J.M.Garg, >> https://efloraofindia.com/ >> >> On Wed, 6 May, 2026, 2:24 pm Nancy Seby, <[email protected]> wrote: >> >>> Dear Mr. Kasaju and Mr. Garg, >>> >>> Here's what Claude (AI) says happened. The error is from a proxy server >>> that is placed before our website that failed. Should be a temporary >>> problem. Can you please check with another device, another browser, or >>> incognito mode? Eitherways, it is good to report the problem to Lady Bird >>> Web Solutions, which Mr. Garg has done already. >>> >>> That's a *SiteLock TrueShield* error page. SiteLock is a security >>> service (a Web Application Firewall + reverse proxy) that sits in front of >>> flowersofindia.net. When you visit the site, your request actually goes >>> to a SiteLock proxy server first, which then fetches the page from the real >>> origin server and passes it back to you. >>> *What "Error 20" means:* The SiteLock proxy tried to open a TCP >>> connection to the origin web server and didn't get a response in time — so >>> it gave up and showed this page to the visitor. It's specifically a >>> connection-level failure between SiteLock and the origin, not between the >>> visitor and SiteLock. >>> *Why it works for you but not for them:* >>> >>> - SiteLock has many proxy nodes around the world. Your visitor was >>> routed through proxy 107.154.231.251; you're almost certainly being >>> routed through a different one. If that one specific proxy couldn't reach >>> the origin (network blip, route flap, brief origin overload), only people >>> hitting that node would see the error. >>> - The IP 27.34.66.197 is in an APNIC-allocated range, so the visitor >>> is likely somewhere in Asia. Geographic routing means they hit a >>> different >>> edge node than you, and possibly a different path to the origin. >>> - It's almost always *intermittent*. TCP timeouts are usually >>> transient — a few seconds or minutes later, the same person often gets >>> through fine. >>> - Less commonly, SiteLock's WAF may have flagged that visitor's IP >>> for some reason (rate limiting, reputation, etc.), though when that >>> happens >>> the error is usually phrased as "blocked" rather than a TCP timeout. >>> >>> *What to do:* >>> >>> 1. Try again in a few minutes — it usually resolves on its own. >>> 2. Try a different network (mobile data instead of Wi-Fi, or vice >>> versa) to get routed through a different proxy node. >>> 3. Clear browser cache or try an incognito window. >>> 4. If it persists for hours specifically for them, their ISP's IP >>> range may be having trouble reaching that particular SiteLock node — a >>> VPN >>> would confirm/work around it. >>> >>> >>> Thank you and warm regards >>> Nancy >>> >>> ------------------------------ >>> *From:* Saroj Kasaju <[email protected]> >>> *Sent:* Wednesday, May 06, 2026 13:43 >>> *To:* J.M. Garg <[email protected]> >>> *Cc:* Nancy Seby <[email protected]>; efloraindia < >>> [email protected]> >>> *Subject:* Re: Site >>> >>> NO yet functioning . >>> >>> Thank you. >>> >>> Saroj Kasaju >>> >>> >>> On Wed, May 6, 2026 at 1:36 PM J.M. Garg <[email protected]> wrote: >>> >>> Hi, Saroj ji, >>> It seems to be working now. >>> Still I have lodged a complaint before this. >>> >>> On Wed, 6 May 2026 at 12:41, Saroj Kasaju <[email protected]> wrote: >>> >>> Hi Nancy, >>> >>> Can you please look into this matter ? >>> It just started. >>> >>> Thank you. >>> >>> Saroj Kasaju >>> >>> >>> >>> -- >>> With regards, >>> J.M.Garg, >>> https://efloraofindia.com/ >>> >>> -- You received this message because you are subscribed to the Google Groups "eFloraofIndia" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion, visit https://groups.google.com/d/msgid/indiantreepix/CAEf%3DytQ6rneqi4VE_MM44FDXxoL24mQ0oynKPT5-8T6yvt5qRA%40mail.gmail.com.
