The most common cause of connection issues is that the connection details have been entered incorrectly or the WordPress user doesn’t have the required permissions.
Please try the suggested solutions under Troubleshooting and Connection issues below.
- Check that you definitely have the latest version of the FooEvents for WooCommerce plugin installed on your website and have the latest Event Check-ins app installed on your device
- Make sure that you enter your website URL exactly as it appears in the browser’s address bar (including either “http://” or “https://” and with or without “www”)
- Make sure that you are using your WordPress username and password to log into the app. NB: By default, only users with the role of “Administrator” in WordPress will have access to the Check-ins app. This article explains how to assign roles to different WordPress users without necessarily giving them admin access to your website: User Roles, Capabilities and Permissions
- Temporarily disable any security related plugins such as Wordfence or iThemes Security to see if they are blocking access
- If you know that you are using the XML-RPC connection fallback (instead of REST API which is preferred), please check that your xmlrpc.php file is accessible. Enter ‘www.YOURSITE.com/xmlrpc.php’ in your web browser. You should see the following message if the xmlrpc.php file is accessible: “XML-RPC server accepts POST requests only.”
- Contact your web host and ask them to do the following:
- Whitelist the rule triggered by the IP address of your mobile device
- Disable the Mod_security rule for your domain
If you still experience any connectivity issues, it’s possible that the FooEvents Check-ins apps are being permanently or temporarily blocked from connecting to your website. This might be due to a security plugin or your website hosting company blocking access.
If you have a security related plugin installed on your website such as Wordfence or iThemes Security please temporarily disable it and try sign-in to the app again. If you are able to sign-in, then the plugin was blocking access and will need to be permanently disabled or configured differently.
If you are sure that the cause of the problem is not a security plugin, please contact FooEvents Technical Support and provide as much detail as possible so we can get back to you with other possible solutions.