We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 41651
    • 10 Posts
    No specific reason I just setup a couple of dummy subdomains to test things out. I'll try that out and let you know.
      • 41651
      • 10 Posts
      Unfortunately that did not work, I am getting the same errors. I even moved my wordpress site and tried a fresh upload non-ftp to the root directory and still the same errors.

      Curiously enough I am able to install this with simple scripts from the fatcow control panel (I generally do not use this, at all), though logging into manager does not work, even resetting the password by the reset password link from my email doesn't work, it just stays on the login screen. So I have it installed but now I can't login, go figure. I'm sure there is something about that particular issue so I'm going to do a bit of research.
        • 10208 ☆ A M B ☆
        • 1,780 Posts
        The last simple scripts install I did (first, and last...) was a nightmare beginning to end, but that had more to do with the server than anything. I have experienced however, install scripts who forget to set the Default Admin to role to super user which locks the admin out of the manager from the get go.

        Go to the database and check the users table. On your user, check the primary_group and sudo fields. They should both be set to 1 (change to 1 if not). The sudo setting will get you in, then you can check your user group. It should be Administrator.
          Frogabog- MODX Websites in Portland Oregon
          "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
          Having server issues? These guys have MODX Hosting perfected - SkyToaster
          • 10208 ☆ A M B ☆
          • 1,780 Posts
          Here's something else to check from the troubleshooting info in docs. Your original error talks of sessions...

          http://rtfm.modx.com/display/revolution20/Troubleshooting+Installation#TroubleshootingInstallation-Theloginpagekeepsredirectingmebacktotheloginscreenwithnoerror



          The login page keeps redirecting me back to the login screen with no error

          This can happen with older Revolution beta installs. To fix it, delete the following 3 system settings from the DB table `[prefix]_system_settings` (where prefix is your table prefix):

          session_name
          session_cookie_path
          session_cookie_domain

          Then delete the core/cache/config.cache.php file.

          Unless, of course, you've changed these explicitly for some purpose of your own.
            Frogabog- MODX Websites in Portland Oregon
            "Do yourself a favor and get a copy of "MODX - The Official Guide" by Bob Ray. Read it.
            Having server issues? These guys have MODX Hosting perfected - SkyToaster
            • 41651
            • 10 Posts
            Quote from: frogabog at Oct 11, 2012, 07:40 PM
            Here's something else to check from the troubleshooting info in docs. Your original error talks of sessions...

            http://rtfm.modx.com/display/revolution20/Troubleshooting+Installation#TroubleshootingInstallation-Theloginpagekeepsredirectingmebacktotheloginscreenwithnoerror

            Yeah, I hate simple scripts... I much prefer to setup everything myself. I've already removed modx through simple scripts but maybe I can try to troubleshoot it that way. I found something about sessions and:

            chmod 777 -R /var/lib/php/session


            based on this post: https://forums.modx.com/thread/28834/revolution-install-problem

            unfortunately I do not have access. I'll try the simple script route and check a couple of mysql tables. Thanks for all the help, I appreciate it.
              • 41651
              • 10 Posts
              So I followed that guide, deleted those values and the cache file, looked at the users table and both are set to 1 and I am set to the default admin. Now I noticed a couple of interesting things... 1 is I looked through user attributes and it shows that I logged in 4 times and 0 failed login attempts, so I'm assuming that I am in fact logging in. And the other interesting thing that I noticed is the hashing system makes no sense... why would the password be the same exact value as the salt? Both were hashed using md5; maybe that is an issue with simplescipts. Unless that was intentional like using md5 as a suitable hashing algorithm for storing passwords... why not sha256 or sha512?

              I'm at a loss, I can't install modx manually and I can't get it to work with simple scripts. I appreciate your help and I've been trying to find different ways to get it to work but nothing seems to be working. I'm going to continue because now I'm going to get it working out of spite for FatCow.

              *EDIT* Upon further inspection the default hashing method is actually PBKDF2 which is exactly what I'm using for my login system, except I use sha512, and you guys are using 256 default. I wonder why my hashing method was set to md5 and both salt and password had the same hash... very interesting to me.

              **EDIT** I installed xampp on my personal computer and was able to install modx without errors (with the same packaged zip file) so the .zip file is not corrupt. I'm going to have to assume it is an issue with my web hosting. I will just have to call them and find a reasonable solution. Thanks for all the help. [ed. note: kiasta last edited this post 14 years ago.]
                • 18373 ☆ A M B ☆
                • 3,141 Posts
                Going back a few steps, you are saying you see this error still?
                Make sure your PHP session configuration is valid and working

                That's a fatal error for a reason, and likely something you will need to get in touch with your host for. The setup sets a session var, redirects you to a different page, and checks that session var to ensure that sessions are working on the server. If it can't retrieve the value from the session var, that is obviously a serious problem and it will prevent you from running setup until it's been solved.

                In some cases it could be a permissions issue (as you tried but didn't have access for), but it could also be a php misconfiguration. That's not really my area of expertise, so I suggest sending a ticket to the host asking them to check it out and resolve the issue.

                Why the one click install worked? Probably cause it doesn't care about errors and has its own methodology of creating a new instance of MODX without ever doing the health checks the setup performs. In case you hadn't noticed, I'm not a fan of those kind of scripts either wink The reason the hash was set to MD5 is probably from the way the one click script creates the user. As of 2.1.0, PBKDF2 is the default and newly created users will have those with a proper salt.
                  Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

                  Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.