500 Server Error on several parts o the Back Office [Solved]



  • I just opened an Issue on Github found here: Issue #378

    I want to verify if this is a problem or just a configuration issue… anybody else experiencing the same?

    Im hosting on a 1and1.com server.



  • Have you turned on error reporting? Did it give any clue as to what the issues were?



  • @lesley wasnt able to but weirdly enough few minutes later the store started working fine…

    seems like a host error to me… will mark the issue as resolved until further checks are perfomed.



  • I just upgraded for 1.03 to 1.04 I did a clean & fix DB issues and now I get this 500 Error on the 3 area’s listed above I did have access before I did that also the updater is not working from 1.04 to 1.05 any ideas?



  • Oh I turned on the debug I get 500 error pn Performance & Modules but on payments I see this:
    Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Crypt_RSA has a deprecated constructor in /homepages/31/d658016058/htdocs/modules/googleshopping/lib/phpseclib/Crypt/RSA.php on line 280

    Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Crypt_Hash has a deprecated constructor in /homepages/31/d658016058/htdocs/modules/googleshopping/lib/phpseclib/Crypt/Hash.php on line 82

    Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Math_BigInteger has a deprecated constructor in /homepages/31/d658016058/htdocs/modules/googleshopping/lib/phpseclib/Math/BigInteger.php on line 176



  • Obviously a problem of this googleshopping module. Ignoring that these security relevant classes are probably pretty dated, you can try to rename these constructor methods to just __construct(... (two underscores in front).

    What is the constructor method? Well, the method (function) with the same name as the class. If the class is called RSA, then its old-style constructor is function RSA(.... Also identifiable by the line number given in the deprecation message.



  • I don’t use googleshopping so how do I remove whole thing? I should mention my shop was mirgrated from PS to 30B’s



  • Find it in the list in back office -> Modules & Services and select Delete from the menu. Not just Disable or Uninstall.



  • See that is part of the issue when I click modules & services I get a 500 internal server Error by removing google shipping by FTP I php errors are gone on the payment link but now even that too gives a internal 500 error. any guesses like I said I used the 30 bees tool to fix & repair the db and they I used the tool under that to optimize.



  • Then you have to go to the file system and remove it there. It’s the modules/googleshopping/ folder. Remove it entirely, but keep a backup somewhere outside the shop.

    And then cross fingers this module didn’t install overrides. Getting rid of them without having the module is pretty complicated.



  • Done no difference still have the internal server error on the 3 sections performance,payment,Modules & services



  • Which error is it now when turning on debug mode? Can’t be the same as before.

    One can have debug mode turned on all the time until such stuff is sorted. Worst case customers see error messages.



  • front end does not seem to be effected so far that I can tell it’s not a busy time for me but I would like to get the whole thing sorted out. I just didn’t want to loose the history on the website but maybe I should just say F it & do a fresh install.



  • You could also try to delete class_index.php file in cache directory. Many times the stale class cache is the root cause of such issues



  • @datakick nope tried your suggestion same thing was worth a shot



  • One thing to try is to turn off non-thirtybees modules. There are two switches on back office -> Advanced Parameters -> Performance to do this, Disable non thirty bees modules and Disable all overrides.

    If the shop works with these two switches turned on, you can keep history fairly easy:

    1. Get the 1.0.6 release package.
    2. Remove folders modules and overrides entirely and replace them with the ones coming with the release.
    3. Install required third party modules again.


  • I cannot access that section it`s one of the ones that gives the 500 error what if I update all the files to 1.6 and still remove the for-mentioned files and replace



  • what does the server’s error log say?



  • where is it kept I will pull it under logs I guess?



  • what if I update all the files to 1.[0.]6 and still remove the for-mentioned files and replace

    Sounds like a good idea. At least if finding the problem fails.


 

Looks like your connection to thirty bees forum was lost, please wait while we try to reconnect.