Python Forum
post error from cloudflare
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
post error from cloudflare
#11
hope you didn't lose your post.
Tradition is peer pressure from dead people

What do you call someone who speaks three languages? Trilingual. Two languages? Bilingual. One language? American.
Reply
#12
(Jun-23-2022, 08:14 PM)Larz60+ Wrote: I just happened to get one today
As mention before this is most likely a local problem with your network.
I spend some time on this forum and have never got a CloudFlare error.
Have asked before if other regular here get CloudFlare error and answer has been no,
so most like this is not central CloudFlare problem,more that local network can cause this problem.

There is of course not an option to turn of CloudFlare off,we route all network traffic tough it.
We have not one instant of DDoS attack after used CloudFlare.
Before forum was slow down for long period in DDoS attack,and we had to go in manually to stop the attack.
CloudFlare also provide Firewall and optimization that we use.
Reply
#13
The only time I see it is if I attempt to respond to a thread using the following sequence.
  1. Forums->Unread Posts
  2. Click on one of the Unread posts
  3. Quick Reply
  4. Reply must have a link to some other forum area like Posts to NOT make at all. I chose this at random, can't say it has any association with the help URL
  5. Click on Preview Post (always occurs during preview), and only in quick reply.
  6. entire text in Quick reply is erased.
If, instead, I use 'New Reply' button, there is no error even with same exact text as attempted in quick reply.
If it's my network, then this is the only site, and/or forum where it occurs. So, even though it's remotely possible, it's unlikely.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  error while previewing locked post Kebap 4 6,807 Sep-17-2016, 05:52 AM
Last Post: metulburr

Forum Jump:

User Panel Messages

Announcements
Announcement #1 8/1/2020
Announcement #2 8/2/2020
Announcement #3 8/6/2020