This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 41
Bad response 301 #62
Comments
We have recently changed the domain name of Chart Studio Cloud from |
thanks Nicolas |
same here |
I have temporarily fixed it by overriding the plot.ly URLs in the file |
From reading the source, it appears that the |
this works for me thanks |
Have tried after undoing my fix and it works for me as well. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
The text was updated successfully, but these errors were encountered: