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.
Related
Recently we created a custom bundle from AWS workspace having Windows Server 2019. When we started to deploy this image to users, we saw that many of them did not have internet connection enabled. o far only 2/6 users for whom the image was deployed had internet connection enabled. We tried to rebuild the image, still the issue persists.
So far, we did not find any helpful docs on AWS to resolve this issue. If anyone faced similar issue & were able to resolve it, let us know how.
We tried to do ipconfig /flushdns & /releaseip. But this did not work. /releaseip resulted in Workspace loosing complete internet access & it got stuck in rebooting state. So far, only re-deploying the image has worked. But that too is a blind shot as it may or may not work.
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.
Is anyone getting this issue with Google Cloud Run Domain Mapping? When I add a custom domain to my domain mappings, I get this:
Waiting for certificate provisioning. You must configure your DNS records for certificate issuance to begin.
I know it says it's only added 1 day ago and I should give it time, but I actually let it go for 5 days, deleted it, and this is my second try.
You can see in the below screenshot that it is added via Cloudflare. I even tried toggling the Proxy service on and off with no luck.
Turning proxying off in CloudFlare resolved the issue in my case (keeping it as DNS only).
Most likely the Google balancer needs to get the request first-hand in order to make the certificate safe.
I faced the same issue with exact error:
Waiting for certificate provisioning. You must configure your DNS records for certificate issuance to begin.
After digging a bit more the error actually made sense. Before generating the cert Google is trying to check if our DNS records are properly configured and well propagated through all regions which is not the case for me due to some glitch at the nameserver level. I raised a ticket with my nameserver vendor with the DNS propagation report from the below tools/websites which clearly showed that the DNS records are not available in some regions. Once they fixed the propagation issue, all my reports started to show positive results after which I recreated my domain mapping and it worked within few minutes.
Tools used to check DNS propagation status:
https://dnspropagation.net/
https://www.whatsmydns.net/
https://dnschecker.org/
At the moment, seems like Domain Mapping is just a buggy service.
Seems like the solution at the moment is to be patient and to try several times until it works. I'd suggest to give it some time between attempts.
The reasons why I feel it's a buggy service:
gcloud beta run domain-mappings create stucks at Creating......⠼.
gcloud beta run domain-mappings describe shows messages such as:
"Domain mapping '[...domain_name...]' already exists for this application.
You can modify this domain mapping with DomainMappings.PATCH".
"Waiting for certificate provisioning. You must configure your DNS records
for certificate issuance to begin." - Even though the DNS records are fine.
User Interface isn't any better. It also can stuck while creating... And in the console, it says that it may fail silently, suggesting to use gcloud CLI as a workaround
Update 2022
It's been a while since I last used this feature but it is still taking ~2 hours for the domain to become available.
I just tried Toggling the proxy off again it seemed to work. They must have fixed something internally.
I had the same issue in past few days, the loading icon was spinning for hours/day and my DNS records were correct (checked in google toolbox). I "resolved" this issue just by repetitive add/remove of the domain, after like four attempts it suddenly started to working. I always waited for hour+ before each attempt. I used the GCR interface, not the console solution. I guess, as was mentioned before, it's because it's still BETA, but maybe this comment might help someone till they resolve this issue.
Adding the domain mapping via the console does not show the correct DNS records to be added as is it missing the name field. If you run gcloud beta run domain-mappings create it shows the DNS records as having a name field with the value of the cloud run service.
I had a similar error on a domain I bought with Goddady, the issue was a result of a parking domain whose source I can't tell unless it was set by the vendor. It mapped my domain to this page and its IP 34.102.136.180 was preventing my service from mapping correctly. After chatting with a gae assistant I was able to resolve the issue by deleting the IP, but of course, sought clarification from the vendor themselves. It was my first time using Godaddy and for the life of me I couldn't figure out the problem.
I had the same situation. Additionally incurred me error message on cloud domains.
Your domain is suspended because the registrant email address has not
yet been verified. Check your email and follow the instructions to
remove the suspension.
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.
I realize CloudFoundry is still in beta and I'll admit to being moderately ignorant when it comes to this level of cloud computing but here's my question: I create an app, everything works, I upload it to CF. Now what? I want to launch my app in the wild. I want users to not see a CF URL.
Here are some pieces I do know, but I'm not getting the entire picture.
I know I can map a URL to an app. So presumably that's just some DNS routing happening. But other than that, is it safe at this point to bet the farm on CF and, for example, launch of startup using it? At what point am I going to realize I need to move to something like RackSpace (or whatever) and is it possible to take my CF VM and just move it?
Overall, I just don't fully understand what we're getting with CF other than a quick way to deploy a demo application.
At this point, if you need a custom domain, you need to configure an external proxy and from there route the traffic to your CF.com URL. This is a good example.
But the advantage of CloudFoundry is that it is entirely open source. You can always move your app to a compatible service provider, for example AppFog, with not much more than a simple push.
You could even deploy your own CF instance/server on Rackspace.
It appears that there is still no support for external domain mapping on Cloud Foundry. Here is another example that uses a Python reverse proxy running on Google AppEngine. This works well. http://programming.mvergel.com/2011/11/cloud-foundry-and-custom-domain.html
Right now, CloudFoundry.com doesn't offer domain mapping. You might expect that it will do so in a future fully-supported paid version, but as you note, right now it is still in beta.
For what it's worth, I am running a startup B2B product on CloudFoundry.
I have deployed the open source version on our own infrastructure though, I keep a close watch on changes and even review other people's commits.
That's a significant investment in terms of learning and time, but in my opinion it's worth it.