Incompatibility issue or something else

  • Resolved Rajat Singh

    (@couponzania)


    4 months, 2 weeks ago

    hey team,

    i am on wpx hosting and tried to setup breeze and noticed some problems.

    1. Local analytics – Local Analytics never even worked, the request kept generating through googles server and the file was never generated under uploads/breeze as mentioned on the site.
    2. local fonts – even local fonts did not work, it somehow detected incorrect font – I beleive it took the fonts at the wp-admin section and not which were running on the frontend – I tried reloading the pages where I used poppins which is the correct font for us. This never worked.
    3. Varnish – Wpx hosting uses varnish and I personally used plugins that let clear varnish cache – they even have article on how to cache varnish using these. Just google “WPX CDN — Remote Cache Invalidation” – in this doc it says to use the ip with the port 127.0.0.1:6081 and your plugin does not allow adding 6081 so I did it via the php file of your plugin but it still did not work.

    please help fix this. The performance was awesome but these challenges happened.

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

Viewing 1 replies (of 1 total)
  • Plugin Author owaisalam

    (@owaisalam)

    4 months, 2 weeks ago

    Breeze’s Local Analytics feature currently relies on specific file system permissions to generate the local gtag.js file under the /uploads/breeze/ directory. It appears WPX’s file permission or caching system may be preventing file creation.

    To clarify — WPX Hosting doesn’t actually use a traditional Varnish caching layer. They use their own proprietary system called WPX Cloud CDN, which handles caching and invalidation differently. The guide you mentioned (WPX CDN — Remote Cache Invalidation) refers to internal cache management within WPX’s system and not an exposed Varnish service in the same way other hosts (like Cloudways) do.

    That’s why adding the 127.0.0.1:6081 port in Breeze doesn’t take effect — the WPX cache isn’t a standard Varnish endpoint accessible to Breeze.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.