css processing – broken website

  • Resolved marampb

    (@marampb)


    8 years, 9 months ago

    Hello
    all worked fine till version 1.4.4
    after installation of the last 2 versions (currently use 1.4.7) of the plugin, the processing of css files, push my website down. Looks like there is an interaction in between apache (2.4) / php (7.0) and existing nginx.
    my website is installed on a virtual host on Apache, the nginx is used for the remote server administration.
    note: I completely deactivated the cache plug-ins, and removed the caches, restarted apache, cleaned the browser cache. In the logs from plugin I constantly receive the following message for each css file
    – REQUEST FAILED () – //mysite
    The pages have hard to load and finish by displaying – 504 Gateway Time-out nginx (normally Apache should handle these pages).
    I ended by selecting – deactivate the css completely.
    Should I activate additional php extensions? Something else?
    could you please help

    thanks a lot
    B

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Raul P.

    (@alignak)

    8 years, 9 months ago

    Hi and thanks for reporting.

    I think that your server might be blocking some http requests, because what you see on the “view log” button as – REQUEST FAILED – has been requested by the wordpress api to your site.

    Now this can happen if the url is wrong or if the server is blocking the requests somewhere. If only a few have the – REQUEST FAILED – that could be a rate limit or something else.

    Can you post the complete contents of that failed log files or a screenshot please?

    Thread Starter marampb

    (@marampb)

    8 years, 9 months ago

    Hi Raul
    thanks a lot for your answer.
    i apologise. On my first contact i forgot to thank you for this “best in class plugin”
    despite the problem i have since the version 1.4.5, I remain convinced it is one of the best i ever seen! 🙂

    These are the logs reported in the plugin. (i replaced my domain name and the port). if needed i can share this information with you offline.
    —————————————
    fvmcss-022bd250c026a013a-1493849831.min.css

    – REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/dashicons.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/admin-bar.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/responsive-cookie-consent/includes/css/style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/static/libs/font-awesome/css/font-awesome.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/static/libs/qtip/css/jquery.qtip.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/extensions/feedback/extensions/feedback-stars/static/css/styles.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/bootstrap.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/jquery.mmenu.all.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/uploads/the-core-style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-child/style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/prettyPhoto.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/animate.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/extensions/shortcodes/shortcodes/section/static/css/background.css
    – FROM CACHE: //fonts.googleapis.com/css?family=Raleway:700,300,100,100italic|Martel+Sans:200,regular|Crimson+Text:regular|Open+Sans:300,300italic&subset=latin,latin-ext,devanagari

    fvmcss-0d3be1db5026a013a-1493849831.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/dashicons.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/admin-bar.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/responsive-cookie-consent/includes/css/style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/static/libs/font-awesome/css/font-awesome.min.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/bootstrap.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/jquery.mmenu.all.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/uploads/the-core-style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-child/style.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/prettyPhoto.css
    – REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/animate.css
    – FROM CACHE: //fonts.googleapis.com/css?family=Raleway:700,300,100,100italic|Martel+Sans:200,regular|Crimson+Text:regular|Open+Sans:300,300italic&subset=latin,latin-ext,devanagari
    —————————–

    status of the different toggles:
    ON: Use the default dynamic “//” protocol
    OFF: Force HTTP urls [ needed for the CDN Enabler plugin ]
    OFF: Force HTTPS urls [ needed for the CDN Enabler plugin ]

    HTML Options
    HTML Options
    OFF Disable minification on HTML
    OFF Strip HTML comments
    OFF Fonts Options

    CSS Options
    OFF (when on site broken) CSS Options Disable CSS processing
    ON Disable minification on CSS files
    ON Inline all enqueued CSS

    JavaScript Options
    OFF Disable JavaScript processing
    OFF Skip minification on JS files

    ————–advances

    Render-blocking JS
    ON Render-blocking Enable defer parsing of JS files
    ON Enable defer of JS for Pagespeed Insights
    ON Skip defer of JS for the jQuery library
    OFF Load CSS asynchronously with loadCSS and rel=”preload”

    exclusions:
    /wp-includes/js/jquery/jquery.js
    /wp-includes/js/admin-bar.min.js
    /wp-includes/js/jquery/jquery-migrate.min.js
    /wp-includes/js/jquery/ui/effect.min.js
    /wp-includes/js/wp-embed.min.js
    /wp-content/themes/the-core-parent/js/

    preconnect headers:
    //fonts.googleapis.com/
    //fonts.gstatic.com

    on server side:
    virtual port based on port
    HTTP
    HTTPS 9433
    root — myfolder
    HSTS on
    HTTP/2 on
    main server – apache 2.4
    main php – 7.0

    the message reported on the browser is 504 Gateway Time-out nginx

    note: my site is intended to work on https. i added a plugin which replace widely the http or https with // this for avoiding having mixed content problems.
    i didn’t check – if you think useful i can deactivate it, and force here the https, and also to rewrite this part of the .htaccess

    additional information – my dev website is hosted on a synology system (this is why the combination of different web servers) and the server is in prod. the dev website is on the virtual host in purpose, before it is migrated to a new hosting.

    thanks a lot
    B

    Thread Starter marampb

    (@marampb)

    8 years, 9 months ago

    Hello Raul

    just did a quick check to the plugin – WP Async CSS – created by Robert Sæther.
    I saw a mention of this plugin in one of your recent discussions, on the version 1.4.4 asking you to implement this 😉
    The behaviour is exactly the same (nginx gateway error).
    It looks like my website “does not appreciate” the functions included. Maybe there are somme commonalities in processing the css in between that plugin any fast velocity?…
    Is there any incompatibility with Apache 2.4/php7 of that supposed feature.

    thanks in advance
    best regards,
    B

    Plugin Author Raul P.

    (@alignak)

    8 years, 9 months ago

    I think I may have a solution for you shortly, hold on.

    Thread Starter marampb

    (@marampb)

    8 years, 9 months ago

    Thanks a lot 🙂
    maybe a “switch” in between using the “old” techno and “new” techno for CSS ?
    could be nice.
    info – i already tried the version 1.4.7.1 – with no success.

    thanks
    B

    Plugin Author Raul P.

    (@alignak)

    8 years, 9 months ago

    Hi, can you try version 1.4.8 and tell me if it fixed it for you?

    It seems to be requesting from //fonts.googleapis.com/ just fine, but not from //myFQDN:myPort/…

    I’m not sure if it’s because your url has a port number, if it’s because the url is incorrect, ssl fails, or if it’s getting it from the live site where the files do not exist… but we will get there if you like.

    For now, try 1.4.8 it should work on css at least.

    Thread Starter marampb

    (@marampb)

    8 years, 9 months ago

    Yes Sir!

    Perfect 🙂 now it is working !
    There are some css not correctly loading in frontend as “planned”, but this is normal.
    I will exclude them on the proposed list 🙂

    really Great! This is a 5 star plugin!
    your support is best in class. I also really appreciate the “pro” clean implementation, and the missing advertising/add-ons or hard pushing by any mean for buying something.

    All my best regards and success for the new devlopments!
    B

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘css processing – broken website’ is closed to new replies.