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.
Related
So I have been following the following step for past few months:
Log in to Google Cloud Console from Chrome's incognito mode
Activate Cloud Shell
From there, I usually opened Editor and managed my files in a new window
Today while I was following the above steps, this issue raised up:
Basically, I cannot open editor anymore. I have already went through similar posts, and my issue is that I am using incognito where browser extensions or cookies shouldn't be an issue.
I am facing this problem for the first time and if anyone knows what is the cause or any suggestions would be appreciated.
EDIT:
For now Microsoft Edge InPrivate Mode is working for me. I am still interested in fixing the issue for Chrome.
Have reported the issue in Issue Tracker. Please "start" for more attention.
This started happening recently because third-party cookies stopped being supported in Incognito mode as of Chrome 83. Third-party cookies are required for the editor to work because of the way the open-source Theia IDE is integrated into Cloud Shell. The team is exploring various fixes, but in the mean time the following workaround should work:
In Incognito Mode, click on the crossed out 'eye' icon on the address bar.
Click on 'Site not working?'
Click on 'Allow cookies'
Safari problem stems from the same issue, but I am not certain if a similar workaround exists.
I've encountered the same issue myself (I tried this on Chrome running on both ChromeOS and MacOS) - it looks like a bug so in this case I'd recommend reporting it on Google's Issuetracker (you can even put a link to this post).
UNfortunately it looks like it's not just the Chrome browser. I tried this on Safari 13.1 and found the issue you described is also present.
I didn't check other browsers but IssueTracker is the way to go. And be patient :)
I am having an issue with GitHub where when I try to submit certain things on the website it will shoot out the following error: "Your browser did something unexpected. Please contact us if the problem persists." I logged out of GitHub and now when I try and login, I am getting the error and cannot get back in.
Note this error is only occurring on my Chrome application and not on Microsoft Edge. I did clear the cache, cookies, data etc and restarted Chrome and the issue remains.
Anyone know of a good solution for this error or what is causing it in the first place?
Thanks VonC for your feedback! Turns out it was one extension in particular. Having the VPN application, Private Internet Access enabled, seems to cause issues with GitHub for some reason. Not sure why.
Check first if the issue persists, because the incident yesterday was about "elevated errors for Web and API requests."
Check also if you have 2FA activated (in which case, don't forget to use a personal access token as your password)
Finally, try and open Chrome without any plugin activated (start chrome --disable-extensions), to see if any plugin might have been interfering with the login process.
check the browser's extensions and turn off Adblock or Adgurd any extensions that block advertising then, try again
I have switched off every extension except uBlock Origin (edit: now I tried disabling that too) and this still happens: links in Google searches and Inbox mails get rewritten to lnkr.us. I have checked with developer tools and this is not in the HTML source. This happens on click. Then uBlock Origin brings up the "document blocked" tab, I close it and if I click again, it goes straight to where it should. I am quite clueless as to what can cause this. I have seen others complaining and pinning it on this extension or that but as I said: I have disabled all my extensions. I am on Linux and hopefully malware free.
Looks like this:
https://lnkr.us/get?sourceId=5&uid=50639x1413x&format=go&host=icontent.us&out=http%3A%2F%2Flink.freedompopaccount.com%2Fu.d%3FZ4GuEv3xXUytsV84j81iW%3D3361&ref=https%3A%2F%2Finbox.google.com%2Fu%2F0%2F
A most curious example of this is:
http://mail-archives.apache.org/mod_mbox/httpd-users/201601.mbox/%3CCA+gyi+0DXFUBw5NYoyKFsvn-zxJ_65KJS_S8UxSHgHzSqsfNUQ#mail.gmail.com%3E
where the mangled URLs got into the mailing list archive.
Another is:
https://www.reddit.com/r/urbanplanning/comments/471v0k/the_distorted_dna_of_your_community/
The real question is: how can I debug what happens. I can read C, I have used gdb but I am no master of it to say the least.
Edit: nothing unusal on chrome://plugins either.
Edit2: sometimes it's icontent.us ; apparently that has been there for a year now, check https://twitter.com/baio1980/status/557236850486960128 the link there.
Edit3: I think this doesn't happen in Incognito mode so it might be an extension still but how can an extension stay alive after ticking it off on the Extensions screen?
Edit4: I have created a new ~/.config/google-chrome directory , disabled syncing extensions, reinstalled all my extensions and this doesn't happen now. My apps and plugins are the same.
I have created a new ~/.config/google-chrome directory , disabled syncing extensions, reinstalled all my extensions and this doesn't happen now. My apps and plugins are the same.
It seems that the latest update of Google Chrome 44 to 45 is blocking clickonce applications.
Our clickonce application is working fine and is in production for over weeks.
This morning we got reports that when users tried to download our application it straight end up in the Downloads tab with following message: "[...].application may harm your browsing experience, so Chrome has blocked it. Recover malicious file". After clicking that message a confirmation dialog is shown and if that gets accepted the user can download the application file.
Is anyone else having the same experience with their clickonce applications and do you have any idea how to get around with it?
Thanks for any ideas / help!
(I have sadly not enough reputation to post images, sorry for that)
Elia
It looks like it might have just been raised in the Chromium issue tracker:
https://code.google.com/p/chromium/issues/detail?id=532952
Quoting from there:
My understanding is that if Google has not scanned the file because it is unreachable or isn't aware of it (no public links so it can't be crawled), Chrome will block the application."
In latest version things are worse: There is only Suppress button next to the message "xxx may harm your browsing experience, so Chrome has blocked it" with no links for "recover". The trick is to click on Show all downloads button on far right. There you will see the link for recovering the file that Chrome unnecessarily deemed as malicious.
Our application runs within a frameset that uses one visible frame to show content and two others to handle communication with the server. I did not design this and have no power to change it now.
The problem is that my local machine does not have a valid SSL certificate (it's self-signed), so accessing it and trying to login pops an 'invalid certificate' error. In IE and FF I am able to simply click a button to continue. However, I just started trying to test with Chrome and it seems to stop me dead with:
Error 501 (net::ERR_INSECURE_RESPONSE): Unknown error.
There is no option to continue. There also doesn't appear to be anything in the options menu to add localhost as a trusted site, though I may have missed something. Does anyone know a way around this? Disabling SSL locally won't be very easy and risks me forgetting to enable it for deployment. Any other thoughts?
Thanks.
What I would recommend is to add the self-signed certificate to Chrome manually rather than trying to make localhost a trusted site. It looks like there are a couple ways to accomplish this. Here is one forum thread that discusses the issue, but I think it boils down to:
If you are on Windows, install the certificate in IE. The linked thread explains this process in more detail, but it looks like you go to the site in IE, click "Continue" or similar, then right-click the certificate error button to the right of the URL bar and follow the prompts. (If that doesn't work, here's a question that I believe addresses the issue.)
More recent versions of Chrome appear to allow certificate import directly. On version "15.0.874.121 m" for Windows, I can click the tool menu, go to Options, then Under the Hood, then the Manage Certificates button. I believe you then click the "Import..." button, though I do not recall whether you need to be on the Personal tab or one of the others. You will need to have the certificate in a file format that Chrome supports (p12 is one, there are others). There is a help link in the appropriate place that specifies the accepted formats.
I recommend Safari for this purpose. Sign a cert with StartCom, and enroll the cert in the browser.