Issue: Member unable to post after XF/VW update

Issue Tools
- View Changes

March 11, 2018 10:15 AM

Alfa1

Distinguished Member

Member unable to post after XF/VW update

I updated to VW 4.0.21 two days ago and XF 1.5.17 yesterday.
At 1:12 AM the follow cron runs once a week: vw_cron_watch2
This may be a coincidence but at that exact time there occurred found a number of errors. Please see the error log.

My members were no longer no longer able to post anywhere on the site until I turned VW off.
Please see my profile on my site where a member posted screenshots of network issues: /members/alfa.1/#profile-post-84295
I still dont understand why but there seems to be some issue with VW elements loading from CDN and therefore the editor doesn't load.

I first disabled the CDN from XF and VW , but that didnt help.
I then tried to disable the wiki but it didn't work.
Then I disabled the XF VW plugin. Im seeing some new posts now, so that seems to have alleviated the issue.

Issue Details

Issue Number 5376

Issue Type Bug

Project VaultWiki 4.x Series

Category Forum Posts / Non-Wiki Content

Status Cannot Reproduce

Priority 3 - Loss of Functionality

Affected Version 4.0.21

Fixed Version (none)

Milestone (none)

Software DependencyXenForo 1.x

License TypePaid

Users able to reproduce bug 0

Users unable to reproduce bug 0

Attachments 0

Assigned Users (none)

Tags (none)

March 11, 2018 2:57 PM

Alfa1

Distinguished Member

I turned CDN back on for the forum, but left VW off. My members are still able to post.

Reply
March 12, 2018 9:42 AM
pegasus

VaultWiki Team
For the issues at 1:12 AM, this looks like you were uploading files at 1:12 AM and caused those errors because the process took those files offline for a second.

As for your other issue...

With the CDN on, even while VaultWiki is disabled, large numbers of resources do not work for me (most images). Example:
cdn/styles/default/xenforo/gradients/form-button-white-25px.png
Returns "500 Origin Error: The origin server is not reachable or returns an error."

If your CDN was active while you were upgrading XenForo, this could cause the issue. It may have tried to refresh from the origin while the files were locked for uploading or while they were partially written. After all files have been completely uploaded, you should try changing your CDN expiry URL parameters. Right now it looks like the datestamp used for many images is from July 2017.

I was not able to reproduce the issue of not being able to post on your site currently, nor after enabling VaultWiki. However, I have re-disabled VaultWiki so you did not wonder how it magically enabled itself.

I believe that your issue was most likely caused by your CDN attempting to pull Javascript resources from the origin while you were still uploading those resources (and then caching that state in the CDN). You tend to have issues with users accessing resources while you are uploading them. Since you use a CDN and your site is high-traffic (so you cannot guarantee that users will not access the site while you are upgrading), you should make use of XenForo's cache-buster config.php option (which you currently do not).

In library/config.php:

Code:

$config['jsVersion'] = 'random_string';

After every completed upgrade of XenForo (or any time you modify/upload Javascript), you should change this to a different random_string of your choosing. This will force the CDN to re-pull your Javascript.
Reply

+ Reply

All times are GMT -4. The time now is 3:27 PM.

This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.

Learn more… Accept Remind me later

Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

Issue: Member unable to post after XF/VW update

Issue Tools