Moodle, I directed my VM on Google Cloud to my subdomain that is in plesk, when I access my Moodle through the subdomain it already enters Moodle, however it appears the Fixed IP of Google Cloud, I would like to use mine from the subdomain.
Tentei alterar no dns da google, porem sem exito.
Related
I had an operational and accessible Bitnami Wordpress site on Lightsail with my domain at GoDaddy. My cert expired so I went to renew it, and also switch my domain from living at GoDaddy to being at Google Domains. Ever since, I haven't been able to load the site by IP or domain. Are there any good guides specifically for configuring this set up?
Bitnami Engineer here,
Please ensure your domain points to the correct IP address (the one assigned to your instance). You can verify that using this online tool:
https://www.whatsmydns.net/
If the domain doesn't resolve to the correct IP address, you will need to update the DNS records in your DNS provider dashboard. Once you confirm everything is configured correctly, you should be able to renew your certificate.
I have bought a domain name on Google Domains, installed Wordpress Multisite on a Google Cloud VM with Compute Engine, setup a load balancer with 2 instances and an Active Google Managed certificate.
I have followed the instructions at https://cloud.google.com/load-balancing/docs/https/ext-https-lb-simple and pointed the Google DNS at the Load Balancer. I currenty get:
The website working in http (not secure) with the direct IP of the VM.
The balancer switching between the two IPs if I enter the https address (ie returning Page served from: lb-backend-pubdeals-x06k) but not returning the wordpress site.
Address is https://pub.deals
But what I want is someone to type in http://pub.deals and https://pub.deals and get the secure site.
Does anyone have instructions on how to redirect users who arrive at http://pub.deals are then redirected to https://pub.deals?
Thanks Jay
So John Hanley was right, I was over complicating things. For the last 20 years or so I've used hosting companies for my sites, and taken care of ssl when I needed to within wp-config and .htaccess, but this is my first time using google cloud and vm builds, so I followed their docs to apply a google managed ssl. They say in order to issue a google managed sll you need to have a load balancer set up, so I rtfm and set one up. It worked as far as the user was delivered to a secure site of either one of two instances, but I couldn't figure out how to attach them to my vm instance with wordpress on it and hence get my content displayed. I did get the http --> https forward using these docs (https://cloud.google.com/load-balancing/docs/https/setting-up-http-https-redirect) but I still didn't manage to connect the whole affair to the VM with wordpress on it.
TLDR; I deleted the load balancers and google certificate and did it through wordpress.
I'm starting out on AWS and try to host a website on the platform. The S3 bucket and its content is set up and i'm able to access the website via the url s3 is providing.
Permissions and properties are set to accept public traffic and that the bucket is used to host a website. The index document is correct.
Now i want traffic to be redirected to my domain visionranger.com, but it shows the error "IP address could not be found"
I tested this issue on 4 different devices across multiple browsers (including Chrome, Safari and Firefox).
Bucket, domain and hosted zone do have the same name and as AWS recommends, I asked my previous provider if they transferred the dns services to the new provides (in this case route 53) and they did.
I waited longer than 48 hours after settings everything up before writing this so all services should be working by now - but they don't.
The image shows the dns records of route 53.
I am grateful for any help.
By running a DIG command to get the NS value of your domain it returns a SERVFAIL indicating that the configured nameservers for your domain do not contain the record for you domain.
The next step is to run a whois which indicates your configured nameservers are below:
NS1.BDM.MICROSOFTONLINE.COM
NS2.BDM.MICROSOFTONLINE.COM
NS3.BDM.MICROSOFTONLINE.COM
NS4.BDM.MICROSOFTONLINE.COM
As you're trying to use a Route 53 public hosted zone you will need to update your domain registrar to use the nameservers found under the NS record of the public hosted zone.
Follow the instructions here for your specific domain.
I've recently converted from using traditional registrars and started using Google for website hosting and domain registration. I've followed various guides and am currently infuriated at how hard it is to connect my domain owned by google to the google cloud instance while retaining email forwarding.
In order to point the domain to my VM in requires changing the nameservers. Once the name servers are changed then email forwarding stops working. I'm stuck in an infuriating loop. There has to be a better way.
Here's the process I followed
Google Domain > ExampleSite.com
Google Domain > support#examplesite.com (email forwarding to default gmail account)
Google Cloud > Create Wordpress VM instance
Google Cloud > Add DNS Records
Google Domains > Update Nameservers with info from Google Cloud DNS
Works, but email forwarding is immediately disabled unless I revert to default google nameservers, which stops the domain from pointing to the VM.
Please. Anyone. Help with a better way of doing this. Please. I'm so frustrated.
Thank you.
The reason why email forwarding breaks that your Cloud DNS is not configured with the necessary MX records. Here are the two possible solutions:
Add the MX records described here to your Cloud DNS configuration.
Revert back to Google Domain's name servers, which has the MX records built in. You can then set up your website by creating an A Record for the # record and www subdomain record to point to your GCE's IP address.
If all you want to do is to host a website I recommend (2), as it saves you the cost and complexity of having Cloud DNS as well as Google Domains.
We wanted a subdomain http://magento.ngstorefront.com to point to a VM on Google Cloud. We could not find clear docs on this.
What we did:
Deployed a Magento Google Click to Deploy VM from marketplace
Assigned a Static ip address to the VM --> 35.193.85.53
The default Magento site loads at http://35.193.85.53
To have the sub-domain http://magento.ngstorefront.com load the site (loading at http://35.193.85.53). So we added a new A record for "magento.ngstorefront.com --> 35.193.85.53" in Google Cloud DNS
On the domain registrar (Google Domains), we added a Registered host (magento.ngstorefront.com) and a Custom Record as below.
But the site doesn't load at http://magento.ngstorefront.com What are we missing?
The subdomain is resolving now. Wanted to add the answer.
The mistake we did was to create the subdomain A record in Registrar (Google Domains). Although registered in GoogleDomains, our primary domain ngstorefront.com is pointing to Siteground
So we have to add the A record in Siteground instead of GoogleDomains , like this
Updated on 3/15/2019
While the above solved the issue of IP address pointing and loading Magento, but we had one issue where the URL would change to IP instead of staying as http://magento.ngstorefront.com
To solve the above, do this:
Login to Magento Admin > Stores > Configuration > General > Web > Base URLs
And enter the domain name you want Magento to use.
Based upon the answer provided, I'd say that the problem is, still having set siteground.us as NS.
You'd have to change the NS records to Cloud DNS name-servers at Google Domains, then it would resolve through Cloud DNS and the zone-file can be maintained there (as you've tried without effect).