Several issues (cURL error 28, Ads, /amp/, …)

  • Resolved JeRetiens

    (@jeretiens)


    4 years, 5 months ago

    Hello,

    I changed my theme and my AMP plugin and I encounter several issues.

    Some background here: I was on Publisher by BetterStudio and BetterAMP. The AMP plugin generated amp pages located at mysite/my-page-name/amp. It basically added /amp/ after every post/page URL.

    I changed to Generatepress, and I’ve understood the developper made a plugin (amp-for-generatepress) available on Github which works with AMP for WP.
    So, I integrated your plugin on my website.

    First issue is I encounter this error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed) ?

    This error appears after the activation of the Standard or Transitional mode AND when I try to “review the validation errors”. Nothing is shown but this error.
    It might be a server issue, I don’t know, I’m hosted on OVH with an heavy plan to support my traffic.

    Second issue is my ADS totally disappeared from my website (there were inserted manually, I don’t want to use a plugin for it… and there were managed automatically by Google Ad Sense on mobile).

    Third issue, is all the /amp/ old urls… What can I do with them ? Is it a 301 redirect rule able to tell something like “all the /amp/ points to its related article without /amp/ url” ?

    Thanks a lot for your concern and your enlightment !

    If needed, my website is located here: https://jeretiens.net

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter JeRetiens

    (@jeretiens)

    I had to find a solution, I desactivated AMP for good and found this .htaccess rule to redirect old /amp/ pages to parent posts.

    RewriteEngine On 
RewriteCond %{REQUEST_URI} (.+)/amp(.*)$ 
RewriteRule ^ %1/ [R=301,L]

    I put it here for the people interested.

    @jeretiens Thanks for sharing your info. If you plan to revisit AMP once again I would suggest setting up a staging environment, and we can then assist with any of these errors you’ve been encountering.

    For the issues you did encounter you’ll also find some useful previous support topics that answer most of your queries, such as the cURL error 28.

    For ads you’ll need to implement AMP ads for AMP URLs. If they worked previously for AMP URLs it may have been an ads plugin that converted traditional ads into AMP ads.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Several issues (cURL error 28, Ads, /amp/, …)’ is closed to new replies.