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

    I installed the latest version of modx-2.5.4-pl from installation package. Steps, which I did:

     
    wget https://modx.s3.amazonaws.com/releases/2.5.4/modx-2.5.4-pl.zip
    unzip modx-2.5.4-pl.zip
    mdkir /var/www/modx && mv -fT modx-2.5.4-pl /var/www/modx
    chown -R httpd:httpd /var/www/modx
    


    After I opened http://my.site.com/setup and went through installation process without errors.
    Now when I am trying to log in http://my.site.com/manager - I get the blank page with 200 code after putting credentials.

    OS - Centos 6. Apache/2.4.18 (Red Hat). php 5.6.9 compiled as a module.
    Compilation flags:
    './configure' '--with-apxs2=/opt/rh/httpd24/root/usr/bin/apxs' '--enable-maintainer-zts' '--disable-ipv6' '--with-mysql' '--enable-mbstring' '--enable-libxml' '--enable-dom' '--enable-xml' '--enable-xmlreader' '--enable-xmlwriter' '--without-pear' '--with-mcrypt=ext/mcrypt/' '--with-gd' '--with-mysqli' '--enable-simplexml' '--with-zlib' '--with-pdo_mysql' '--with-vpx-dir=/usr/lib64' '--with-jpeg-dir=/usr/lib64' '--with-xpm-dir=/usr/lib64' '--with-freetype-dir==/usr/lib64' '--with-curl' 


    No errors in apache and php error log. Even with php.ini settings:
    display_errors = On
    log_errors = On
    error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT


    In access log I see:
    ...
    - - [11/Jan/2017:11:02:55 +0100] "POST /manager/ HTTP/1.1" 302 -
    - - [11/Jan/2017:11:02:55 +0100] "GET /manager HTTP/1.1" 301 247
    - - [11/Jan/2017:11:02:55 +0100] "GET /core/docs/changelog.txt HTTP/1.1" 206 1
    - - [11/Jan/2017:11:02:55 +0100] "GET /manager/ HTTP/1.1" 200 -



    I see the next messages in core/cache/logs/install.config.2017-01-11T10.29.12.log:
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/2a724313a9b7e6abf3d81c60f57b2e63/0/ to /var/www/modx/index.php
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/2a724313a9b7e6abf3d81c60f57b2e63/1/ to /var/www/modx/ht.access
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/87fcd742aadfb6c7056f8af912fc5787/0/ to /var/www/modx/manager/assets
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/87fcd742aadfb6c7056f8af912fc5787/1/ to /var/www/modx/manager/controllers
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/87fcd742aadfb6c7056f8af912fc5787/2/ to /var/www/modx/manager/templates
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/87fcd742aadfb6c7056f8af912fc5787/3/ to /var/www/modx/manager/min
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/87fcd742aadfb6c7056f8af912fc5787/4/ to /var/www/modx/manager/ht.access
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /var/www/modx/core/packages/core/modContext/87fcd742aadfb6c7056f8af912fc5787/5/ to /var/www/modx/manager/index.php
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /var/www/modx/core/packages/core/xPDOFileVehicle/d814151617e976887af7a24c1ce65c78/ to /var/www/modx/connectors/
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /var/www/modx/core/packages/core/xPDOFileVehicle/5c11eeeb6af6006377decec1fdac1c01/ to /var/www/modx/connectors/
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /var/www/modx/core/packages/core/xPDOFileVehicle/a147d2ea23b7e0dc1d3038c829e529c8/ to /var/www/modx/connectors/
    [2017-01-11 10:29:19] (ERROR @ /var/www/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /var/www/modx/core/packages/core/xPDOFileVehicle/6ae8d7fb3556f5083957458d7c407b11/ to /var/www/modx/connectors/


    What I already have tried:

    1. Different modx versions 2.5.2, 2.4.4 - story the same.
    2. Building from git as described here https://docs.modx.com/revolution/2.x/getting-started/installation/git-installation . No errors in install.log, but the same result.
    3. Different installation options and directory permissions.
    4. sql_mode= in mysql.
    5. Enabling modx debug, by adding into manager/index.php:

    if (!MODX_API_MODE) {
        [b]$modx->setDebug(true);[/b]
        $modx->request->handleRequest();
    }


    core/cache/logs/error.log has appeared. In ends like this:
    ...
    [2017-01-11 11:06:48] (DEBUG @ /var/www/modx/core/xpdo/xpdo.class.php : 1520) Returning validation rules: Array
    (
        [id] => Array
            (
                [invalid] => Array
                    (
                        [type] => preg_match
                        [rule] => /^[0-9a-zA-Z,-]{22,255}$/
                        [message] => session_err_invalid_id
                    )
    
            )
    
    )
    
    [2017-01-11 11:06:48] (WARN @ /var/www/modx/core/xpdo/validation/xpdovalidator.class.php : 123) Validation succeeded: Array
    (
        [id] => 1
    )
    
    [2017-01-11 11:06:48] (DEBUG @ /var/www/modx/core/xpdo/om/xpdoobject.class.php : 2178) Validator class executed, result = 1
    [2017-01-11 11:06:48] (DEBUG @ /var/www/modx/core/xpdo/xpdo.class.php : 1775) Returning ancestry for modSession: Array
    (
        [0] => modSession
        [1] => xPDOObject
    )
    
    [2017-01-11 11:06:48] (WARN @ /var/www/modx/core/xpdo/validation/xpdovalidator.class.php : 123) Validation succeeded: Array
    (
        [id] => 1
    )
    
    [2017-01-11 11:06:48] (DEBUG @ /var/www/modx/core/xpdo/om/xpdoobject.class.php : 2178) Validator class executed, result = 1


    I compared this to working modx installation and it looks the same.

    I am already struggling with it for a day. Cannot understand what is wrong. Could anybody help?
      • 3749
      • 24,544 Posts
      Did you use UpgradeMODX to do the update? If not, try deleting all files in the core/cache directory.

      In any case, try logging in with your browser in incognito or private mode. Sometimes a leftover cookie or browser cache file will mess things up after an upgrade. If that works, clear you browser cache and cookies.
        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
        • 53144
        • 4 Posts
        Quote from: BobRay at Jan 12, 2017, 08:29 AM
        Did you use UpgradeMODX to do the update? If not, try deleting all files in the core/cache directory.

        In any case, try logging in with your browser in incognito or private mode. Sometimes a leftover cookie or browser cache file will mess things up after an upgrade. If that works, clear you browser cache and cookies.

        It is a fresh installation. Not an upgrade.

        I have already tried to clean up all cookies and to access manager page in incognito mode.
        Also tried to remove core/cache directory.
        Nothing works.
          • 3749
          • 24,544 Posts
          Sorry, I missed that it was a new install.

          You've probably already tried running setup again in upgrade mode, but if not, give that a shot.

          You can check the permissions and ownership of the files and directories, though normally, Setup would complain about problems with that.

          A session problem can cause login failures, though that usually lands you back at the login page.

          Also, make sure that compress_css and compress_js are both off in the modx_system_settings table.

          Check the paths and urls in the core/config/config.inc.php file, especially the connectors ones.

          Make sure the character set there matches the character set of the DB.

          If none of that works, check the network tab in Firefox or Chrome Dev. Tools and see if you can find a failed get, or a processor response that shows an error.

          If your server is disallowing external connections, the Manager dashboard makes some outside connections for the security feeds and other things, so it might hang if it can't do that.

          On very rare occasions, a file gets corrupted or lost in the transfer, so re-downloading and re-installing is a last resort.


          [ed. note: BobRay last edited this post 7 years, 3 months ago.]
            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
            • 53144
            • 4 Posts
            Quote from: BobRay at Jan 13, 2017, 07:50 AM
            Sorry, I missed that it was a new install.

            You've probably already tried running setup again in upgrade mode, but if not, give that a shot.

            You can check the permissions and ownership of the files and directories, though normally, Setup would complain about problems with that.

            A session problem can cause login failures, though that usually lands you back at the login page.

            Also, make sure that compress_css and compress_js are both off in the modx_system_settings table.

            Check the paths and urls in the core/config/config.inc.php file, especially the connectors ones.

            Make sure the character set there matches the character set of the DB.

            If none of that works, check the network tab in Firefox or Chrome Dev. Tools and see if you can find a failed get, or a processor response that shows an error.

            If your server is disallowing external connections, the Manager dashboard makes some outside connections for the security feeds and other things, so it might hang if it can't do that.

            On very rare occasions, a file gets corrupted or lost in the transfer, so re-downloading and re-installing is a last resort.



            Thank you for your help. Basically I have tried everything mentioned here already.

            Here is what did help for me:
            mysql> update `modx_system_settings` set `value`='http://feeds.feedburner.com/modxsecurity' where `key`='feed_modx_security';
            Query OK, 1 row affected (0.00 sec)
            Rows matched: 1  Changed: 1  Warnings: 0


            The default value is http://forums.modx.com/board.xml?board=294 . I know that modx uses this link to show in window inside manager. And I know that is actually requests data remotely and caches it.

            I have checked few times and I am able to retrieve the content of the default link from the server. This works fine from the server:

            [#]$ wget http://forums.modx.com/board.xml?board=294
            --2017-01-13 15:10:32--  http://forums.modx.com/board.xml?board=294
            Resolving forums.modx.com... 169.46.7.136
            Connecting to forums.modx.com|169.46.7.136|:80... connected.
            HTTP request sent, awaiting response... 301 Moved Permanently
            Location: https://forums.modx.com/board.xml?board=294 [following]
            --2017-01-13 15:10:32--  https://forums.modx.com/board.xml?board=294
            Connecting to forums.modx.com|169.46.7.136|:443... connected.
            HTTP request sent, awaiting response... 200 OK
            Length: unspecified [text/html]
            Saving to: “board.xml?board=294”
            
                [ <=>                                                                                                                                                                                                ] 6,442       --.-K/s   in 0s
            
            2017-01-13 15:10:33 (556 MB/s) - “board.xml?board=294” saved [6442]


            So, for some reason modx is not able to get the content from default link. Maybe because of 301 redirect to https page. I still don't know why.
            Anyway I would prefer to see error-message in this case. Doesn't look like good design.
              • 3749
              • 24,544 Posts
              Yes, that's what I was referring to with this: "If your server is disallowing external connections, the Manager dashboard makes some outside connections for the security feeds and other things, so it might hang if it can't do that."

              There are two system settings in the modx_system_settings table that turn the feeds on and off:

              feed_modx_news_enabled
              feed_modx_security_enabled

              If you set the value field for both to 0, MODX won't try to access those URLs (and your Manager will load faster). I usually turn them off since I subscribe to security alerts via email.

              FYI, if it's not a problem with your server, the problem might be temporary. Maybe one of the servers went down or took too long to respond -- or you might have gotten into the Manager if you waited long enough.

              I agree that the response should be more graceful if one of the feeds fails.

                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
                • 53144
                • 4 Posts
                Quote from: BobRay at Jan 14, 2017, 05:12 AM


                feed_modx_news_enabled
                feed_modx_security_enabled


                Thank you! Will update these settings.