Cloudflare & BigCommerce CLI Development Environment Problem


We are using BigCommerce as our eCommerce platform and Cloudflare worker processes to handle redirecting traffic from our previous site to the new BC sites.

When we try to run the BigCommerce CLI development environment with traffic passing through Cloudflare we get a server 500 error reported by BigCommerce.

If we set Cloudflare to be DNS only and flush the cache the problem goes away.

I have tried running CF in Development Mode and flushing the cache but this doesn’t fix the problem.

The only work around is to turn CF off and use it solely as a DNS but this is no good for us because we need the worker processes to be in play.

Does anybody know why CF causes this problem with BigCommerce and what a solution might be?
I’ve pasted the error reported by the BigCommerce CLI below in case that helps. I appreciate that this may be a BigCommerce issue but clearly something CF is doing is affecting BC and any guidance on what this might be would be extremely helpful.

Many thanks,

Debug: internal, implementation, error

  • Error: Error: The BigCommerce server responded with a 500 error*
  • at C:\Users\Andrew\AppData\Roaming\nvm\v10.16.3\node_modules@bigcommerce\stencil-cli\server\plugins\renderer\renderer.module.js:45:31*
  • at C:\Users\Andrew\AppData\Roaming\nvm\v10.16.3\node_modules@bigcommerce\stencil-cli\server\plugins\renderer\renderer.module.js:134:20*
  • at finish (C:\Users\Andrew\AppData\Roaming\nvm\v10.16.3\node_modules@bigcommerce\stencil-cli\node_modules\wreck\lib\index.js:249:20)*
  • at wrapped (C:\Users\Andrew\AppData\Roaming\nvm\v10.16.3\node_modules@bigcommerce\stencil-cli\node_modules\wreck\node_modules\hoek\lib\index.js:879:20)*
  • at ClientRequest.onResponse (C:\Users\Andrew\AppData\Roaming\nvm\v10.16.3\node_modules@bigcommerce\stencil-cli\node_modules\wreck\lib\index.js:200:20)*
  • at Object.onceWrapper (events.js:286:20)*
  • at ClientRequest.emit (events.js:198:13)*
  • at ClientRequest.EventEmitter.emit (domain.js:466:23)*
  • at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:556:21)*
  • at HTTPParser.parserOnHeadersComplete (_http_common.js:109:17)*
  • at TLSSocket.socketOnData (_http_client.js:442:20)*
  • at TLSSocket.emit (events.js:198:13)*
  • at TLSSocket.EventEmitter.emit (domain.js:466:23)*
  • at addChunk (_stream_readable.js:288:12)*
  • at readableAddChunk (_stream_readable.js:269:11)*
  • at TLSSocket.Readable.push (_stream_readable.js:224:10)*

That won’t be Cloudflare. That will be your server when requests come from Cloudflare’s datacentres. You should check out your error log and why it returns that 500. Typically this is because the host blocks or rate limits Cloudflare. Only your host can fix that.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.