{"id":482,"date":"2019-11-01T07:46:45","date_gmt":"2019-11-01T07:46:45","guid":{"rendered":"https:\/\/help.foosales.com\/docs\/frequently-asked-questions\/setup\/im-having-trouble-logging-into-foosales\/"},"modified":"2024-11-27T09:57:16","modified_gmt":"2024-11-27T16:57:16","slug":"mam-potize-s-prihlasenim-do-foosales","status":"publish","type":"docs","link":"https:\/\/help.foosales.com\/cs\/docs\/frequently-asked-questions\/setup\/im-having-trouble-logging-into-foosales\/","title":{"rendered":"M\u00e1m pot\u00ed\u017ee s p\u0159ihl\u00e1\u0161en\u00edm do FooSales?"},"content":{"rendered":"

Common Issues:<\/h3>\n
    \n
  1. Have you installed and activated the FooSales WordPress plugin?<\/a><\/li>\n
  2. Was your URL entered correctly?<\/a><\/li>\n
  3. Did you enter the correct username and password?<\/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. Have you installed and activated the FooSales WordPress plugin?<\/h3>\n

    The FooSales WordPress plugin<\/a> needs to first be installed on your web store and remain activated<\/em> in order to login to the FooSales POS apps.<\/p>\n

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

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

    \"\"<\/p>\n

      \n
    1. Did you specify the correct protocol (including https:\/\/<\/strong>)?<\/li>\n
    2. Does your website URL start with ‘www<\/strong>‘ or does it exclude<\/em> ‘www<\/strong>‘?<\/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 WordPress admin area<\/strong>.
      \nGo to Settings<\/strong> > General<\/strong> > WordPress Address (URL)<\/strong><\/p>\n

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

      FooSales uses the same WordPress username and password<\/strong> that you use to connect to your website. Please ensure that you entered your username and password correctly and that you did not enter your FooSales Account<\/strong> login details instead.<\/p>\n

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

      By default, access to the FooSales web and tablet apps is restricted to users with the \u201cAdministrator<\/strong>\u201d or \u201cCashier<\/strong>\u201d user roles, or\u00a0any user with \u201cpublish FooSales<\/strong>\u201d permission. You can find out more about managing user roles and permissions<\/a> using a free third-party plugin.<\/p>\n

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

      FooSales 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> related plugins such as Wordfence<\/strong> and iThemes Security<\/strong> to see if it is blocking access.<\/p>\n

      If your security plugin is blocking access to FooSales, please try adding the IP address of your tablet device to your security plugin’s whitelist\/allowlist. If you are using the FooSales web app, please add the following IP address: 188.40.1.115<\/em><\/strong><\/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 CAPTCHA<\/em> plugin, please ensure that CAPTCHA is not applied to WordPress logins.<\/p>\n

      If you are using the Advanced noCaptcha & invisible captcha Settings<\/strong> plugin, you can disable CAPTCHA on the login form via the plugins settings. Login to your WordPress admin area<\/strong>, go to Settings<\/strong> > Advanced noCaptcha & invisible captcha Settings<\/strong> > Enabled Forms<\/strong> > Login Form<\/strong> and ensure Login Form<\/strong> is not checked.<\/p>\n

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

      Make sure that your website’s REST API<\/strong> is accessible by entering the following address in your web browser: ‘www.YOURWEBSITE.com\/wp-json\/foosales\/v4’<\/span><\/p>\n

      You should see a screen that displays code which starts with {\"namespace\":\"foosales\\\/v4\",\"routes\":<\/code> as opposed to an error page such as 404 file not found<\/em> which indicates that something is wrong with your server configuration or the REST API<\/strong> is blocked.<\/span><\/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 FooSales 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 is not accessible, the app will try to connect using the less preferred XML-RPC<\/strong> connection. Ask your hosting company to confirm that there are no security restrictions on the \u2018xmlrpc.php\u2019 file which is part of WordPress and advise if the IP address of your device has been blocked from connecting to your site<\/p>\n

      If you still experience issues, please contact FooSales Technical Support<\/span><\/a> and include as much detail as possible so we can get back to you with other possible solutions.<\/span><\/p>\n

      8. Is your site installed in a subdirectory of another WordPress site?<\/h3>\n

      If your site is installed in a subdirectory of another WordPress site, then the .htaccess files of your subdirectory might cause permalinks conflict, making the REST API inaccessible.<\/p>\n

      Example:<\/strong><\/p>\n

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