XF 2.3 ost being stopped because of required refreshing issue Confirm Form Resubmission

[oldandlively]

Please migrate this issue to the appropriate subforum if you please since I can't seem to post in other other subforums.

Issue. We just recovered our forum from a disaster, installed v2.3.4, and discovered an issue. We searched all over the place, but could not find the appropriate answer specifically. The suggestions to dig inside the *.php files are not resolving the problem.

Issue:
When the user logged in, browsing around, every 5 to 10 minutes, the browser required the user to "refresh" the page. The page then connects to CloudFlare, reconfirm, and resume on the user's merry way.

However, when the users start their long posting editing, the system will prevent the post from submission. The post can only be submitted when the user refresh the page, which possibly lose quite a bit of their posting content.

On the mobile devices, the dialogue box error tends to pop up as "Confirm Form Resubmission". For browsers on the PCs, it simply pops up as "Oops! We ran into some problems."

This may have been answered before, but I can't seem to search with specific keywords. Any help is greatly appreciated.

 

[Ozzy47]

For browsers on the PCs, it simply pops up as "Oops! We ran into some problems."

When you see that message, check the browser console for errors.

Are there any errors showing in the ACP?

 

[oldandlively]

When you see that message, check the browser console for errors.

Are there any errors showing in the ACP?

Unfortunately, there's no errors showing up in the browser's console. That's where things bug me.

There's no error showing up in ACP either. Just the simple dialogue message. Here's another update. The members are pointing out that when they click the box "Remain logged in", the forum refreshes between 10 to 15 minutes and forces the user to log back in again.

 

[oldandlively]

Resolved one issue after probing the ACP long enough, which is the "Online status timeout". This is a hidden field. You have to use the search under ACP to search for "timeout". It's not displayed by strolling through the ACP Options. I'm going to test to see if this works.

 

[Joe Blow]

Some of my users are reporting a similar issue. This is how one of them describes it::

I open the forum and am logged in ok, open a few tabs based on latest posts, alerts etc
By the time lets say 10 or 15 minutes i read some of the open tabs, i need to force a refresh to be able to like a post or try to post a reply.my logging to the pages has " expired" and liking or reply posting fails

Apparently this has just started happening recently.

 

[oldandlively]

Some of my users are reporting a similar issue. This is how one of them describes it::

It's been reporting over and over again in the older versions as well. We deployed so many methods and we couldn't determine which method worked, or a combination of methods.

I went into CloudFlare and configured the SSL/TLS from FULL to FULL (Strict). This hasn't resolve anything yet. Every 15 minutes, same issue occurs.

I also changed the Time To Live from the default 5 minutes to 60 minutes. Still not working.

I played with the Timeout option from the hidden item that revealed only during search, it doesn't work. I switched the development mode on for XenForo, edit all the way up to 1440 minutes (24 hours), still not working.

Apparently this has just started happening recently.

For 2.3, it's just started. But for older versions, there were periods of repetitive issues since v1.x. Still, no solution.

 

[oldandlively]

For those who couldn't figure things out, here's something I've played around with and it happens to work for the time being:

CloudFlare settings:

Log in, click on your DNS. This loads up your other settings, such as SSL/TLS and Rules.
Open SSL/TLS » Configure (button on the right hand side) » Full (Strict) » save it.

Open up Rules » Add Rules:
Caching » Browser Cache TTL » 2 hours or even 5 hours. 2 hours should be the limit.
Caching » Crawler Hints » turn on and Caching. Some of you may not want it on as it can effect your site's contents. Read upon Indexing vs blocking bots for crawlers.
Caching » Always Online » on
Caching » select Custom filter expression option
Caching » select Eligible for cache
Caching » select Override origin and use this TTL & Input time-to-live (TTL) (required) set for 1 hour
Caching » select Cache by device type on
Caching » Do not serve stale content while updating
Caching » Tiered Cache » Smart Tiered Caching Topology

So far, things doesn't get refreshed every 5 to 10 minutes. I'm good to go for an hour. My bandwidth is optimized without heavy leaching. This is my scenario anyway.