This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Bad response 301 #62
Description
I have a bad response 301 error on the getImage() function
This cloud function was running fine for months.
{ Error: Bad response status code 301
at ClientRequest.handleResponse (/srv/node_modules/plotly/index.js:237:25)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at ClientRequest.emit (events.js:211:7)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:552:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:119:17)
at TLSSocket.socketOnData (_http_client.js:454:20)
at emitOne (events.js:116:13)
at TLSSocket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12) msg: undefined }
I have not changed anything in my code base.
Is there some type of service outage?
Activity
nicolaskruchten commentedon Mar 31, 2020
We have recently changed the domain name of Chart Studio Cloud from
plot.lytochart-studio.plotly.com, and it looks like this library does not accept the redirection requests... I'll see what I can do about pushing out a patch with the new URL.handihow commentedon Mar 31, 2020
thanks Nicolas
2dvisio commentedon Mar 31, 2020
same here
2dvisio commentedon Mar 31, 2020
I have temporarily fixed it by overriding the plot.ly URLs in the file
node_modules/plotly/index.jswith chart-studio.plotly.com.nicolaskruchten commentedon Apr 1, 2020
From reading the source, it appears that the
usernameparameter can be either a string or an object, so passing in an object withusernameandapiKeykeys, and ahostkey with value'chart-studio.plotly.com'should do it, without needing a new release.handihow commentedon Apr 1, 2020
this works for me thanks
2dvisio commentedon Apr 2, 2020
Have tried after undoing my fix and it works for me as well.
shaedmorgan commentedon Dec 21, 2020
I'm running into this same issue now months later. Code was working just fine until it all of the sudden stopped working. I tried implementing the updated URL to no avail. Error message is almost exactly the same as above, but I'm getting a 500 code instead of the 301.
Any ideas?
Code:
Error:
