I did just that in Chrome, at it finally worked. Luckily, the community here worked and was able to suggest disabling popup blockers. Oh and BTW, when you finally do (on a different browser, for example) - you find out that you actually cannot contact support because your team is on a Standard plan. However, to contact support you must first log in. It's actually quite amazing that, when experiencing issues with login - your UI suggests contacting support. algorithm" have made a malformed request, by poor design. Seriously, 3 years + and the best you can do is say "Oops you have made a malformed request" when in reality, for some reason, popup blockers are incompatible with how your authentication works? Is it that "I have made a malformed request" or is it more accurate to say that "you / your auth. Once again, I appreciate the tools, but this is a weak point. There is next to nothing on installing the SSL certificate, the DB connectivity details are out of date based on KB articles later found, documentation references settings there were removed. I ran into this when I setup our local Jira Server instance too. They work great, but the documentation is bad. I would say this is my one complaint about your tools. All your documentation needed was a line that stated: "This error can also be the result of a conflict with an enabled browser extension, please disable browser extensions and try again."Īfter 3 years to waste this much time on this because you didn't add one line. I sat here repeatedly deleting cookies, cache, and following useless other suggestions only to find this article and fix it in 2 minutes. I find it a real head scratcher that after 3 years that at a minimum the error report details or KB article hasn't been updated. It got tossed into the we will have to research it bucket. I ran into the same problem this week I contacted support who sent me some email messages and to which I supplied the requested details.
0 kommentar(er)
