Support » Plugin: WooCommerce » Woocommerce IPN url not accepted by Paypal

  • I am trying to get Paypal Standard working with WooCommerce. I followed the instructions given and put the url

    into the IPN settings section of my PayPal account. I get the error message:

    We're sorry. That URL won't work. Please enter an “https” URL.

    Does this mean I need an SSL now? How do I solve this?

    ### WordPress Environment ###
    Home URL:
    Site URL:
    WC Version: 2.5.5
    Log Directory Writable: ✔
    WP Version: 4.4.2
    WP Multisite: –
    WP Memory Limit: 256 MB
    WP Debug Mode: –
    Language: en_GB
    ### Server Environment ###
    Server Info: Apache
    PHP Version: 5.4.45
    PHP Post Max Size: 40 MB
    PHP Time Limit: 30
    PHP Max Input Vars: 1000
    SUHOSIN Installed: ✔
    MySQL Version: 5.6.29
    Max Upload Size: 32 MB
    Default Timezone is UTC: ✔
    fsockopen/cURL: ✔
    SoapClient: ✔
    DOMDocument: ✔
    GZip: ✔
    Multibyte String: ✔
    Remote Post: ✔
    Remote Get: ✕ wp_remote_get() failed. The WooCommerce plugin updater won't work with your server. Contact your hosting provider. Error: name lookup timed out
    ### Database ###
    WC Database Version: 2.5.5
    woocommerce_sessions: ✔
    woocommerce_api_keys: ✔
    woocommerce_attribute_taxonomies: ✔
    woocommerce_termmeta: ✔
    woocommerce_downloadable_product_permissions: ✔
    woocommerce_order_items: ✔
    woocommerce_order_itemmeta: ✔
    woocommerce_tax_rates: ✔
    woocommerce_tax_rate_locations: ✔
    ### Active Plugins (26) ###
    Admin Menu Editor: by Janis Elsts – 1.5
    Cimy User Manager: by Marco Cimmino – 1.5.0
    Display Widgets: by Strategy11 – 2.05
    Download Monitor: by Never5 – 1.9.1
    Formidable: by Strategy11 – 2.0.24
    Google Analytics by Yoast: by Team Yoast – 5.4.6
    IM8 Exclude Pages: by intermedi8
    ipm-frommen – 2.7
    LearnDash Pro Panel: by LearnDash – 1.5.4
    LearnDash Course Grid: by LearnDash – 1.1
    LearnDash WooCommerce Integration: by LearnDash – 1.3.2
    Meta Slider: by Matcha Labs – 3.3.6
    Nav Menu Roles: by Kathy Darling – 1.7.9
    PDF Embedder Premium Secure: by Dan Lester – 2.5.1
    Post Types Order: by Nsp Code – 1.8.6
    Reveal IDs: by Oliver Schlöbe –
    LearnDash LMS: by LearnDash – 2.2.0
    Page Builder by SiteOrigin: by SiteOrigin – 2.3.2
    Theme My Login: by Jeff Farthing – 6.4.4
    User Role Editor: by Vladimir Garagulya – 4.24
    WooCommerce - Autocomplete Orders: by Serious Plugins – 1.1.3
    WooCommerce: by WooThemes – 2.5.5
    Word Stats: by Fran Ontanaya – 4.5.1
    WP Clone by WP Academy: by WP Academy – 2.2.2
    WP Maintenance Mode: by Designmodo – 2.0.3
    Weather Underground: by Katz Web Services
    Inc. – 2.1.1
    MailPoet Newsletters: by MailPoet – 2.7.1
    ### Settings ###
    Force SSL: –
    Currency: AUD ($)
    Currency Position: left
    Thousand Separator: ,
    Decimal Separator: .
    Number of Decimals: 2
    ### API ###
    API Enabled: ✔
    API Version: 3.1.0
    ### WC Pages ###
    Shop Base: #630 - /shop/
    Basket: #632 - /basket/
    Checkout: #634 - /checkout/
    My Account: #636 - /my-account/
    ### Taxonomies ###
    Product Types: course (course)
    external (external)
    grouped (grouped)
    simple (simple)
    variable (variable)
    ### Theme ###
    Name: i-excel
    Version: 1.1.6
    Author URL:
    Child Theme: ✕ – If you're modifying WooCommerce on a parent theme you didn't build personally
    then we recommend using a child theme. See: How to create a child theme
    WooCommerce Support: ✔
    ### Templates ###
    Overrides: i-excel/woocommerce/global/quantity-input.php

Viewing 8 replies - 16 through 23 (of 23 total)
  • Hi Marcus (@netweblogic), the notify_url will have to be HTTPS in future. The return parameter does not need to be HTTPS. Do you agree with this or are you saying something different?



    NetWebLogic Support

    @realredranger, I think I’m saying the same for both notify_url and return parameter NOT having to be HTTPS. I’m not sure what you mean specifically by return paramenter, but if you mean the URL you put into your IPN settings, it’s essentially the same as notify_url.

    What does need to be HTTPS is the call to when your server receives an IPN call and needs to check back with PayPal to make sure it’s valid. This is something the plugin (in this case WooCommerce) should deal with and you don’t need to worry about.

    Hi Marcus, I do not think your information is correct as according to PayPal ( you will need to HTTPS for IPN from 30th June 2017.

    This means the notify_url parameter has to be an HTTPS address for IPN.

    The “return” parameter in the form is a different address. It is the actual page the user is returned to after making payment. I use PDT on this page. It does not have to be HTTPS.

    I should add I’m not using WooCommerce or WordPress, I built a custom made website that integrates with PayPal. I must have ended up on this forum just because of this specific issue with HTTPS.



    NetWebLogic Support

    Are you sure that’s the right link? I see a list of issues, not a specific answer.

    You did mention a similar link earlier:

    On there it says what I’m saying:

    For increased security going forward, only HTTPS will be allowed for postbacks to PayPal. At this time, there is no requirement for HTTPS on the outbound IPN call from PayPal to the merchant’s IPN listener.

    Whilst this thread started about WooCommerce, it concerns any plugin using PayPal, so I think we’re still on-topic for anyone worried about these notifications coming from PayPal.

    Yeah we both posted the same link, but it won’t work if you click on it from within the email, only if you click on it from the forum website.

    I understand what you are saying now. The call to your website from PayPal (outbound IPN call) does not have to be to an HTTPS address, so I was wrong sorry. The notify_url parameter does not have to be an HTTPS address for IPN.

    The postback to PayPal will in future have to be from an HTTPS address.

    I think confusion came from my assumption that most people will be doing the postback to PayPal from the same address that receives the IPN call from PayPal. This is how my solution works, but from what you are saying, WooCommerce will do the postback to PayPal from a separate HTTPS address.

    Let me know if we are on the same page now!



    NetWebLogic Support

    Yes, that’s correct.

    You can post back to PayPal from wherever you like https or not, provided you’re posting back to an https address.

    I don’t think you worded that last reply properly? The postback to PayPal will have to be HTTPS. It’s the call to your website from PayPal (outbound IPN call) that does not have to be to an HTTPS address.



    NetWebLogic Support

    No, what I said is correct I think, I mean the same as what you just said.

    You -> PayPal = HTTPS
    PayPal -> You = Either

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Woocommerce IPN url not accepted by Paypal’ is closed to new replies.