|
Pedro Ordenes
|
May 8, 2016 at 4:54 pm
We are so excited to check out the new app – but I’m getting the “requested resource could not be found” error upon login attempt. I am using WordPress 4.5.2 and EE 4.8.43. I also re-saved permalinks which are set to post name anyway, but to no avail. Thanks in advance for any suggestions!
|
|
Josh
|
May 9, 2016 at 8:43 am
Hi Lauren,
The error you’re seeing is because there’s an issue happening when the authentication headers are supposed to be sent. We’ve seen this issue occur when it’s a server that’s using FCGI. Are you comfortable with making an edit to your .htacess file that will help allow the authentication headers to authenticate the app?
|
|
Pedro Ordenes
|
May 9, 2016 at 11:37 am
Yes. Please let me know what I can do. Thanks!
|
|
Josh
|
May 9, 2016 at 8:19 pm
You can follow the steps from this guide:
https://eventespresso.com/wiki/ee4-event-apps/#troubleshooting
|
|
pupung purnama
|
May 11, 2016 at 11:33 pm
Awesome, I’ll update you once done.
Thanks,
|
|
Pedro Ordenes
|
May 12, 2016 at 5:48 am
Hi Josh! Thanks for the easy instructions. I’m still getting the same message, though. Plugin is installed and activated, .htaccess is correctly updated… maybe it takes a bit of time for the app to realize it?
|
|
Josh
|
May 12, 2016 at 8:24 am
Nope, it should be instant. If the above doesn’t fix the issue for you, then there’s a different reason why you’re seeing the error.
Can you deactivate any JSON API plugins that are installed on your site? If there are any of the older JSON API plugins installed, those will change the endpoints and the app will not be able to access the correct endpoints.
|
|
Pedro Ordenes
|
May 12, 2016 at 8:36 am
That fixed it! Two more things – it doesn’t show any 2016 events – not in search, or under upcoming or today – but it does for all the years prior. Then, on the old events which it does show, I’m unable to view attendee lists as explained by a super long error message that basically suggests I probably can’t see them because I’m not an admin, even though I’ve signed in with an admin account. Any ideas?
|
|
Josh
|
May 12, 2016 at 8:48 am
You’re technically not signed in if it gives you that message. Which version of the Basic Auth plugin is activated right now?
|
|
Pedro Ordenes
|
May 12, 2016 at 8:49 am
0.1
|
|
Josh
|
May 12, 2016 at 8:59 am
This looks like it may be an nginx server, so the edits to the .htaccess file may not have the affect of allowing the authentication headers. Do you have any security plugins activated?
|
|
Pedro Ordenes
|
May 12, 2016 at 9:05 am
I have WordPress HTTPS and Cartpauj Register Captcha. I also have s2member installed; I know it pulls some strings to protect the dashboard being accessed by lower level users, but I don’t believe that should be an issue here since I’m logging in with an admin account. Thanks for all your help!
|
|
Josh
|
May 12, 2016 at 12:42 pm
I’m not sure there’s much we can do if the site doesn’t use the .htaccess file and the Basic Auth plugin isn’t allowed to pass the Authentication headers. We can investigate further to try to understand for sure why the Authentication is failing if you can send WP admin and FTP credentials over our secure form on this page:
https://eventespresso.com/send-login-details/
|
|
Steve
|
May 15, 2016 at 1:44 pm
This sorted my issue too! thanks.
Will this get incorporated into the app so that we don’t have to add this special extras?
|
|
Josh
|
May 16, 2016 at 9:14 am
No, they’ll have to find/build a different means to authenticate that doesn’t use http headers. If your server doesn’t allow the authentication headers, there’s not much the app can do to change that.
|
|
Aaron Claessens
|
May 20, 2016 at 5:43 am
I this the right place to note another issue with the nginx server not working? Same symptoms, “attendees” are not displayed in the app. I added the plugin and updated the htaccess file, and no luck …
Thanks
|
|
Josh
|
May 20, 2016 at 6:19 am
Hi Aaron,
It’s not. Are you sure it’s an FCGI server?
|
|
Aaron Claessens
|
May 20, 2016 at 7:10 am
Thanks Josh, I can open a new thread if you want.
This is a nginx server that appears to not use .htaccess (AMIMOTO Amazon Instance) … it seems to also be running FCGI, but I’m not as sure on this.
|
|
Josh
|
May 20, 2016 at 8:19 am
It’s likely that your server isn’t compatible with the current method of Authentication that the mobile apps use. They’re going to work in another method of Authentication that should be compatible with a wider variety of servers. When that’s ready, I do not know because they’re off to a slow start on making that happen.
|
