jbarker2018

Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Forum: Plugins
    In reply to: [Cloudflare] Blank Settings Page
    Thread Starter jbarker2018

    (@jbarker2018)

    8 years, 5 months ago

    That did the trick on the new website.

    Summary: Windows Server 2008 R2 is using an older version of MIME for .js and needs changed to : application/javascript

    This is found by opening IIS. Selecting the server name in the left hand window. Clicking on MIME types on the right hand pane. Scroll down until you see: .js

    Then modify to: application/javascript

    I restarted IIS service afterwards.

    The setting screen immediately appeared.

    The older website still has an issue, but at this point I assume its a conflict with another plugin. I can use the CF online dashboard to manage easy enough.

    Forum: Plugins
    In reply to: [Cloudflare] Blank Settings Page
    Thread Starter jbarker2018

    (@jbarker2018)

    8 years, 5 months ago

    do you think i should add a second entry to modify to application/javascript (if you even can) or change the existing mime type?

    That setting is whatever the default in this version of IIS was set to?

    Thanks for the help. Getting there!

    Forum: Plugins
    In reply to: [Cloudflare] Blank Settings Page
    Thread Starter jbarker2018

    (@jbarker2018)

    8 years, 5 months ago

    The link you posted on 406 was actually the one I was reading earlier. But thanks for posting.

    Forum: Plugins
    In reply to: [Cloudflare] Blank Settings Page
    Thread Starter jbarker2018

    (@jbarker2018)

    8 years, 5 months ago

    No. this is actually IIS on a Server 2008 R2 Machine.

    The old website has a ton of .js fetches with other plugins that work correctly.

    I double checked the mime types for .js on the IIS server.

    It is there with MIME Type:

    application/x-javascript

    Forum: Plugins
    In reply to: [Cloudflare] Blank Settings Page
    Thread Starter jbarker2018

    (@jbarker2018)

    8 years, 5 months ago

    Thanks for responding. I completely forgot about developer mode in the browser. I am more network engineer side. But getting better in dev.

    I have tried both Chrome and Firefox and get the same error in both developer consoles:

    406 Not Acceptable
    Config_Fetch_Error

    I have verified the same error on both websites. The brand new one with zero info or plugins other than cloudflare and the older website that used to view the settings page.

    The brand new website just stops after the config_fetch_error

    I have searched the forums for cloudflare 406 error and I don’t see anything that I think is relevant. One post was a conflicting security plugin, which on the new website doesn’t apply. Another post had an improperly configured DNS which I know is wrong on the old website since its working as expected.

    I’ll do some more digging on the 406 error. Its not one I am familiar with.

    Log files are below.

    Brand new website:
    GET http://www.newwebsite.io/wp-content/plugins/cloudflare/config.js?ver=3.3.1 406 (Not Acceptable)
    (anonymous) @ VM129:1
    d.end @ compiled.js?ver=3.3.1:35
    o @ compiled.js?ver=3.3.1:35
    i @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    dispatch @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    value @ compiled.js?ver=3.3.1:35
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    a @ compiled.js?ver=3.3.1:30
    perform @ compiled.js?ver=3.3.1:6
    u @ compiled.js?ver=3.3.1:30
    perform @ compiled.js?ver=3.3.1:6
    batchedUpdates @ compiled.js?ver=3.3.1:35
    i @ compiled.js?ver=3.3.1:6
    _renderNewRootComponent @ compiled.js?ver=3.3.1:30
    _renderSubtreeIntoContainer @ compiled.js?ver=3.3.1:30
    render @ compiled.js?ver=3.3.1:30
    (anonymous) @ compiled.js?ver=3.3.1:35
    t @ compiled.js?ver=3.3.1:1
    (anonymous) @ compiled.js?ver=3.3.1:1
    (anonymous) @ compiled.js?ver=3.3.1:1
    compiled.js?ver=3.3.1:35 action CONFIG_FETCH_ERROR @ 06:28:35.794
    compiled.js?ver=3.3.1:35 prev state {activeZone: {…}, app: {…}, config: {…}, intl: {…}, user: {…}, …}
    compiled.js?ver=3.3.1:35 action {type: “CONFIG_FETCH_ERROR”}

    The older site continues with the API key being verified as I had set it up previously.

    The older website:

    VM152:1 GET https://www.oldwebsite.com/wp-content/plugins/cloudflare/config.js?ver=3.3.1 406 (Not Acceptable)
    (anonymous) @ VM152:1
    d.end @ compiled.js?ver=3.3.1:35
    o @ compiled.js?ver=3.3.1:35
    i @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    dispatch @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    (anonymous) @ compiled.js?ver=3.3.1:35
    value @ compiled.js?ver=3.3.1:35
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    performInitialMount @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:35
    mountComponent @ compiled.js?ver=3.3.1:6
    a @ compiled.js?ver=3.3.1:30
    perform @ compiled.js?ver=3.3.1:6
    u @ compiled.js?ver=3.3.1:30
    perform @ compiled.js?ver=3.3.1:6
    batchedUpdates @ compiled.js?ver=3.3.1:35
    i @ compiled.js?ver=3.3.1:6
    _renderNewRootComponent @ compiled.js?ver=3.3.1:30
    _renderSubtreeIntoContainer @ compiled.js?ver=3.3.1:30
    render @ compiled.js?ver=3.3.1:30
    (anonymous) @ compiled.js?ver=3.3.1:35
    t @ compiled.js?ver=3.3.1:1
    (anonymous) @ compiled.js?ver=3.3.1:1
    (anonymous) @ compiled.js?ver=3.3.1:1
    compiled.js?ver=3.3.1:35 action CONFIG_FETCH_ERROR @ 06:33:35.363
    compiled.js?ver=3.3.1:35 prev state {activeZone: {…}, app: {…}, config: {…}, intl: {…}, user: {…}, …}
    compiled.js?ver=3.3.1:35 action {type: “CONFIG_FETCH_ERROR”}
    compiled.js?ver=3.3.1:35 next state {activeZone: {…}, app: {…}, config: {…}, intl: {…}, user: {…}, …}activeZone: {id: “”, name: “”}app: {isInitialized: false}config: {config: {…}, isFetching: false}intl: {locale: “”, translations: {…}, isFetching: false}notifications: []pluginSettings: {entities: {…}, result: Array(0), isFetching: “”}routing: {locationBeforeTransitions: {…}}user: {isLoggedIn: false, isFetching: false}zoneAnalytics: {entities: {…}, isFetching: false}zoneDnsRecords: {entities: {…}, result: Array(0), isFetching: false, updateIsFetching: “”}zonePurgeCache: {isFetching: false}zoneRailguns: {entities: {…}, isFetching: false}zoneSettings: {entities: {…}, result: Array(0), isFetching: “”}zones: {entities: {…}, result: {…}, zoneDeleteIsFetching: false, zoneFetchIsFetching: false, zoneProvisionCnameIsFetching: false, …}__proto__: Object
    options-general.php?page=cloudflare:823 Live Support Info : Api key verified but user is not vip.

    Forum: Plugins
    In reply to: [Cloudflare] Blank Settings Page
    Thread Starter jbarker2018

    (@jbarker2018)

    8 years, 5 months ago

    In an effort to continue troubleshooting this. I just reinstalled from scratch on the same local windows server that had Cloudflare working. Same details as before.

    Completely fresh install of wordpress 4.9.1. New database. No plugins installed except for Cloudflare. I still get the blank settings page.

    My other site that is working with cloudflare still shows a blank settings page as well.

    Any thoughts or direction would be much appreciated.

    Thanks
    John

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