Not able to see SQL dashboard in Google Cloud Platform. When clicking on SQL link, getting the below error.
Any idea why it's happening and how to fix it ??
Got the solution from google like 'it's browser issue'. In crome its not working. But in other browser(eg firefox, IE) its working.
This message can appear for a number of reasons. It could be an intermittent issue or something wrong with your account settings. To troubleshoot do the following steps in order:
Try to open the page in incognito mode of your browser
Check your permissions in IAM
If the issue persists, open a new private case on Issue Tracker mentioning your project-id by clicking here
Today this error really annoys so much, comes again and again and only come in the SQL instance, every other thing works fine But in the end, I try to login into Incognito mode and then its work so please try in the incognito mode or else try in a different browser.
Related
I followed the AWS guide on how to set up Drupal on AWS, everything installed fine and the command line is working well.
It's the basic site and set up with nothing custom.
I can access the site fine following the guide but when I try to log in I get the below error:
To log in to this site, your browser must accept cookies from the domain ec2-XXX
After Googling, it mentions a patch could fix it but I can't seem to get it working.
Any help is appreciated! Thanks
Turns out I just needed to Open on Safari - I was already logged into the site!!
Must be an actual Chrome cookie issue, clean up those crumbs people!
Leaving in case someone needs the help....
I'm currently finding myself unable to enable the Admin UI. It was enabled before and now does not seem to work.
When I looked at my backends I see this.
Image of Amplify backend environment with a button to enable admin UI.
I then clicked the switch to turn on the Admin UI as shown below.
Image of the Admin UI enable screen.
I clicked it and it says it's enabling in a popup here, before saying it succeeded in another popup here.
I thought this was originally something wrong with my project but it's happening on my other amplify project - is the Amplify Admin UI down for some reason?
P.S. I was going to post this on server fault as this post says but there was no tag for Amplify on here.
Sorry this is not an answer, I cannot make comment so I have to write here.
I wasted a whole day by meeting the exactly the same issue.
At the same time, I tried to run Amplify pull --appid --envName several times, it always stuck there.
Amazon status page shows everything is fine now but I cannot believe it.
I also posted a question here but it seems nobody answered it.
I hope this issue was discovered by more people and Amazon finally can fix it, I believe it's not a problem on our side.
The issue was resolved as shown in this ticket I opened.
https://github.com/aws-amplify/amplify-adminui/issues/206
Have you tried selecting the environment and then clicking Open Admin UI?
I also wasnt able to login clicking in the URL and with my credentials, but clicking there worked.
My internet connection behaves in a weird way.
At some point, websites stop opening (I am using Chrome), but the tray icon (Wi-Fi or Lan) indicates that everything is alright, and the TroubleShoot Diagnostics tool tells this as well.
One thing to notice is that when I enter Google search requests at google.com, then it provides me with search results. However, when clicking on any of the search results, then websites do not open.
Sometimes, internet gets "frozen" in this way when I open a Jupyter notebook, which also stops working (which is strange, since it uses localhost at 127.0.0.1:8888).
ping 127.0.0.1 does not show any problems as well, and the file 'hosts' also looks OK (there is the line '127.0.0.1 localhost').
What could be the reason and how else I could trace the problem?
Update: here is the screenshot of the Chrome's development tools (Network tab)
All three error are ERR_TIME_OUT
Sounds like you may have blocked some site/sites with Chrome. You can verify by using a different browser and trying out sites that you can't get to in Chrome.
Another good troubleshooting method is to use Chrome Developer Tools. On Mac, the shortcut is Command+Option+I. Open the developer tools and go to a site that's not working. You should see a bunch of error messages in the console (if the console is not shown, press Esc). Also, go to the 'Network' tab and check if any of the requests are in red.
If the red request status says 'blocked' then open the console back up (Esc button) and click the 3 dots in the top left corner of the console pane. Select 'Request Blocking' and deselect the checkbox that says 'Enable request blocking'
Another possibility is that you've disabled cookies on certain sites. In that case, in the navigation bar, go to chrome://settings/cookies and remove any entries from 'Sites that can never use cookies'
I see the below Failed to load error with a tracking number when I click on the SQL option:
Failed to load
Tracking Number: c7505762059293335
I have tried clearing the browser cache, and I have also tried using different browsers - tried Chrome, Firefox and IE; I see the same issue in all three browsers.
This message can appear for a number of reasons. It could be an intermittent issue or something wrong with your account settings. To troubleshoot do the following steps in order:
-Try to open the page in incognito mode of your browser
-Check your permissions in IAM
-If the issue persists, open a new private case on Issue Tracker mentioning your project-id by clicking here
i have running opencart for months now never have an issue since yesterday when i try to login to admin it does not show any error but stay on admin page. with these 2 request
http://mywebsite.com/admin/index.php?route=common/login
http://mywebsite.com/admin/index.php?route=common/login&token=c68f8306024feb01cac3ba1814a61a80
I am using windows. I've checked error.txt nothing there. Have no idea where to go from here
I had similar problems. Do you have slow_log enabled in MySQL's my.cnf? If so, check the size of the log and the free space on the server (when the slow log takes up all the free space things go nasty with OC).