Instapy: WARNING [2019-08-18 13:19:18] [***] --> Couldn't follow '***'! ~user is inaccessible

Created on 18 Aug 2019  路  9Comments  路  Source: timgrossmann/InstaPy


Expected Behavior

follow the user

Current Behavior

WARNING [2019-08-18 13:19:18] [dino.runs] --> Couldn't follow '*'! ~user is inaccessible

InstaPy configuration

    session.set_do_follow(enabled=True, percentage=15, times=1)
    session.set_do_comment(enabled=True, percentage=75)
    session.set_comments([
 'Awesome!',
 'Really cool',
 'Nice !',
 'Great !',
 'Leuk !',
 'I like your stuff',
 'very nice pictures'])
    session.like_by_tags(['***','***','***','***','***','***','***','swimbikerun'], amount=50)
    session.set_do_like(enabled=True, percentage=75)

This part is correct right?

wontfix

Most helpful comment

To anybody still having this issue on 6.1
Its caused by a typo in the file xpath_compile.py

Line 83 "follow_button_XP": "(//button)[2][text()='Following' or \

It looks like this ^^^

It needs to look like this

Line 83 "follow_button_XP": "//button[text()='Following' or \

That will fix it.

All 9 comments

Don't know but I guess:

  1. You have been blocked
  2. Or the account changed its name while InstaPy was running
  3. Or internet connection/chrome/instagram failed

Can you check these options?


How was the warning generated:


def is_page_available(browser, logger):
    """ Check if the page is available and valid """
    expected_keywords = ["Page Not Found", "Content Unavailable"]
    page_title = get_page_title(browser, logger)

    if any(keyword in page_title for keyword in expected_keywords):
        reload_webpage(browser)
        page_title = get_page_title(browser, logger)

        if any(keyword in page_title for keyword in expected_keywords):
            if "Page Not Found" in page_title:
                logger.warning(
                    "The page isn't available!\t~the link may be broken, "
                    "or the page may have been removed..."
                )

            elif "Content Unavailable" in page_title:
                logger.warning(
                    "The page isn't available!\t~the user may have blocked " "you..."
                )

            return False

    return True

# check if the page is available
    valid_page = is_page_available(browser, logger)
    if not valid_page:
        logger.warning(user_inaccessible_msg)
        person_new = verify_username_by_id(
            browser, username, person, None, logger, logfolder
        )
        if person_new:
            web_address_navigator(browser, ig_homepage + person_new)
            valid_page = is_page_available(browser, logger)
            if not valid_page:
                logger.error(failure_msg.format(person_new.encode("utf-8")))
                return "UNAVAILABLE", None

        else:
            logger.error(failure_msg.format(person.encode("utf-8")))
            return "UNAVAILABLE", None



        elif following_status in ["Unblock", "UNAVAILABLE"]:
            if following_status == "Unblock":
                failure_msg = "user is in block"

            elif following_status == "UNAVAILABLE":
                failure_msg = "user is inaccessible"

            logger.warning(
                "--> Couldn't follow '{}'!\t~{}".format(user_name, failure_msg)

It鈥檚 none of both.

I can still follow with this :
session.follow_user_followers(['xxx','xxx','xxx','xxx'], amount=3, randomize=True, interact=False)

And the link is the same because I can click on it and then I see my like / comment

To anybody still having this issue on 6.1
Its caused by a typo in the file xpath_compile.py

Line 83 "follow_button_XP": "(//button)[2][text()='Following' or \

It looks like this ^^^

It needs to look like this

Line 83 "follow_button_XP": "//button[text()='Following' or \

That will fix it.

Excellent contribution @Mr-HaleYa again as always. thank you!!

It was already like this in version 0.6.2 but still same problem ...

I'm still having this issue with unfollowing....

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this problem still occurs, please open a new issue

The problem is still there

@siddhantchimankar The problem most likely will never be fixed since this project is dying...

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ghost picture ghost  路  3Comments

v77v picture v77v  路  3Comments

tibor picture tibor  路  3Comments

thisishotdog picture thisishotdog  路  3Comments

converge picture converge  路  3Comments