|
rdowling90
|
September 3, 2018 at 8:30 am
Hi I have the following error messages appearing on the app when logging in:
iPhone – “Error Occurred. The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.”
Android – “Connection error. Unable to load data.”
From what I recall this error may have started appearing when I migrated the website to a different server, so could be server related?
I have followed the troubleshooting guides to include the line in .htaccess without success.
|
|
Josh
|
September 4, 2018 at 7:21 am
Hi,
Yes it could be server related because not all web servers are configured to allow passing the Authorization header in the request. That’s what the app uses to authenticate with your site.
You could check with your web host to see if the server is configured to block the HTTP Authorization header, and if that’s the case can they unblock it?
|
|
rdowling90
|
September 4, 2018 at 9:12 am
Thanks, after sending that on to the hosting provider they added the following to .htaccess:
RewriteEngine On
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule .* – [e=HTTP_AUTHORIZATION:%1]
However I still have issues. Any thoughts? Is it possible that having reCaptcha on my admin login page would affect this?
When entering the website URL to login to the app, should I be using my homepage website address or the admin login address? When I use the homepage it seems to login but then after a while of loading I get a time out error – “The request timed out”. When using the admin login, I get the error I mentioned in my first post…
Not sure if it’s relevant but when these error messages appear they pop-up about 4 times on-top of each other…
|
|
Josh
|
September 4, 2018 at 9:34 am
You should be using the homepage website address. The apps do not use the WP-admin, so any plugins that add things to the wp-admin page (like a reCAPTCHA challenge) will not affect the app.
So it sounds like the Authorization header is getting passed, and when you use the correct URL to connect the app to the site the only issue now is the request is timing out. Your host may be able to set the max_execution_time value to a higher limit which will help in case the limit is low.
|
|
rdowling90
|
September 5, 2018 at 7:14 am
Ok thanks for confirming the login URL. The hosting provider has increased the max_execution_time on the domain to a generous 600 seconds. However I still get “The request timed out” after about 20 seconds or so.
Any further thoughts on what is causing this? Any other server configurations that might need adjusting?
Again I am certain this is server related as the app works when I connect to my old version of the site on my development server.
Thanks.
|
|
Josh
|
September 5, 2018 at 7:40 am
I’m not aware of a server setting that would cause a timeout, unless it involved blocking your device from doing a GET request. Are all the same plugins installed on the new site that were on the old version of the site?
|
|
rdowling90
|
September 6, 2018 at 8:32 am
I mentioned your comment to the host, they replied saying they “set Access-Control-Request-Origin in the .htaccess file”. The issue still persists however.
There are two new plugins, ‘Really Simple SSL’ and ‘Limit Login Attempts’ installed on the new version. I tried de-activating these but no change. I even installed those plugins on the old version to see if it would stop that one working but it still did.
Any other ideas?
|
|
Josh
|
September 6, 2018 at 10:22 am
You could gather as much information about the development server as possible, then send that information over to the host of the live server and maybe they can configure the new server in the same way as the development server.
That said, I’m not aware of any specific settings that would not allow the app to connect to the site.
|
