I am just wondering if there have been any reports of sites running App Connect based sites causing 403 status errors?

My server runs Fail2Ban, and I have had a number of visitors have their access blocked due to numerous 403 status errors while accessing pages I have developed using App Connect and it's various components. I am wondering if this is due to something I am not using correctly, or if there are use practices I should be adhering to that improve performance and reduce these status errors.

I'm really just grasping at straws in this regard, because sometimes the site runs at blazing speeds, and other times there is significant lag (slow enough that data sets do not load, but after a page refresh they will.) Any ideas?

Hi Lee,

We don't have any reports about problems with fail2ban yet. We also haven't used it our selves. Could you check its logs for the block reason?
App Connect does nothing special that could trigger a ban. Maybe you have a server issue of some kind.

Maybe to try to disable fail2ban for a while see if your problems still persist.

Greetings,
George

The log entries that correspond with my visitors banning are all 'apache-403' issues. I have increased the number of allowable fails, and this appears to be helping with the issue.

I have a few pages that make quite a few separate calls to the database. I have the results accessible on separate tabs, even though the record sets are not particularly large, I am wondering if it would be more efficient to break apart this tabbed content to separate pages. Do you have any 'generic' recommendations for best practices in regard to number of concurrent data-sets / page that I could use as guideline?