Question dbseo URLs not forwarding

[diecastfast]

vBSEO URLs not forwarding.

Examples: https://www.google.com/search?q=site:sportshoopla.com

Mod not enabled in General Settings. Very frustrating waste of time.

vBSEO import instructions state.

9. Chmod the ./store_sitemap folder to 077

Where is this file?

Also, can you tell me if MaxCDN settings in vBSEO imported?

I replaced vBSEO because it kept crashing the server, as it did tonight. However, I'm getting the same problem with your product so it must be a server issue. Can you take a look at this screenshot from Process Manager and give me any insight?

 

[Fillip H.]

vBSEO URLs not forwarding.

Examples: https://www.google.com/search?q=site:sportshoopla.com

Mod not enabled in General Settings. Very frustrating waste of time.

Sorry, I'm a little bit confused. By default, the modification comes enabled in the General Settings. Are you saying the issue got resolved by you re-enabling the modification?

I am seeing that old URLs are not working as intended from that Google link, which indicates the URL formats may have changed. Have you ran the vBSEO Import?

vBSEO import instructions state.

9. Chmod the ./store_sitemap folder to 077

Where is this file?

This is a folder, not a file. You can see a reference to it in the Sitemap Settings in the DBSEO CP. If it does not exist, you should create it

Also, can you tell me if MaxCDN settings in vBSEO imported?

DBSEO has no CDN functionality of any description.

I replaced vBSEO because it kept crashing the server, as it did tonight. However, I'm getting the same problem with your product so it must be a server issue. Can you take a look at this screenshot from Process Manager and give me any insight?

The problem is that your server is not powerful enough to handle the traffic you're experiencing, it's unfortunately that simple.

Process management scripts will mistakenly claim that vBSEO and DBSEO are the sole cause of traffic on your server, because of the way that vBSEO & DBSEO routes the requests.

When you request domain.com/some-seo-url/some-thread.html your server obviously does not have a subdirectory called "some-seo-url", and no file called "some-thread.html" in that directory, so the .htaccess file then tells the server to route that request through /dbseo.php. DBSEO will then load and run vBulletin once it's figured out where you actually meant to go.

What this means is that 100% of vBulletin's resource usage will be attributed to vBSEO or DBSEO, when this is not the case.

Hope this helps

 

[diecastfast]

I'm really puzzled. Last night when I enabled the mod, everything worked after importing. Now this morning the mod is disabled again and I can't seem to get it working.

 

[diecastfast]

Confirming that the mod keeps disabling.

 

[Fillip H.]

There is absolutely no code in DBSEO that disables the modification automatically in any scenario. Are you sure your host doesn't have some form of monitoring script that does this?

Are you running some form of cache like XCache on your server?

I'm really at a loss for what could be causing this, as in my 10 years of experience writing modifications for vBulletin I have never heard of this happening.