Attempted a minor system update to WikiJS yesterday afternoon, and when the site came up for a restart... all I'm getting now is a site can't be reached failure.
Having issues SSH'ing into the box, and am looking for ways around that particular problem. It's hosted on an AWS EC2 instance that I can stop/start/reboot, but that's it.
At one point yesterday I did get an Unknown authentication strategy "jwt" error, but now it's showing nothing again.
While I'm working through the issues of getting into the box itself, is there anything that jumps out at y'all that I should be looking towards?
Many thanks in advance.
Related
This may be a very simple thing, but I am pretty new to GCP and don't really understand how all this stuff works so please bear with me.
I am trying to host a static site with GCP. My site is built with Jekyll and I am using GCP containers to deploy it. I got that part working.
I then wanted to give it a human-friendly URL. I bought one using the GCP console and then went to create a domain name mapping. So far I have been waiting for a couple of days. I read on some other similar posts that canceling and restarting the mapping process helped with the issue, but I've tried 3 times so far waiting ~24 hours between each, and no luck still.
It tells me that I need to configure the DNS records with my domain host, but if I understand it correctly GCP is my domain host. I have also followed the instructions here and still no luck.
Am I doing something wrong or perhaps I am missing something here?
Note: I have DNSSEC on, maybe that makes a difference.
The Airflow UI randomly fails to show up and a 503 google error message is shown. It's getting really hard and annoying to navigate the Airflow UI. Is this a known issue? After searching this for a long time, on the internet I did not get any leads.
Please let me know if I'm doing something wrong.
I have attached the error message that I'm getting randomly. Hope this gets fixed.
Would you happen to be trying to access the Airflow UI from Asia? This is a known issue for APAC users, and a remedy is coming soon. In the meantime, a workaround is to deploy a self-managed webserver.
Using Spinnaker-Ubuntu-14.04-42 (ami-cfb87eaf) AMI I have created an instance. I have followed the instructions given at here. Though my UI works, but when I click Actions and Create Application the New Application popup seems to take lot of time and it does not finish. What could be a problem?
Finally, I found the solution to the problem, by following the instructions given at following links:
Troubleshooting guide, by looking at the Javascript, I figured that the problem is caused due to the credentials of AWS account/user. The error was 429 Too Many Requests.
Then following the instructions given here, especially bulleted point 3, I was able to start the application.
When I was getting this. I found I actually needed to use a bigger sized instance. Try using one with more memory.
I am actually experimenting with the new Machine Learning API on Google cloud. All tutorials work great, Machine Learning API is activated, I can train models and access the status of the Jobs in the command line. But for some reason, I can't open the page https://console.cloud.google.com/ml/ to manage my models and jobs online.
Also, I don't have the Machine Learning button in the "Product and Services" column on the left from https://console.cloud.google.com/home/dashboard.
Even if I can do without, I wish I could have access to this console to make my work easier.
I found the same question here: Where is the Google Cloud ML Console UI? but the problem seems to be fixed since one of my colleague have access to it. Is there something to update?
I think the fix to enabling public access to all is in the process of rolling out. Sorry for the inconvenience and thanks for patience!
Is it possible that your colleague was a member of our alpha program, and was previously whitelisted to the console functonality?
I guess the title says it all.
I noticed some ads were popping up on a client's site we are currently developing. It only shows on this particular site. Not any other site. It is very annoying to put it mildly.
I thought removing it would be as easy as setting up a new environment on ElasticBeanstalk for it. I was wrong!
I have started a fresh instance for the application, scanned the project folder for malware before deploying, emptied the content of s3 bucket for static files. All these made no difference. The adware/malware is still there.
It has been driving me nuts for the past few days. Does anyone know how to resolve this kind of problem?
Mark B pointed me in the right direction.
I used inspect element to check the network processes of pages showing the Malware/Adware. It was after this i noticed a few asynchronous posts going to http://api.adsrun.net/post. Of course, i'm not making any post calls to this link. So i decided to inspect my JavaScript files as seen in View Page Source. Fortunately, it was in the last few lines of the second file i inspected. Immediately i deleted this file, normalcy returned to my web application.
It has been a very frustrating several hours. Thanks once again, Mark B for your suggestion.