|
CraigK
|
May 27, 2016 at 1:42 pm
Hi everyone. I wonder if you can help.
** CONFIG **
I have installed EE4 Everything, with ticketing options.
I have installed Event Espresso 4 from iOS App Store onto iPhone 6s. (Version 1.0.0)
** Setup **
Created 3 test events:
Event 1 – runs over 3 days, started today
Event 2 – runs over 6 days, starts in the future
Event 3 – runs over 1 day, started today
** TESTING **
I have run testing on scanning of the tickets and none of the images used have been approved (allowed) for registration / checkin of the ticket.
– First test run through mobile application using scanning icon on top right of mobile screen (with all events listed) so I assume this is a generic scan and not for a specific event.
– Second test run through mobile application using scanning icon on top right of mobile screen, for a specific event.
(Note: With both tests I have scanned both the Bar-code and the QR-code).
** RESULT **
With all tests the mobile application is returning a error code of:
“This ticket is for a different event”.
(Note: I have used the iPhone with the Mobile App to scan the tickets, and have tested against the screen of a MacBook and also an iPad, with both devices displayed the HTML images and the tickets looked perfect.)
?? Can anyone shed some light on this ??
|
|
Josh
|
May 27, 2016 at 2:10 pm
This might be an authentication issue. When you click on one of the event’s attendees list, does it display a list of attendees or does it show an authentication error?
|
|
CraigK
|
May 30, 2016 at 2:43 pm
Hi Josh.
When clicking on any of the 3 event attendee lists, it comes up with an “Error Occurred”:
The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorised response, authenticating will make no difference. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant client permission to access the resource (e.g., a recognised user attempting to access restricted content).
I have no idea?
Any suggestions?
|
|
Josh
|
May 31, 2016 at 11:34 am
Hi there,
The error you saw means that there was an error when the app tried to authenticate with your server that has Event Espresso installed. Some server configurations have some issues with the Basic Authentication method (which is how the app authenticates). If your server uses FCGI, then you can work around the authentication issues by following the steps in this other thread:
https://eventespresso.com/topic/ee4-app-error-requested-resource-could-not-be-found/#post-203548
|
|
CraigK
|
May 31, 2016 at 4:04 pm
Hi Josh.
Thanks for the update.
I have :
1. Edited htaccess file
2. Uploaded Basic Auth plugin
3. Disabled the only JSON plugin I had.
No Luck.
I am not sure how to figure out if my servers are running FCGI as its hosted through servers in the UK on the 1and1.co.uk Hosting Services.
Any further suggestions? (Still same error).
|
|
CraigK
|
May 31, 2016 at 4:11 pm
To confirm – Running PHP 5.6 on the site.
|
|
Josh
|
June 1, 2016 at 8:25 am
The troubleshooting guide has further suggestions:
https://eventespresso.com/wiki/ee4-event-apps/#troubleshooting
|
|
CraigK
|
June 5, 2016 at 5:22 pm
Hi Josh.
Thanks for the direction advice on what to do.
Unfortunately, using the troubleshooting guide has not helped.
I have contacted the hosting company – its on a shared server( so they have other customers), and CGI/FCGI is enabled with no option to change.
Any further suggestions ?
—
Should I be asking their server experts to change authentication for the domain or something else?
|
|
Josh
|
June 6, 2016 at 2:14 pm
Sure, maybe you can pass along these links that have examples showing how to allow passing the Authorization header through to FastCGI:
http://orangejuiceliberationfront.com/http-auth-with-php-in-cgi-mode-e-g-on-dreamhost/
http://www.besthostratings.com/articles/http-auth-php-cgi.html
|
|
etcwebdivision
|
June 17, 2016 at 9:52 am
I’m having the exact same issue as described by Craig here. Were you ever able to solve the issue by contacting your host?
|
|
Josh
|
June 17, 2016 at 10:05 am
Hi etc,
Can you start a new thread and let us know whether you’ve tried this solution yet? Then we can follow up there.
|
