We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36551
    • 416 Posts
    I'm moving a site to a new server.

    The site is currently running 2.5.0. It was hacked so I'm want to install that version on the new server, import the database and assets, then upgrade to 2.6.5. However, After I run the setup for 2.5.0 and attempt to login to the manager I get a 503 error, page not found on the manager. I'm getting 500 server error on the front-end. I tried running the setup multiple times.

    Thinking there might be a corrupt file, I deleted the entire installation, re-uploaded the zip file and repeated the setup. Same result.

    This is on A2 hosting where I've got a dozen other sites running perfectly (not on this account).

    Apache Version 2.4.34
    MySQL Version 10.1.31-MariaDB-cll-lve

    For my first attempt the the server was running php 7.0. Thinking an older version of modx might prefer an older version of php, I downgraded to 5.6. No change.

    There were no errors or warnings during any of the setup routines. There are no errors in any logs that I can find.

    The htaccess is not in play.

    I've looked at the config.inc.php file all seems in order, paths look good, database server, name, pw all look fine to me.

    I also worked with A2 tech 2nd level support, they tell me that the server is not generating any errors and the problem is at the application level.

    I read in a forum post from last year MySQL MariaDB is not supported. Yet it seems to be working fine on my other sites hosted at A2 where that is being used. Is it possible this older version won't work with this? If so what are my options?

    If that's not the issue, what else? How do I get past this?

    This question has been answered by BobRay. See the first response.

      • 38783
      • 571 Posts
      Not sure if you came across this Forum post. There might be something relevant here: https://forums.modx.com/thread/102748/after-installation-503-for-root-index-500-for-manager
        If I help you out on these forums I would be very grateful if you would consider rating me on Trustpilot: https://uk.trustpilot.com/review/andytough.com

        email: [email protected] | website: https://andytough.com
        • 36551
        • 416 Posts
        Yep, that's where I saw the reference to MariaDB.
        • discuss.answer
          • 3749
          • 24,544 Posts
          Check the MODX error log (core/cache/logs/error.log).

          Also, try Dev. Tools (Ctrl-shift-i) in Chrome or Firefox. Watch the network tab as the page loads. Click on various rows in the grid and check the response tab. You may see a PHP error there.

          FWIW, I *think* you could install 2.6.5 and import your DB. The extra fields in the DB won't get populated, but I don't think that will cause any trouble. I could be wrong.

          Since you were hacked and you have an SQL dump of your DB, I'd read through it looking for suspicious code and users who don't belong unless it's from a backup from before the hack.
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 36551
            • 416 Posts
            Bob, thanks for letting me know I could import the DB from 2.5.0 into the 2.6.5. That did the trick.

            Thank you!