Salta al contenuto
0
  • Categorie
  • Recenti
  • Tag
  • Popolare
  • Mondo
  • Utenti
  • Gruppi
  • Categorie
  • Recenti
  • Tag
  • Popolare
  • Mondo
  • Utenti
  • Gruppi
Collassa

Forum Federato

Di Piero Bosio
  1. Home
  2. Categorie
  3. Senza categoria
  4. Cloudflare Setup

Cloudflare Setup

Pianificato Fissato Bloccato Spostato Senza categoria
7 Post 4 Autori 0 Visualizzazioni
  • Da Vecchi a Nuovi
  • Da Nuovi a Vecchi
  • Più Voti
Rispondi
  • Topic risposta
Effettua l'accesso per rispondere
Questa discussione è stata eliminata. Solo gli utenti con diritti di gestione possono vederla.
  • yasasundefined Questo utente è esterno a questo forum
    yasasundefined Questo utente è esterno a questo forum
    yasas
    scritto su ultima modifica di
    #1

    Hi all,

    We've been using Cloudflare for a while now and atm we are in the free tier if that helps(and have turned off acceleration).

    Since like last week we've seen a sudden hike in requests to the point where the server cannot handle it anymore.

    c565cb7d-b40f-4e4c-8c34-1ef344883e6c-image.png

    These should be AI crawlers and we're trying to limit access to them but they seem to crawl into the forum somehow.

    While we would want non-logged-in users/visitors to see the content, since no one can use the site anymore we have decided to only let in logged-in users without checks and for others, for a human check to go through.

    The following is the rule we're using to identify logged in/actual users:

    19bebf17-9484-4b47-93cf-cb9eec823add-image.png

    I was wondering if there is a better/more standardised/more accurate way to identify logged in users.

    Thanks very much!

    D1re_W0lfundefined 1 Risposta Ultima Risposta
    • yasasundefined yasas

      Hi all,

      We've been using Cloudflare for a while now and atm we are in the free tier if that helps(and have turned off acceleration).

      Since like last week we've seen a sudden hike in requests to the point where the server cannot handle it anymore.

      c565cb7d-b40f-4e4c-8c34-1ef344883e6c-image.png

      These should be AI crawlers and we're trying to limit access to them but they seem to crawl into the forum somehow.

      While we would want non-logged-in users/visitors to see the content, since no one can use the site anymore we have decided to only let in logged-in users without checks and for others, for a human check to go through.

      The following is the rule we're using to identify logged in/actual users:

      19bebf17-9484-4b47-93cf-cb9eec823add-image.png

      I was wondering if there is a better/more standardised/more accurate way to identify logged in users.

      Thanks very much!

      D1re_W0lfundefined Questo utente è esterno a questo forum
      D1re_W0lfundefined Questo utente è esterno a questo forum
      D1re_W0lf
      scritto su ultima modifica di
      #2

      Since you are on Cloudflare, do you have their Block AI bots rules on?
      They seem to help.

      julianundefined 1 Risposta Ultima Risposta
      • D1re_W0lfundefined D1re_W0lf

        Since you are on Cloudflare, do you have their Block AI bots rules on?
        They seem to help.

        julianundefined Questo utente è esterno a questo forum
        julianundefined Questo utente è esterno a questo forum
        julian
        scritto su ultima modifica di
        #3

        D1re_W0lf those rules do not seem to help, I have enabled them as well.

        yasas we have been seeing the same behaviour starting perhaps a week ago. The bursts seem to happen for maybe half a day and then disappear.

        Since we wanted the site to start working quickly, we opted for an allow-list approach. We turned on "I'm under attack" mode, which has some unfortunate side effects (namely, causing federation to stop).

        These are our rules:

        (any(http.request.headers["accept"][*] eq "application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"")) or (any(http.request.headers["accept"][*] eq "application/activity+json")) or (http.request.method eq "POST" and starts_with(http.request.uri.path, "/inbox")) or (starts_with(http.request.uri.path, "/assets")) or (starts_with(http.request.uri.path, "/.well-known"))
        

        This lets (respectively):

        1. ActivityPub fetches
        2. Same
        3. ActivityPub publishes to the NodeBB inbox
        4. Static assets
        5. Certbot and webfinger (also for AP)
        1 Risposta Ultima Risposta
        • yasasundefined Questo utente è esterno a questo forum
          yasasundefined Questo utente è esterno a questo forum
          yasas
          scritto su ultima modifica di
          #4

          D1re_W0lf Thanks for the response. Seem they do not work as Julian has confirmed.

          Hi julian
          Thanks a lot. Our current version is still NodeBB v3 so guess we may have to either make some tweaks or schedule a v4 upgrade soon. Thanks anyway Julian. Hope crawlers from search engines are still able to get through with the above setup yeah?

          julianundefined 1 Risposta Ultima Risposta
          • omegaundefined Questo utente è esterno a questo forum
            omegaundefined Questo utente è esterno a questo forum
            omega
            scritto su ultima modifica di
            #5

            yasas Yep seen the same last week, not nodeBB install, but the server behind cloudflare showed a huge uptick, not served by cache either. SO I am guessing scanning the whole site or large parts.

            IIRC the traffic was coming manly from swiss-german based servers but did not have the time to dig in. This is even with Block AI cralwers turned on.

            In the recent past it's been Asia, like mostly Singapore.

            The only way to handle this in Cloudflare is to watch and then put in place with geo-based challenge security rules in place afaict

            1 Risposta Ultima Risposta
            • omegaundefined Questo utente è esterno a questo forum
              omegaundefined Questo utente è esterno a questo forum
              omega
              scritto su ultima modifica di
              #6

              You can also use this online tool to check servers when reviewing the logs in cloudflare, this is an example of one of those serves that showed up, the radar tracks it as 86.8% bot

              https://radar.cloudflare.com/bots/as132203

              Here can be seen the 6th of September surge on on the graph and it coincides with the server traffic

              A lot of these bots are hammering wordpress exploits with targets such as /wp-content/index.php and so on, it might not be a bad idea to block by default if you have server load issues.

              1 Risposta Ultima Risposta
              • yasasundefined yasas

                D1re_W0lf Thanks for the response. Seem they do not work as Julian has confirmed.

                Hi julian
                Thanks a lot. Our current version is still NodeBB v3 so guess we may have to either make some tweaks or schedule a v4 upgrade soon. Thanks anyway Julian. Hope crawlers from search engines are still able to get through with the above setup yeah?

                julianundefined Questo utente è esterno a questo forum
                julianundefined Questo utente è esterno a questo forum
                julian
                scritto su ultima modifica di
                #7

                yasas turning on "I'm Under Attack" mode will likely block search engine crawlers as well.

                It is meant to be used as a last resort.

                1 Risposta Ultima Risposta
                Rispondi
                • Topic risposta
                Effettua l'accesso per rispondere
                • Da Vecchi a Nuovi
                • Da Nuovi a Vecchi
                • Più Voti


                • Accedi

                • Accedi o registrati per effettuare la ricerca.
                • Primo post
                  Ultimo post