|
AkramVignan
|
February 4, 2018 at 12:33 am
Dear support,
while loading eventespresso app we’re getting “Error Occurred – The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.
The scan already worked at my mobile in the past but as we tried yesterday, only me could scan properly, the others 3 were getting the error above. Then I deinstalled my app and installed a new version. Since there I’m now getting same error.
We’re using EE4 and current versions of the app, WP and EE4.
Thanks for your troubleshooting:
https://eventespresso.com/wiki/ee4-event-apps/#troubleshooting
This could not help. I adjusted .htaccess but it didn’t work. Refresh via permalinks either.
Could you please help? We wanted to test the app with 4 mobile phones today.
I installed application passwords for each user.
Thanks.
Best regards,
Alex
|
|
Tony
|
February 7, 2018 at 3:33 am
Hi Alex,
Which device are you using, Android or Apple?
The apps use the REST API to communicate with your server and on checking the site linked to your support license its showing a blank screen.
You can test this yourself by navigating to {your_domain}/wp-json/
It should show content but your site shows error 500 and a whitescreen.
If you check the servers error logs can you see any errors there?
Or enable WP_DEBUG using the snippet here:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
Then let us know once you have the above enabled and we can test again.
|
|
AkramVignan
|
February 9, 2018 at 3:15 pm
We’re using Apple for test. And would need to use 3-4 mobile phones. Perhapps also Android version on the event. The event is in April but we need to fix it asap for testing.
Yes, I did a retest as you said. It shows white screen. Where can I see the servers error logs?
I enabled WP_DEBUG using your snippet in wp-config.php, but I don’t get any logs into wp-content directory.
Please help further. Thanks in advance.
Alex
|
|
Josh
|
February 9, 2018 at 3:27 pm
I enabled WP_DEBUG using your snippet in wp-config.php, but I don’t get any logs into wp-content directory.
Your server may be configured to not allow adding new files there, in which case you can FTP into the server and add a blank file to the wp-content directory and give it this name: debug.log
If the file permissions allow, WP will then log errors there if WP_DEBUG and WP_DEBUG_LOG are set to true.
Sometimes a whitescreen / 500 error just means the server is running too low on memory, in which case you can try adding the following to your site’s wp-config.php file:
define( 'WP_MEMORY_LIMIT', '128M' );
|
|
AkramVignan
|
February 10, 2018 at 1:45 pm
Thanks Josh. I opened an empty file debug.log at wp-content directory. I added also the last define… statement in wp-config.
Nothing happened after I tried to open https://events.akram-vignan.de/wp-json – white page and tried to login into the app – same error. File debug.log is still empty.
Please help. Thanks.
Alex
|
|
AkramVignan
|
February 11, 2018 at 5:08 am
Do we have a possibility to use an old app version? It has already worked.
Thanks in advance.
|
|
Tony
|
February 12, 2018 at 4:00 am
The problem isn’t the app, as mentioned the app uses the REST API to access the data on your site, /wp-json/ returning error 500 is why you apps aren’t working.
Were are you adding the WP_Debug snippet on the site?
It needs to be above the line that has /* That's all, stop editing! Happy blogging. */.
WP includes define('WP_DEBUG', false); in your wp-config.php file by default, I’d recommend replacing that line with the snippet I mentioned (otherwise WP_DEBUG may not actually be enabled).
|
|
AkramVignan
|
February 12, 2018 at 1:29 pm
Great! Thanks. Now I get this error into the log:
[12-Feb-2018 20:27:45 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 92 bytes) in /var/customers/webs/Kraa0UB1/Events/wp-includes/rest-api/class-wp-rest-server.php on line 1198
|
|
AkramVignan
|
February 12, 2018 at 1:46 pm
I tried to change define( ‘WP_MEMORY_LIMIT’, ‘128M’ ); to define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); then I got following text via …/wp-json – the whole page was filled with this code. Now I changed back to 128M. Please help.
Alex
{“name”:”Akram Vignan Germany e.V. Events”,”description”:”Events von Akram Vignan Germany e.V.”,”url”:”https:\/\/events.akram-vignan.de”,”home”:”https:\/\/events.akram-vignan.de”,”gmt_offset”:1,”timezone_string”:”Europe\/Berlin”,”namespaces”:[“oembed\/1.0″,”2fa\/v1″,”contact-form-7\/v1″,”ee\/v4.8.29″,”ee\/v4.8.33″,”ee\/v4.8.34″,”ee\/v4.8.36″,”wp\/v2″],”authentication”:[],”routes”:{“\/”:{“namespace”:””,”methods”:[“GET”],”endpoints”:[{“methods”:[“GET”],”args”:{“context”:{“required”:false,”default”:”view”}}}],”_links”:{“self”:”https:\/\/events.akram-vignan.de\/wp-json\/”}},”\/oembed\/1.0″:{“namespace”:”oembed\/1.0″,”methods”:[“GET”],”endpoints”:[{“methods”:[“GET”],”args”:{“namespace”:{“required”:false,”default”:”oembed\/1.0″},”context”:{“required”:false,”default”:”view”}}}],”_links”:{“self”:”https:\/\/events.akram-vignan.de\/wp-json\/oembed\/1.0″}},”\/oembed\/1.0\/embed”:{“namespace”:”oembed\/1.0″,”methods”:[“GET”],”endpoints”:[{“methods”:[“GET”],”args”:{“url”:{“required”:true},”format”:{“required”:false,”default”:”json”},”maxwidth”:{“required”:false,”default”:600}}}],”_links”:{“self”:”https:\/\/events.akram-vignan.de\/wp-json\/oembed\/1.0\/embed”}},”\/oembed\/1.0\/proxy”:{“namespace”:”oembed\/1.0″,
|
|
Tony
|
February 12, 2018 at 2:04 pm
[12-Feb-2018 20:27:45 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 92 bytes)
Means your site is running out of memory… so you increased the memory:
I tried to change define( ‘WP_MEMORY_LIMIT’, ‘128M’ ); to define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); then I got following text via …/wp-json – the whole page was filled with this code.
Increasing the amount of available memory allowed the page to load, the code you mentioned is the correct output for that endpoint.
Now I changed back to 128M. Please help.
Meaning your site now once again does not have enough memory, why did you change it back?
134217728 bytes = roughly 138MB, which is a little on the high side but depends on multiple different factors, the number of posts on the site, various different plugins adding output to the rest api and so on. Either way right now you site needs more memory to function so you’ll need to increase the above again.
|
|
AkramVignan
|
February 13, 2018 at 12:45 pm
Now I adjusted back to 256M. Could you please help further?
|
|
AkramVignan
|
February 13, 2018 at 12:48 pm
One more error:
[13-Feb-2018 19:31:54 UTC] PHP Notice: Undefined offset: 1 in /var/customers/webs/Kraa0UB1/Events/wp-content/plugins/wp-members/inc/class-wp-members-forms.php on line 150
|
|
Josh
|
February 13, 2018 at 1:30 pm
You can turn WP_DEBUG off now (set it to false). After WP_DEBUG is deactivated, can you log into the app?
|
|
AkramVignan
|
February 14, 2018 at 3:15 pm
Thanks Josh. I switched WP_DEBUG off in wp-config.php file by setting it to false as it was before. Now I cannot login into app after even after deletion and download it once more. Same error. I saw following last error in debug.log:
[14-Feb-2018 22:05:13 UTC] PHP Notice: Undefined offset: 1 in /var/customers/webs/Kraa0UB1/Events/wp-content/plugins/wp-members/inc/class-wp-members-forms.php on line 150
|
|
Josh
|
February 14, 2018 at 3:21 pm
That’s technically not an error, it’s a PHP notice caused by the WP Members Forms plugin.
You may need to troubleshoot this further by deactivating all WP plugins (except EE) and switch to one of the default twenty* themes, then try the app again.
|
|
AkramVignan
|
February 15, 2018 at 1:35 pm
Each plugin deactivated first separately, than everything except EE deactivated, nothing helps. No I activated back plugins because we need them. I wouldn’t like to switch theme off because we have done some custom adjustments of the layout.
|
|
AkramVignan
|
February 15, 2018 at 1:48 pm
Now I switched also theme to Twenty Fifteen. Same issue. And now back to Salient.
|
|
AkramVignan
|
February 15, 2018 at 2:01 pm
I found now I did not the following for Application Passwords plugin. Perhapps it could be the issue. I don’t know where is the composer and how to use it. Please explain if needed.
Installation with composer
Assuming that you already have a working composer setup, edit your composer.json and add the following:
{
“repositories”: [
…
{
“type”: “vcs”,
“url”: “https://github.com/pelmered/application-passwords.git”
}
],
“require”: {
…
“georgestephanis/application-passwords”: “dev-master”
}
}
|
|
Josh
|
February 15, 2018 at 2:47 pm
You do not need the Applications Password plugin.
|
|
AkramVignan
|
February 17, 2018 at 9:17 am
Now I deactivated Applications Password plugin. Same error within the app.
|
|
Josh
|
February 19, 2018 at 10:24 am
May I ask what is the exact URL that’s being input into the app’s URL field when you try to log in?
|
|
Tony
|
February 21, 2018 at 2:10 am
Please remove /wp-admin/ from the URL, the app requests the Website URL rather than the wp-admin URL so it wont work with the above.
Just events.akram-vignan.de should work fine, the app should work out if it’s HTTP or HTTPS for you.
|
|
AkramVignan
|
February 21, 2018 at 3:42 pm
Thanks! Finally its solved at my mobile phone! Thank you very much. We’ll test on other mobiles whether it works in parallell.
Best Regards,
Alex
|
|
Tony
|
February 22, 2018 at 1:42 am
You’re most welcome, please do let us know if you still run into problems.
|
