Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Login to Feature requests in Chrome does not work!

Markus Zuber

I just get the following bug report:

{"message":"invalid json response body at https://app-co-myaccountspaclientbff-we-live.azurewebsites.net/api/v1/Sso/GetZendeskSsoUrl?redirectUrl=https%3A%2F%2Fsupport.captureone.com%2Fhc%2Fen-us%2Fcommunity%2Fposts%2Fnew%3Fcommunity_post%255Btopic_id%255D%3D360000154057 reason: Unexpected end of JSON input"}
0

Comments

5 comments

Date Votes
  • SFA

    Markus,

    There are some specific security type related settings that are not always set as required on people's systems.

    The simplest "solution" so far seems to be to log in to your main Capture One site account and then head to the forum and click the sign-in.

    I was told some time ago that the problem was a specific unset default Windows registry setting in Win 7.  I fixed that and things seemed to work for a while but now with Win 10, a new system and using the Edge browser (Firefox and IE on my older system) I still get the same problem unless I first log in to the C1 main site before using the sign-in of the Community pages.

    0
  • Markus Zuber

    Thanks - I was not precise enough. I can log in into my account on both Safari and Chrome - but from Chrome the access to the Community forum is not possible - ending up with the error message shown above.

    0
  • Permanently deleted user

    I've had that problem too with Firefox. My solution was to clear out the Capture One cookies and I was able to log again.

    0
  • SFA

    Clearing the cookies seems to work for about a day.

    Using the latest Edge installation on Windows 10 I get the same sort of message. 

    Support advised that if I first log in to the Capture One site and then sign in to the forum there should be no problem. That is indeed the case although the login to the main site expires after 24 hours anyway so the sign-in surprise does not go away.

    It is somewhat frustrating to have an enforced multi-stage login. 

    However, there is some slight saving possible if, when the error is presented, on opens a tab for the main site and logs in (setting the cookies) and then returns to the error messaged tab and refreshes it. That should then permit sign-in. It's not much but it does at least save having to do all of the navigation back to the thread into which one wanted to post something.

    0
  • Markus Zuber

    still the same with Chrome - the only way is to login via the C1 account - then switch to Support, then to Forum and then choose "Sign in" - and finally you are where you should be... :(

    0

Post is closed for comments.