Support

March 31, 2017 at 7:59 am

Hi there,

The errors that you’re seeing in the app indicate that the URL input into the first field of the app login screen does not match the URL of your website. May I ask, what’s the URL that you input there?

March 31, 2017 at 8:28 am

Looking over your site the JSON API is returning error 500 when testing the andpoints.

Do you have access to the servers error logs? If so take a look and see if there are any fatal errors shown in the log recently.

Or, if you enable WP_DEBUG on the site we should be able to see the error shown then.

March 31, 2017 at 10:16 am

Do you have any security plugins installed on the site?

Do you have any plugins that alter the REST API installed on your site?
(Check your plugin list for ANY plugin that mentioned REST)

Either something is blocking the requests or your server is throwing an error when the apps are making a request (but oddly enough not when the browser makes one).

March 31, 2017 at 11:24 am

If you check your website’s .htaccess file, is there any code between these two .htaccess comments?

# Wordfence WAF
# END Wordfence WAF

March 31, 2017 at 2:26 pm

You could try this edit to the .htaccess file:
Add a new line immediately before the line that has
# BEGIN WordPress
and add this:

# Begin Custom htaccess
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
# End Custom htaccess

If you still can’t log in with the app, you can try deactivating all other plugins installed on the site except for the Event Espresso plugins and the Application Passwords plugin.

April 3, 2017 at 11:36 am

Did you make the edit to the .htaccess file?

April 3, 2017 at 1:05 pm

One way to find out would be check the server’s access logs.

April 4, 2017 at 7:07 am

You’ll look at the exact times where you tried to use the app and see if anything was logged at those moments. It may help to try the app, then immediately check the access logs.

Also, if the requests from the app are reaching your site, then you can also check what was logged from the WP REST API Log plugin at those same times.

April 5, 2017 at 7:22 pm

If your logs include IP addresses, then the IP address of your iphone will be included in the request. If your logs include user agent strings, this is what the typical user agent string from the app:

EventEspressoHD\/3 CFNetwork\/808.3 Darwin\/16.3.0

April 6, 2017 at 12:10 pm

You can check with your host to see if they have mod_security rules or a firewall configured to block requests from the app.

April 7, 2017 at 12:44 pm

Some examples include:

/wp-json/ee/v4.8.36/site_info

/wp-json/ee/v4.8.36/events?where%5BDatetime.DTT_EVT_start%5D%5B%5D=%3E&where%5BDatetime.DTT_EVT_start%5D%5B%5D=2017-04-07T23:59:00&order_by%5BEVT_name%5D=ASC&include=Datetime.*,Venue.*&calculate=Datetime.spaces_remaining_considering_tickets,Datetime.registrations_checked_in_count,Datetime.registrations_checked_out_count,Datetime.spots_taken_pending_payment,image_thumbnail,image_large,image_medium&limit=0,50&caps=read_admin

April 10, 2017 at 10:01 am

The part in the .htaccess file where you added

# Begin Custom htaccess
SetEnvIf Authorization “(.*)” HTTP_AUTHORIZATION=$1
# End Custom htaccess

needs to get moved to the line before
# BEGIN WordPress

because otherwise the next time the rewrite rules get reset, you’ll lose those changes.

Can you check with your host to see if they’ll allow the Authorization header to get passed in the request?

April 10, 2017 at 3:36 pm

They confirmed that they allow such modification, but can they confirm that they’ll actually allow the Authorization header to get passed when using Basic Auth?

April 10, 2017 at 4:33 pm

You can use the Postman app to send a GET request to the /registrations/ route and include your WordPress username and password in the Basic Auth header.

This is a screenshot that shows an example of the above request in Postman:

https://www.evernote.com/l/AAR1Lix4IyBK5IXi4I8DJ5vuD5rSNWOnr0I

April 11, 2017 at 9:27 am

No, the /registrations/ route on your site is:

http://tickettail.com/wp-json/ee/v4.8.36/registrations

When I try the above URL in Postman, I get a 500 server error, so it’s looking like a fatal error is being thrown on your site when that route is requested.

April 11, 2017 at 10:04 am

I can suggest that you activate WP_DEBUG and check the debug.log file in the wp-content folder and/or check the server’s error logs for the time when you got the 500 server error.

April 11, 2017 at 11:52 am

I can advise that you contact your host about the error because that’s a server configuration issue. You’ll note that there’s no issue with the same URL pattern if it’s a request that doesn’t require authorization, like this one:

http://tickettail.com/wp-json/ee/v4.8.36/events/

April 12, 2017 at 11:07 am

The host will need to fix the configuration to allow the Authorization header to be passed when Authentication is required for a GET request. How is it that changing the path called by the URL is going to fix anything?

Did you actually share the “Permission denied:” error message with the host so they can review?