Alustatud

Thank you for reporting the issue. We already know about the problem.

We're currently working on this with the highest priority. We'll let you know when we figure out what happened.

Sorry for any inconvenience.

Hi,

Could you lease remove all cookies. Here is an instruction https://support.google.com/chrome/answer/95647?co=GENIE.Platform%3DDesktop&hl=en-GB

Please let us know if it helps.


-1

Still getting this error.  Cleared cookies, and everything else on the Application panel.

Tried Firefox: not supported

Tried Edge: works for now.

Cleared all vertabelo history.  Was able to login, but get:

Oops we've got a problem. Something went wrong ... Reload page

Which then kicks me back to the Login page.

We've deployed a fix to production. Please try again and let us know if it helped. Thanks.

No still getting kicked back to the "Oops we have a problem...reload page" then kicked back to login.  Will try clearing cache and cookies and try again

No change.  Here is the console log:


common.js?v=3.7.4:284 Trying to reconnect to server
common.js?v=3.7.4:284 Trying to reconnect to server
webapp.js?v=3.7.4:376 [{…}, callee: ƒ, Symbol(Symbol.iterator): ƒ]
VM458:161 WebSocket connection to 'wss://ws-user.vertabelo.com/ws' failed: Error during WebSocket handshake: Unexpected response code: 404
WrappedWebSocket @ VM458:161
c @ common.js?v=3.7.4:276
(anonymous) @ common.js?v=3.7.4:278
fire @ jquery.js:3148
fireWith @ jquery.js:3260
done @ jquery.js:9314
callback @ jquery.js:9718
common.js?v=3.7.4:284 Error occured while communicating with server  Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
common.js?v=3.7.4:284 Websocket closed abnormally. CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}
common.js?v=3.7.4:284 Trying to reconnect to server
common.js?v=3.7.4:284 Trying to reconnect to server
VM458:161 WebSocket connection to 'wss://ws-user.vertabelo.com/ws' failed: Error during WebSocket handshake: Unexpected response code: 404
WrappedWebSocket @ VM458:161
c @ common.js?v=3.7.4:276
(anonymous) @ common.js?v=3.7.4:278
fire @ jquery.js:3148
fireWith @ jquery.js:3260
done @ jquery.js:9314
callback @ jquery.js:9718
common.js?v=3.7.4:284 Error occured while communicating with server  Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
common.js?v=3.7.4:284 Websocket closed abnormally. CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}
VM458:161 WebSocket connection to 'wss://ws-user.vertabelo.com/ws' failed: Error during WebSocket handshake: Unexpected response code: 404
WrappedWebSocket @ VM458:161
c @ common.js?v=3.7.4:276
(anonymous) @ common.js?v=3.7.4:278
fire @ jquery.js:3148
fireWith @ jquery.js:3260
done @ jquery.js:9314
callback @ jquery.js:9718
common.js?v=3.7.4:284 Error occured while communicating with server  Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
common.js?v=3.7.4:284 Websocket closed abnormally. CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}
common.js?v=3.7.4:284 Trying to reconnect to server
common.js?v=3.7.4:284 Trying to reconnect to server
common.js?v=3.7.4:284 Trying to reconnect to server
common.js?v=3.7.4:284 Trying to reconnect to server
VM458:161 WebSocket connection to 'wss://ws-user.vertabelo.com/ws' failed: Error during WebSocket handshake: Unexpected response code: 404
WrappedWebSocket @ VM458:161
c @ common.js?v=3.7.4:276
(anonymous) @ common.js?v=3.7.4:278
fire @ jquery.js:3148
fireWith @ jquery.js:3260
done @ jquery.js:9314
callback @ jquery.js:9718
common.js?v=3.7.4:284 Error occured while communicating with server  Event {isTrusted: true, type: "error", target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
common.js?v=3.7.4:284 Cannot connect to server. Number of retries = 6
common.js?v=3.7.4:284 Websocket closed abnormally. CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: "", type: "close", …}

Hi

I have this error

  1. ajaxSettings:{url"/api/v1/account/account_info"type"POST"isLocalfalseglobaltrueprocessDatafalse, …}
  2. errorThrown:SyntaxError: Unexpected token P in JSON at position 0 at JSON.parse () at jQuery.parseJSON (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:8520:22) at ajaxConvert (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:8846:19) at done (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:9264:15) at XMLHttpRequest.callback (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:9718:8)
    1. message:"Unexpected token P in JSON at position 0"
    2. stack:"SyntaxError: Unexpected token P in JSON at position 0↵ at JSON.parse ()↵ at jQuery.parseJSON (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:8520:22)↵ at ajaxConvert (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:8846:19)↵ at done (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:9264:15)↵ at XMLHttpRequest.callback (https://my.vertabelo.com/webjars/jquery/1.11.3/jquery.js:9718:8)"
    3. __proto__:Error
  3. jqXHR:{readyState4getResponseHeaderƒgetAllResponseHeadersƒsetRequestHeaderƒoverrideMimeTypeƒ, …}
  4. textStatus:"parsererror"


Hi,


@Dean did you cleared all cookies? See instruction https://support.google.com/chrome/answer/95647?co=GENIE.Platform%3DDesktop&hl=en-GB) . Clearing cookies on the Application panel will not work. Application panel shows only cookies matching "/" path only. That invalid cookie has non "/" path set. We're still looking for the root cause.


Did that.  No change, same error.

Actually, default delete cookies on my system was last 4 weeks.  I did that, did not help.

Then I deleted all cookies since beginning of time, that worked.  It however is a super pain.  I am a web developer myself, managing a lot of different systems and deleting cookies to access Vertabelo is not viable.  I have dozens of systems I manage and maintain and wiping out everything anytime I need to get into vertabelo will cost me too much time.  If this persists we will have to cancel.

Fixed

@Dean clearing cookies was one time action. Today we've changed configuration to ignore erratic cookies set by the previous application server.


Sorry for any inconvenience this caused.

Ah I wished you had made that change yesterday.  ;)