• Resolved thecatholicwire

    (@thecatholicwire)


    Hi!

    I have been annoying myself with this for hours.

    I am trying to set up a Podbean podcast to upload posts into a wordpress hosted website, created with Elementor (not that that last makes any difference I think).
    I tried following the instructions here:
    https://help.podbean.com/support/solutions/articles/25000005113-setting-up-my-podbean-podcasts-to-automatically-post-to-my-wordpress-site
    I have realized that now the application password is embedded into wordpress so I tried not installing the plugin and just using it as it comes with wordpress.
    I get the following error:
    “Error: WordPress API connection failed , api response : Unknown username. Check again or try your email address.(invalid_username)”
    I also got this error in other attempts:
    “Error: WordPress API connection failed , api response : Sorry, you are not allowed to do that.(rest_forbidden)”

    I have tried creating the user in many different ways, with different users, etc… There must be something I am not doing, but haven’t found anything online….

    I recently went and took a big risk, and modified the htaccess. Now, it looks like this:

    # BEGIN WordPress
    # The directives (lines) between "BEGIN WordPress" and "END WordPress" are
    # dynamically generated, and should only be modified via WordPress filters.
    # Any changes to the directives between these markers will be overwritten.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization}]   
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    I added this line to the Original
    RewriteRule .* – [E=REMOTE_USER:%{HTTP:Authorization}]

    Still not working.

    Help please!!!!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter thecatholicwire

    (@thecatholicwire)

    Update: I realize The user that one uses in to log in must be an admin, otherwise it won’t let it connect remotely through the API to create posts.

    Anyway we can change this, so I can allow non-admin users to connect via API from podbean, to create new Posts automatically?

    Help!!! Thanks

    HI!!! I have been struggling with this same issue and finally got it to connect, so thought I should share. Podbean tells you to use the username that you create when creating the Application Password. Their example is “Podbean” or whatever you decide to name it. However, I just got the API to connect when I used the ACTUAL username and the password generated from Applications Password. That connected… hope this helps!

    Thread Starter thecatholicwire

    (@thecatholicwire)

    Yes, indeed that’s what needs to be done.

    You must use the REAL user name and the password given for the Applications Password.

    Thank you!

    Hey guys,

    I’m also having this issue. Pretty sure I have the correct username (just using the username from the account)

    Any help would be appreciated. I have also contacted podbean.

    Thread Starter thecatholicwire

    (@thecatholicwire)

    The answers above supply the solution.
    The user must be an Administrator (I believe).
    You have to use the REAL User Name. (Not the one created for the application password)
    But the Password from Application Password.

    That’s what worked for me. Couldn’t get around it.

    Ok I figured it out. I had another application password plug in, that I had to deactivate because wordpress made it part of the new update.

    Then I had to deactivate the cache plug in I had.

    And yes, I had to use my own username, not the ‘podbean’ username as they said in their documentation.

    Spent alot of time on this one.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Application Password for Podbean not working’ is closed to new replies.