Bug VBSEO Imported:- Now Error : /website/www/index.html (None could be negotiated).

Status
Not open for further replies.
neounix

neounix

Customer
Hi Again,

Decided to testi importing old VBSEO configuration.

All was OK after we set the Navbit rewrite function off.

However, we noticed that we cannot access the home page, and get this error:

Code: 
[Thu Dec 12 16:37:45 2013] [error] [client <ip addr>] Negotiation: discovered file(s) matching request: /website/www/index.html (None could be negotiated).

Did we miss a setting when we imported the old VBSEO config?
 
Yes, the issue began when we installed DBSEO.

I just turned DBSEO off, and it works fine.

So, the issue is with DBSEO, not our server config, because it works find when we turn off DBSEO.
 
Please don't be so quick to list something as "NOT A BUG" .. Thanks. (I can do Google searches too, LOL). :) :)

When we turn on DBSEO, it is broken.

When we turn off DBSEO, it works as it did before.

Hence, the logical conclusion is that DBSEO is causing the problem, not a configuration that has been working for over a year.
 
No. It does not work no matter what we do. I tried those with DBSEO on.. just to check. Nothing works with DBSEO on.

The only way it works is to disable DBSEO.

The configuration has worked perfectly for over a year. Now that DBSEO is installed, it is broken.
 
Perhaps not related, but we are not seeing this warning as well:

[Thu Dec 12 17:37:12 2013] [error] [client 58.137.213.180] Negotiation: discovered file(s) matching request: /website/www/index.html (None could be negotiated).
[Thu Dec 12 17:37:12 2013] [error] [client 58.137.213.180] PHP Warning: preg_match(): Unknown modifier 'a' in /website/www/dbtech/dbseo/includes/class_core.php on line 624
[Thu Dec 12 17:37:12 2013] [error] [client 58.137.213.180] PHP Warning: preg_match(): Unknown modifier 'a' in /website/www/dbtech/dbseo/includes/class_core.php on line 625
[Thu Dec 12 17:37:12 2013] [error] [client 58.137.213.180] PHP Warning: preg_match(): Unknown modifier 'a' in /website/www/dbtech/dbseo/includes/class_core.php on line 626
Click to expand...
 
I doubt that would make a difference.

I'm not seeing a .htaccess file in your root dir, only an empty ".htacces" file.
I'd like to try possibly tweaking the rewrite rules, can you please make the .htaccess file with the rewrite rules for DBSEO accessible to my account?
 
The problem with the PHP errors were from a string imported into the "Excluded Pages" setting that was created when we imported VBSEO. I removed that and the WARNING went away.

Regarding .htaccess, we do all this directly in the configuration file for the site. I don't think you can "tweek that" to make it work; because I already tried it... nothing works except turning off DBSEO.

It works fine if DBSEO is turned off.
 
I'm at a loss here... Can you not restore the rewrite rules to the .htaccess file, at least while I'm looking into this issue?

Can you also please restore the string you deleted from the Excluded Pages?

Also, for the future, can you please not undo the circumstances that's causing an issue if you're reporting it? I really need to be able to see it in action if I'm to do anything about it.

Thank you.
 
OK. let's forget about the imported string problem the PHP WARNING that is currently not the issue;and focus on the issue at hand.

SInce the problem with the home page not working happens when we turn on DBSEO, and it does not happen when it turn off DBSEO, it seems to me the logical place to debug this is within your DBSEO code base and not tweeking htaccess rules that have been working perfectly for "years' and have not been modified except to add the few lines for DBSEO when installed.

It's 7 AM here, so I'm tired. I do kindly suggest that you do have enough tools to debug this withing the dbseo code base, since that is where the issue resides.

I'm off the net for at least 8 hours, sleeping... It'a all yours!
 
If the "Force Index" setting was turned off, the resulting display would conflict with mod_negotiate and MultiViews. I've added a workaround for that, as well as a potential workaround for the excluded pages issue.
 
I just woke up and saw it was working. Great job and thanks.

OBTW, before I tried both settings (on and off) of the Force Forum Directory Index setting, and neither on nor off worked before; but i see that both settings works now; great news and thanks!

I think we will move to the main server this weekend, if you agree and are comfortable with that.

What do you think?
 
As long as you're okay with the fact that I may need write access to the files again to debug any further issues - like I said in the other topic this mod is a kind of mod that's not exactly straightforward :p

Not unlike, say, vBShout where if it's not loading I open the error console and notice the AJAX request 404's on vbshout.php so I can say "drag and drop the contents of the upload folder to your forum folder".

Of course, if the issue can be reproduced on your staging server I'm fine with that too :) I certainly don't intend to demand write access to the live server :p
 
OK. Thanks.

I'll go back to sleep and run more tests tomorrow. Basically, I need to look at Google Webmaster tools and check a number of links to our site and make sure the old VBSEO links on other sites are working on the test server.

Then, I'll run some more tests on the backup/test server and if no errors, I'll download the latest version from your client area and install on the main server.

The only thing missing is the export settings functionality to export all the DBSEO settings to a flat file and then import that file to the production server; but I don't think you will have that done before the weekend; so we can either cut-and-paste from the backup / staging server; or I can import the VBSEO settings from the main server and then tweek to match the working configuration on the test server.

We are seeing quite an SEO hit since removing VBSEO and 301'ing all the old VBSEO URLS back to the original URLs; and our PR just dropped from 5 to 4; so I am really looking forward to getting DBSEO up and running so I can stop 301'ing all the old VBSEO URLS.

Thank you again, for the great support and also for quickly building DBSEO to replace VBSEO; and for your continued support for all of us.

Much appreciated.
 
OBTW, I assume all the hotfixes you made on our site are also included in the current release in the client area; so best we download from the client area and install on the production server? Or should we move the files from the test server to the production server?

Also, FYI... the main site is working, but we still see the error in the log file:

[Thu Dec 12 20:38:43 2013] [error] [client 58.137.213.43] Negotiation: discovered file(s) matching request: /website/www/index.html (None could be negotiated).
[Thu Dec 12 20:39:32 2013] [error] [client 58.137.213.43] Negotiation: discovered file(s) matching request: /website/www/index.html (None could be negotiated).
Click to expand...
 
Last edited:
Instead of deleting the "MultiViews" entry in our Apache2 config file... I put the minus sign in front:

Code: 
-MultiViews

... and not the error is *finally* gone.

Thanks for your patience on this one. I tried everything yesterday and could not get it to work until today, when I decided to add the "-" in front of MultiViews, and it seems OK now.

Thanks.
 
That was why I wanted access to a .htaccess file on your site. vBulletin includes a commented out Options -MultiViews entry with its .htaccess file as well, as it resolves some issues with the rewrite from content/ to content.php allegedly.

Glad to hear you got it working :)
 
Thanks.

FYI, we do not use .htaccess files (for security reasons); and we do not permit overrides (for security reasons).

All of our apache2 configuration is done outside of the web server document root filesystem (for security reasons).

The good news it is now working.

The only unresolved issue we have at the moment in the thread on stop words, when the setting is set to zero. the stop words are not working.
 
Status
Not open for further replies.

Legacy DragonByte SEO

vBulletin 3.8.x vBulletin 4.x.x
Seller
DragonByte Technologies
Release date
Last update
Total downloads
7,190
Customer rating
5.00 star(s) 1 ratings
Back
Top