{"id":974,"date":"2019-11-27T07:16:55","date_gmt":"2019-11-27T14:16:55","guid":{"rendered":"https:\/\/help.fooevents.com\/docs\/topics\/apps\/xml-rpc-connection-issues\/"},"modified":"2025-01-27T15:13:22","modified_gmt":"2025-01-27T23:13:22","slug":"connection-issues","status":"publish","type":"docs","link":"https:\/\/help.fooevents.com\/nl\/documentatie\/onderwerpen\/check-ins-app-2\/verbindingsproblemen\/","title":{"rendered":"Connection issues"},"content":{"rendered":"

Having trouble connecting the FooEvents Check-ins apps<\/a> to your store?<\/p>\n

Common Issues:<\/h3>\n
    \n
  1. Was your URL entered correctly?<\/a><\/li>\n
  2. Did you enter the correct username and password?<\/a><\/li>\n
  3. Do you have the latest plugin installed?<\/a><\/li>\n
  4. Does the WordPress user have appropriate permissions?<\/a><\/li>\n
  5. Do you have any security plugins installed?<\/a><\/li>\n
  6. Do you use a CAPTCHA plugin?<\/a><\/li>\n
  7. Is REST API accessible?<\/a><\/li>\n
  8. Is your site installed in a subdirectory of another WordPress site?<\/a><\/li>\n
  9. Do you have a WordPress.com site instead of a self-hosted WordPress site?<\/a><\/li>\n<\/ol>\n

    1. Was your URL entered correctly?<\/h3>\n

    Ensure that your website URL is entered exactly as it appears in your web browser\u2019s address bar.<\/p>\n

    \"\"<\/p>\n

      \n
    1. Did you specify the correct protocol (including\u00a0http:\/\/<\/strong>\u00a0OR\u00a0https:\/\/<\/strong>)?<\/li>\n
    2. Does your website URL start with \u2018www<\/strong>\u2018 or does it\u00a0exclude<\/em>\u00a0\u2018www<\/strong>\u2018?<\/li>\n
    3. Does your website URL have a trailing slash at the end (\/<\/strong>)?<\/li>\n<\/ol>\n

      You can find the exact URL that you need to enter in your\u00a0WordPress admin area<\/strong>.
      \nGo to\u00a0Settings<\/strong>\u00a0>\u00a0General<\/strong>\u00a0>\u00a0WordPress Address (URL)<\/strong><\/p>\n

      2. Did you enter the correct username and password?<\/h3>\n

      The FooEvents Check-ins apps use the same WordPress username and password<\/strong> that you use to log in to your website. Please ensure that you entered your username and password correctly and that you did not enter your FooEvents Account<\/strong>\u00a0login details instead.<\/p>\n

      3. Do you have the latest plugin installed?<\/h3>\n

      Check that you definitely have the\u00a0latest version<\/a>\u00a0of the\u00a0FooEvents for WooCommerce plugin<\/strong>\u00a0installed on your website and the latest\u00a0FooEvents Check-ins<\/strong>\u00a0app\u00a0installed on your device<\/p>\n

      4. Does the WordPress user have appropriate permissions?<\/h3>\n

      By default, only users with the role of \u201cAdministrator<\/strong>\u201d 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:\u00a0User Roles, Capabilities and Permissions<\/a><\/p>\n

      5. Do you have any security plugins installed?<\/h3>\n

      FooEvents uses an API to connect to your WordPress site. It is very possible that your security plugin is blocking API access to your site. To test if this is the case, temporarily disable any security<\/em>\u00a0related plugins such as\u00a0Wordfence<\/strong>\u00a0and\u00a0iThemes Security<\/strong>\u00a0to see if it is blocking access.<\/p>\n

      If your security plugin is blocking access to FooEvents, please try whitelisting the IP address of your tablet device.<\/p>\n

      If you are still experiencing problems, please also make sure that two-factor authentication (2FA)<\/strong> is not enabled.<\/p>\n

      6. Do you use a CAPTCHA plugin?<\/h3>\n

      If you are using a\u00a0CAPTCHA<\/em>\u00a0plugin, please ensure that CAPTCHA is not applied to WordPress logins.<\/p>\n

      If you are using the\u00a0Advanced noCaptcha & invisible captcha Settings<\/strong>\u00a0plugin, you can disable CAPTCHA on the login form via the plugins settings. Login to your\u00a0WordPress admin area<\/strong>, go to\u00a0Settings<\/strong>\u00a0>\u00a0Advanced noCaptcha & invisible captcha Settings<\/strong>\u00a0>\u00a0Enabled Forms<\/strong>\u00a0>\u00a0Login Form<\/strong>\u00a0and ensure\u00a0Login Form<\/strong>\u00a0is not checked.<\/p>\n

      7. Is REST API accessible?<\/h3>\n

      Make sure that your website\u2019s\u00a0REST API<\/strong> is accessible by entering the following address in your web browser: \u2018www.yourwebsite.com\/wp-json\/fooevents\/v1\u2019<\/p>\n

      You should see a screen that displays code which starts with\u00a0{\"namespace\":\"fooevents\\\/v1\",\"routes\":<\/code>\u00a0as opposed to an error page such as\u00a0404 file not found<\/em>\u00a0which indicates that something is wrong with your server configuration or the\u00a0REST API<\/strong>\u00a0is blocked.<\/p>\n

      If you are using the “Plain” permalink structure please consider one of the other options instead. The “Plain” permalink structure uses a different REST API path which the Check-ins app does not currently support. You can change this setting if you go to Settings > Permalinks<\/b> and choose e.g. “Post name” instead.<\/p>\n

      If the REST API<\/strong> is not accessible and the app tries to fallback to the less preferred XML-RPC<\/strong> connection, please check that your xmlrpc.php file is accessible<\/strong>. Enter \u2018www.YOURSITE.com\/xmlrpc.php\u2019 in your web browser. You should see the following message if the xmlrpc.php file is accessible: \u201cXML-RPC server accepts POST requests only.\u201d<\/p>\n

      Please also contact your web host and ask them to do the following:<\/p>\n

      If you site is installed in the subfolder of another WordPress site, please proceed to\u00a0section #8<\/a>.<\/strong><\/p>\n