vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   Threads won't show (https://vborg.vbsupport.ru/showthread.php?t=325825)

BoostedK20 11-30-2017 01:38 PM

Threads won't show
 
I can't view any threads or posts on my forum (boostedk20.com). Links re-direct to a 500 error. While talking with my host, they entered the 500 error URL into some website and told me there is a missing vbulletin file. If I remember correctly, the problematic file was "vB_Cache_Db". How can I confirm that this is the affected file or how can I find out what is causing my issue?

Thank you

TheLastSuperman 11-30-2017 10:40 PM

Try: AdminCP > Maintenance > Clear System Cache

Have you made any recent changes to .htaccess?

BoostedK20 12-02-2017 04:12 PM

Quote:

Originally Posted by TheLastSuperman (Post 2591354)
Try: AdminCP > Maintenance > Clear System Cache

Have you made any recent changes to .htaccess?

Clear System Cache brings up a blank page in admincp, nothing happens. Is this because a file is missing?

I have not messed with the htaccess file, but I did recently notice i have three of them - none of which are active (as they are labeled 1.htaccess 2.htaccess etc.).

Seven Skins 12-02-2017 10:26 PM

If you haven't made changes to the core vbulletin files then you can re-upload a fresh copy of vbulletin files with the same exact version on your server. This will take care of the any missing files.

BoostedK20 12-06-2017 09:30 PM

Quote:

Originally Posted by Seven Skins (Post 2591388)
If you haven't made changes to the core vbulletin files then you can re-upload a fresh copy of vbulletin files with the same exact version on your server. This will take care of the any missing files.

Is there a way to confirm that I haven't changed any core vbulletin files? And are you aware of a website which enables a user to paste the URL and it will tell what file(s) are problematic?

Otherwise, it seems simple enough. Could you explain how to do so?

Seven Skins 12-07-2017 10:42 AM

GOTO

AdminCP > Maintenance > Diagnostics > Suspect File Versions ...

BoostedK20 12-07-2017 04:46 PM

Quote:

Originally Posted by Seven Skins (Post 2591474)
GOTO

AdminCP > Maintenance > Diagnostics > Suspect File Versions ...

Thank you. There were a bunch of files not recognized as part of vBulletin. These were mainly product plugins. Do I re-download the files from vbulletin and re-upload? What should I look out for?

Seven Skins 12-07-2017 08:42 PM

You can try that. You dont have to upload image files just in case you are using custom images.

BTW have you tried disabling the plugins to see if that fixes the error?

PS. Make backup 1st.

BoostedK20 12-07-2017 08:48 PM

Quote:

Originally Posted by Seven Skins (Post 2591487)
You can try that. You dont have to upload image files just in case you are using custom images.

BTW have you tried disabling the plugins to see if that fixes the error?

PS. Make backup 1st.

I haven't tried disabling plugins to see. Didn't think of that. Should I disable one-by-one and see if one changes that?

Do you suggest any other things I should try first before re-uploading files? The last post was 4 weeks ago. So, something happened between then and one week ago to cause this. I've added an SSL, that is the only change I've made to the vbulletin site since or before that last post. Is there a log I can check? Thank you for helping me so far

Seven Skins 12-08-2017 09:50 AM

Disable all plugins are see the error goes away. If it does then enable them one at a time OR disable them one at a time and which modifications is causing this problem.

BoostedK20 12-10-2017 09:36 PM

Quote:

Originally Posted by Seven Skins (Post 2591496)
Disable all plugins are see the error goes away. If it does then enable them one at a time OR disable them one at a time and which modifications is causing this problem.

I disabled one at a time. The 500 error for threads persisted with plugins disabled. I'm wondering how my host, at the time, was able to tell me there was a file error? Did they run a 'broken' url that resulted in the 500 error and saw what file was erroneous when called upon? Something similar? If so, how could I go about that and address that file issue? I don't know what caused it unfortunately since it was a month ago so I can't really narrow anything down.

For reference, here is a link. The URL seems off.. http://www.boostedk20.com/forums/sho...2800#post32800

Mark.B 12-14-2017 10:19 PM

What is your vBulletin version, and what is your php version?

TheLastSuperman 12-17-2017 01:55 AM

^ Also has your host recently made any server-side changes or more importantly changes to mod_security or similar?

Edit: Or did you recently update the forum? This could be related to file permission/ownership if for example the files were uploaded via ftp under a different user account - that all depends on how the server is setup.

Mattwhf 12-17-2017 01:56 AM

For this error, I think it caused by your htaccess file or your hosting.
Checking on that.

Dave 12-17-2017 02:03 AM

If you're getting internal server errors (500 status code), check the error logs of Apache or PHP and that should guide you in the right direction of what is going wrong.

BoostedK20 12-18-2017 07:24 PM

Quote:

Originally Posted by Mark.B (Post 2591602)
What is your vBulletin version, and what is your php version?

vBulletin: 4.2.3 patch level 2; Current PHP version: 5.4

Quote:

Originally Posted by TheLastSuperman (Post 2591658)
^ Also has your host recently made any server-side changes or more importantly changes to mod_security or similar?

Edit: Or did you recently update the forum? This could be related to file permission/ownership if for example the files were uploaded via ftp under a different user account - that all depends on how the server is setup.

I added SSL about 5-6 weeks ago.
Quote:

Originally Posted by Mattwhf (Post 2591659)
For this error, I think it caused by your htaccess file or your hosting.
Checking on that.

It may be, but they haven't been touched in a long time. Way before this issue occurred. I'd like to address that aspect, but I'm unsure it's causing this.
Quote:

Originally Posted by Dave (Post 2591661)
If you're getting internal server errors (500 status code), check the error logs of Apache or PHP and that should guide you in the right direction of what is going wrong.

Do I check the error logs through vB or through my host/cpanel? I haven't checked logs before.

Dave 12-18-2017 07:31 PM

In your case, you can only check the errors logs through your host (whatever control panel they use).


All times are GMT. The time now is 06:38 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01216 seconds
  • Memory Usage 1,757KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (9)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (17)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete