Unable to Connect to Site

[designcouch]

The backend is installed in my manager (mxManager v 1.0.0 beta, MODX v 2.3.3) and the app is installed on my phone. When I enter my site info (correct manager url, username and password) it gives me the following notification when I attempt to complete setup:

"Unable to connect to site. Maybe app backend is not installed?"

Have attempted both on my staging site and my production site. Not sure if it's worth mentioning, but my site is also hosted on MODX Cloud.

[bezumkin]

It`s a little typo, sorry. You need to add slash at the end of the url of manager: http://site.com/manager/30.04.2015, 00:45, "Jesse Couch" notifications@github.com:The backend is installed in my manager (mxManager v 1.0.0 beta, MODX v 2.3.3) and the app is installed on my phone. When I enter my site info (correct manager url, username and password) it gives me the following notification when I attempt to complete setup:

"Unable to connect to site. Maybe app backend is not installed?"

Have attempted both on my staging site and my production site. Not sure if it's worth mentioning, but my site is also hosted on MODX Cloud.

—Reply to this email directly or view it on GitHub.

[designcouch]

Unfortunately this did not resolve my problem. I had tried that previously, but tried it again just now so that I could be sure.

[bezumkin]

Try this credentials: http://s1729.h3.modhost.pro/manager/ s1729 123456789012 It is working for me.

[designcouch]

That worked just fine. Is the version of your app backend in the MODX addons library current with the version installed at the above provided url?

[bezumkin]

Yes, of course.

Try to check any redirect rules on your site. App expects HTTP code 200 only from manager url.

[designcouch]

Just double checked my manager's http code - it is indeed 200, and there are no redirects present.

[bezumkin]

Try to manually authenticate via mxManager:

http://test23.dev/manager/?mx_action=auth&username=yourname&password=yourpass&debug=1

You must see something like this

Array
(
    [success] => 1
    [message] => 
    [data] => Array
        (
            [rows] => Array
                (
                    [0] => view_site
                    [1] => resources
                    [2] => elements
                    [3] => files
                    [4] => error_log
                    [5] => manager_log
                    [6] => clear_cache
                )
            [site_url] => http://s1729.h3.modhost.pro/
            [version] => MODX Revolution 2.3.3-pl (traditional)
        )
)

For example - http://s1729.h3.modhost.pro/manager/?mx_action=auth&username=s1729&password=123456789012&debug=1

[designcouch]

I am not seeing that. I've tried removing and reinstalling the extra, removing my core/cache directory, clearing the cache via a manager action, clearing all sessions, etc. At this point, I believe it's either a conflict with an existing plugin, or a conflict with MODX Cloud.

[mikelannen]

Can you remove me from this thread please?

Best Regards,

MIKE LANNEN Founder + Creative Director ETERNITY WEB http://www.EternityMarketing.com

(802) 865-2000 x700

We've Moved!

182 Main Street Studio 3 Burlington, VT 05401

On Wed, Apr 29, 2015 at 3:24 PM, Jesse Couch notifications@github.com wrote:

I am not seeing that. I've tried removing and reinstalling the extra, removing my core/cache directory, clearing the cache via a manager action, clearing all sessions, etc. At this point, I believe it's either a conflict with an existing plugin, or a conflict with MODX Cloud.

— Reply to this email directly or view it on GitHub https://github.com/bezumkin/mxManager/issues/11#issuecomment-97551010.

[bezumkin]

Can you remove me from this thread please?

I don`t know why you subscribed to this thread, but you can unsubscribe.

[mikelannen]

I never subscribed to it. I will try to unsubscribe.

Best Regards,

MIKE LANNEN Founder + Creative Director ETERNITY WEB http://www.EternityMarketing.com

(802) 865-2000 x700

We've Moved!

182 Main Street Studio 3 Burlington, VT 05401

On Wed, Apr 29, 2015 at 9:13 PM, Vasily Naumkin notifications@github.com wrote:

Can you remove me from this thread please?

I don`t know why you subscribed to this thread, but you can unsubscribe. https://file.modx.pro/files/5/b/1/5b126327a8523cd2db4c3156590b7f75.png

— Reply to this email directly or view it on GitHub https://github.com/bezumkin/mxManager/issues/11#issuecomment-97625280.

[designcouch]

This is not something I would consider closed, as the issue is still present and unresolved.

[bezumkin]

This issue is not in mxManager because you can`t even run this simple test.

[designcouch]

It is indeed with either mxManager, or a conflict with something else in my environment - I have run that test, and responded after I did so. The first sentence of that response tells you that I tried your suggestion. I then went on to elaborate on other methods I had tried.

[bezumkin]

If your site did not responds to that simplest request - what can I do?

For example - here the answer of an usual site http://xn--k1afafcmw8d.xn--p1ai/manager/?mx_action=any

{"success":false,"message":"\u041d\u0435\u0432\u0435\u0440\u043d\u044b\u0439 \u0437\u0430\u043f\u0440\u043e\u0441.","data":[]}

You the only one who reported about this issue, so I think, that is your local trouble.

[designcouch]

I'm an experienced developer using a very straight-forward configuration of MODX on a completely typical environment. If I'm reporting this issue, then there's an issue. You're in beta - you can't afford to simply discount this feedback as an "isolated incident" in a test group of less than 100 people. That's quite irresponsible of you as a dev. Were I in your shoes, I would go through the trouble of gathering more information and attempting to replicate the issue instead of being prideful and saying "it must just be you." You're not going to be the first developer in history who has a completely bug-free beta. It just doesn't happen.