When i tries to log in to Bitbucket (web-based version controller) on Chrome (google chrome web browser), i consistently get,
Oops, you've made a malformed request.
If you came here from a link we sent you, please contact support.
This can happen on Chrome. (works fine on Chrome incognito) This issue occurred when i try resetting my password.
then, i founded a solution from Atlassian Cloud Support. this
but, that's not resolve my problem.
In my research, it seems that people have experienced this error before, but none of worked solution i didn't found.
Any help some else is appreciated!
Thanks.
First thing - try to log into BitBucket in another browser, or in incognito mode:
Windows: ctrl + shift + n
Mac: cmd + shift + n
If it doesn't work then your best bet is to contact Atlassian support.
But if it works, then it's a big chance that an extension is causing the issue.
What you should do is disable all your extensions (type in the URL bar: chrome://extensions) and re-enable each extension, one by one, until you find the culprit.
For me it was this extension causing the problem:
Library Detector v5.6.0
I hope this helps you.
As snishalaka mentioned, https://poperblocker.com/ caused my atlassian Oops, you've made a malformed request problem. Disable it then login. Finally, you can turn on again.
As mentioned in the comments, just click 'Allow Popups' in the site in your popup blocker plugin and it will work fine.
Because it works in incognito, it sounds like there's some bad caching or something along those lines. Navigate to Bitbucket, open developer tools (menu -> More Tools -> Developer Tools), navigate to the Application tab, and in the top section of the left pane, click Clear storage. Now in the right pane, you should see several checkboxes and a "Clear site data" button. Click that, reload the page, and try again.
I had the same issue, couldn't login to Atlassian with Chrome. Strangely it was working on incognito. This lead me to checking my Chrome Extensions. One of the extensions I had installed, which was deactivated in incognito, was causing the issue. After removing it, everything went back to normal.
There may be several reasons for this issue. One was, account created earlier and now that was inactive. Other reason can be, login mail used in other bitbucket workspace(in other organization you worked before). So better to send this question to Atlassian support to resolve.
You can raise a question using below form.
ask bitbucket question
search other bitbucket questions
Well the issue for me was due to utorrent extension, soon after i disabled that it started working fine.
I've been getting annoyed from this. It was used to work fine, but it must have happened with some recent update.
I'm on Google Chrome 71 and the microphone doesn't work. Regardless the extension (including Google Meet) and the settings which clearly shows the microphone as active, the audio is not passing sounds in.
The audio settings at computer level are fine, the chrome settings are fine and the microphone is enabled and whitelisted for the given site.
I tried also to fully reset the browser, restoring to the original settings and to use unlinking my accounts. No joy.
Conversely, while using Chromoium (Google Canary) everything works fine.
Has anybody experiencing the same or found a solution?
Ok, in a nutshell - and after having reported this to their chrome bug center - it turned out to be an issue I (and very likely many other users) have been experiencing with the upgrade to MoJave.
Basically, the upgrade seems to remove the microphone access at OS level.
To fix/check this, go into System Preference > Security and Privacy > Microphone and re-instate the check to Google Chrome, which should in theory unticked as it was on my case.
I've had intermittent issues with Google Chrome the past month. I'll open a new tab and a page will time out, and the dev console has been freezing on me.
I'm stumped on how to fix it?
List of things I've done.
Suspected malware, ran Sophos, came up with nothing.
Cleared Chrome of all extensions, cache and localStorage.
Removed Sync / user profile.
Uninstalled & reinstalled (this was before clearing all the saved browser settings)
I'm on Chrome 63.0.3239.132
Am I the only one experiencing this?
Any general advice?
Maybe try going down a few browser versions?
Had it happen today this was my fix - I have no idea what the cause was.
Settings -> Advanced -> Reset
I am trying to implement and use the Chrome Speech API on my website but I'm not able to do it. The response I receive is that the "Permission to use microphone is blocked" but it really isn't. Microphone settings in Chrome are clearly showing that I don't have sites blocked and that the system should it least ask.
It is not a problem with the website because I have performed tests on other computers and it is working fine. I would like to figure out the settings/preferences that need to be readjusted in order to make this work.
In addition to this, in C:\Users\MY-USER\AppData\Local\Google\Chrome\User Data\Default\Preferences I was able to see entries for my site and I removed them but nothing changed. I tried also (not in order:
1- Reset Chrome.
2- Uninstalling/reinstalling Chrome. Manually removing files and registry entries.
3- Run Chrome in incognito mode.
4- Run ChromeCleanup Tool
5- Not working on Chrome Canary.
6- Every computer was tested on the same internet connection.
I am not sure what else I can do about this.
Thanks!
We have a web application that runs within a VPN. It has a self signed cert on it and is accessed through the server's IP address.
Part of the functionality of this app are some legacy Java apps (that no longer run in Chrome). Our initial work around for our Chrome users was to run Shell In A Box within an iframe of the web app to run those. All was good until the latest version of Chrome, v45.
What we’re seeing is that appears to be blocking the iframed content (maybe because of the self-signed cert?). If we grab the ShellinABox URL and drop it in a new tab, it works as it used to in the iframe. If we go back to the iframe, it now works. If we close Chrome and open it back up, it still works.
I should also note that we tried the canary builds as well. It's up to v47.x and we still see the same behavior there. We were reading through some of the Chrome group/bug lists and saw some reports that were similar but the "fixes" supposedly going through canary still didn't resolve it.
So, it appears that an exception is being logged somewhere. Does anyone have an explanation for this behavior and is there a way to set this exception without jumping through those hoops?
It turned out it was due to a permissions issue with ShellInABox that didn't reveal itself until v45 of Chrome, for some odd reason.