When I was clicking to enter the new IBM Cloud Hyper Protect DBaaS Beta service, I ran into the following problem and saw the following error message. To resolve it, I tried clearing Chrome cash and cookies.
Problem:
Am using Chrome Browser and when I click to enter the new IBM Cloud Hyper Protect DBaaS Beta service I get this error about cookies:
When I close the message box it just sits and spins up the error again.
I happened to have Firefox as well and when I used that I could access the cluster overview of Hyper Protect DBaaS just fine.
I tried clearing cookies and cache but am still getting the error on Chrome.
My version seems to be one of the supported browsers:
https://console.bluemix.net/docs/services/hyper-protect-dbaas/help-issues.html#supported-browsers
Ralf, here is the answer hope it will help you ....
Related
I have a GCP project. Then I gave permission to a user A with email A#email. They connected it to Firebase and developed a project there with hosting enabled and verified. Then another user B came and I switched the ownership of the project to them and removed A from this. After ownership change, the hosting verification was re-triggered (as expected). However, since 1 week it only shows
I tried searching for other people who had such an issue and nothing came about. I even wrote a bug report but for more than a week nobody has reached out to me and I am worried because the grace period is 1 month and I my project could go down. Have you heard of similar problems?
Edit from comment:
I can confirm that the error comes in Chrome and incognito (version: 80.0.3987.163 (Official Build) (32-bit)) and in Firefox and incognito (version: 72.0.2 (64-bit)). Opening the console gives error 503 for URLs https://clients6.google.com/siteVerification/v1/webResource?verificationMethod=DNS_TXT&alt=json&key= and https://clients6.google.com/siteVerification/v1/token.
The issue was due to my company's license agreement with Google and the way Firebase Hosting is made. More details below.
Strangely enough, using GCP and Firebase require a GCP license. With this license you can do everything from adding/changing/modifing collections/projects. However, the functionality to 'Verify' your hosting site goes through the Google Console which is not included in the license.
Encountered this same thing. The problem turned out that I was using a Google Workspace account that did not have "Google Search Console" enabled for the domain I was logged in on.
To remedy, I had to login to my Workspace Admin, and go turn it on as shown below.
I am running dockerized images of wirecloud+nginx from a remote server, trying to access Wirecloud from my browser. Wirecloud failed to load correctly, issueing the following message:
Your browser seems to lack some required features
We recommend you to upgrade your browser to the newest version of either Firefox or Google Chrome as these are the browsers currently supported by WireCloud.
I can confirm my browsers (firefox and chrome) are up-to-date, and I can run wirecloud locally on my machine using same browsers, as in
Any idea why this happens please?
Figure it out now, working...
I had issue with static files environment definitions in my docker-compose.yml file that differs for nginxand wirecloud services.
I tried 2 example programs from the IBM website.
timestamp example
I cannot see anything in the debug tab. Debug node is of course activated and its output is set to debug tab and console.
Chrome developer tools gives some more information:
Warning: SVG's SMIL animations (, , etc.) are deprecated and will be removed. Please use CSS animations or Web animations instead.
It also detects that something has happended (Preview "OK", Response "OK").
I also tried Chat example
But even when I try to execute the "Run the app" button the window never displays "connection established" or any chat message. Chrome developer tools throws error:
Uncaught InvalidStateError: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
I did not install anything related to Java, JS, JSON, Node.js on my pc as I asume that everything runs inside Bluemix.
The underlying issue is a failure to establish a websocket connection with the node-red instance running in Bluemix. This is a known issue when accessing from certain networks that is usually resolved by accessing the application using https rather than http.
I am trying to create and configure the Bluemix Single Sign On service and I am facing issues.
I create it unbound of any app, and when trying to setup it on the first dialog (provide a service name which will be part of its URL) it gets hanged. The browser is unresponsive for 1 minute or so and finally it fails with error message: "env: Client internal Error"
I am facing the same issue with Firefox 38.0.5, Chrome 43.0.2357.81m and IE 11.0.9600.17801
Any suggestion? Searching the forums I found as recommendation to clean browser cache and cookies. I already did it with no success.
EDITED: In parallel, I added as manager and developer another colleague to my Bluemix Space and it worked fine to him. So it seems it fails with my user which also is manager and developer but it exists in other spaces, etc...
Any thing I can check to narrow the issue?
Thanks!
on yesterday there have been a maintenance/upgrade activity so probably it your problem could be related to this.
Could you check again if it is working right now?
I'm currently developing a (Java) backend for a mobile application using Google App Engine (SDK v1.8.8) and Cloud Endpoints. I'm using Eclipse (Kepler) with Google Plugin (v3.8.0) to develop/deploy the code.
I've been using Google API's explorer for many months during the development to test the endpoints and up until yesterday, everything was working well... if I ran App Engine locally, I could test the endpoints at:
http://localhost:8888/_ah/api/explorer
Likewise, I could execute against the remotely deployed version at:
https://1-dot-[my-app-id]-app.appspot.com/_ah/api/explorer
...in both cases, everything worked as expected.
However, as of yesterday, local execution no longer works... instead, my requests are sent to the remote (i.e. live!) version of my API. I'm still accessing API Explorer on localhost and according to it's output, my requests are still being posted locally... here is what is printed when I execute a function 'foo' on 'admin' endpoint:
Request
POST `http://localhost:8888/_ah/api/adminendpoint/v1/foo`
X-JavaScript-User-Agent: Google APIs Explorer
However, for some reason, these requests are being sent to the live/deployed instance of the API.
I restarted my browser (Chrome) and cleared it's cache, tried another browser (Safari), restarted the machine, re-deployed the API... It feels like something is being cached somewhere but I'm running out of ideas.
Does anyone have any suggestions?
The error has been fixed in the Google App Engine SDK for Java version 1.9.17, as indicated in the release notes (https://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes). I updated my libraries to 1.9.17, and the APIs explorer started working again for localhost.