I own a domain through GoDaddy with the .app extension (call it mydomain.app). I have a site hosted on Firebase Hosting for this domain and it works fine. However, the website only loads through https://mydomain.app and not https://www.mydomain.app. I have the DNS properly configured according to GoDaddy tech support and wonder if I'm supposed to explicitly add www.mydomain.app in Firebase hosting in addition to mydomain.app? Seems redundant. Or is this not necessary and I have a configuration problem on my hands?
Go to GoDaddy, where you added your A record to point to Firebase the first time.
Since it's working, that means you configured it to use
# ==> your FirebaseAppUrl.
Under it, now, add also another A record, to configure your www.mydomain.com,
by adding www A record, to point to the same place.
www ==> your FirebaseAppUrl.
Keep both records of course in GoDaddy.
Related
Good Noon, I am stuck in a problem that I am the old owner of the domain named goldaccesshk.com and this domain is expired and bought by some other company and I have removed all the data from my Hosting all files including my database but unfortunately when ever I hit the goldaccesshk.com url it is still showing me the results . How can I resolve that issue . A screenshot is mentioned below
enter image description here
It is surely the cache system of your browser because I have nothing.
Check your wordpress hosting server. The hosting server will cache the files and serve for sometimes. So clear the cache on your server.
Remember we have two part:
#1. Domain registration
#2. Hosting provider
You lose the #1 and still with #2, so if the site still working maybe:
#1. Your cache (this apply if only you be access)
#2. The new domain owner not changed the DNS server on domain registra company.
I believe your problem is the #2, so to solve this you can change the domain on your hosting provider because curenctly he is configured to answer to this domain (You can just change the domain to anything).
I have a site hosted on 1&1 Ionos hosting. Purchased an SSL for the site from 1&1 Ionos as well. So let's say https://www.business.com/ is what I have. Then I have another another site say http://www.mycompany.com/ hosted at the same place - still waiting for my business SSL to be approved hence the http.
So I exported the database from business.com using plugin WP Migrated DB - setting the new URL and actual filepath.
Then I imported the database into a new database for my staging environment to be hosted at http://www.mycompany.com/clients/business.
I copied ALL the wordpress files for the site http://www.business.com/ into http://www.mycompany.com/clients/business exactly except I changed wp_config.php file to reflect the new database details. i.e username, database, location and password.
So I expected http://www.mycompany.com/clients/business to be a complete replica of the original https://www.business.com/. But when I browse to http://www.mycompany.com/clients/business I get the following error:
This site can’t provide a secure connection mycompany.com sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR
I can't even login to the admin panel of http://www.mycompany.com/clients/business/wp-admin
Is what I tried even possible and if it is please tell me what I did wrong and how to fix it. I'd like to create a staging environment to test new themes and plugins before implementing on live environment. Critical to my original site is the aMember plugin which manages all the membership registration info. I've deleted the Really Simple SSL plugin folder from WP-Content/Plugins folder but the error remains.
Thanks in advance for any and all help and advice!
Step 1:
Check your .htaccess for rules enforcing https
Step 2:
Did you replace all links in the database? If not, you must search and replace all links from https://www.business.com/ to http://www.mycompany.com/
You can use a tool from: https://interconnectit.com/products/search-and-replace-for-wordpress-databases/comment-page-4/
Or just use command line wpcli (wp search-replace https://www.business.com http://www.mycompany.com
Step 3:
Open the new 'http://www.mycompany.com/' in a incognito tab. Browser caching might still redirect you to https.
I have a working blahblah.firebaseapp.com default domain working correctly. No problems there. My website was on another provider so I went through the process to connect it to firebase hosting. Everything went fine and the domain status in Firebase Hosting console shows connected for my blahblah.com and www.blahblah.com domains. My problem is that when I navigate to blahblah.com, I get a page that says
I can't find anyone with quite the same issue on Stackoverflow or any other site. There was one that was fixed by opening in a different browser (cached site issue), but this isn't my problem. I have double checked the DNS settings from my provider. Everything checks out. It's been close to 20 hours since I have completed the verification and the status shows connected in firebase hosting. I even re-deployed my site to firebase to see if that would reset something. Didn't help.
So now what should I do? Any ideas?
Assuming you initialized your project with default values, your public directory is what get's served. So, edit or add the index.html file in your public folder then firebase deploy. You should now be able to see your custom HTML.
I had also the same issue, experimented a bit and found the solution.
Case 1- You want your website to be served at subdomain.domain.tld as will as on domain.tld, but added only subdomain.domain.tld as custom domain on firebase hosting dashboard.
In this case the address domain.tld will throw an error.
To get rid of this error add another custom domain in your firebase
hosting dashboard as domain.tld
Case- 2- You want your website to be served over domain.tld but also accessible through subdomain.domain.tld
Add both the domains in custom domain field.
Edit subdomain.domain.tld to redirect at domain.tld.
Case- 3- You want your website to be served over subdomain.domain.tld but also accessible through domain.tld
Add both the domains in custom domain field.
Edit domain.tld to redirect at subdomain.domain.tld.
I have the weirdest problem. I deployed my app to heroku and registered a domain name lets say: xyz.example . I tried to move to this URL and my project was there and working fine, then I tried to move to www.xyz.example and I get a completely different project that exist in my computer but have nothing to do with heroku and never have been deployed to there! Its a static website that has been uploaded to another domain using filezila a while ago. My domain provider is Domain.com. I tried to look there for answer in my domains list but nothing has changed and it's all looks fine. What can it be?
To connect your heroku hosting to your domain name,
you have to open your domain name account and in the DNS Management page add in the cname the host: www and in the point to: your heroku url And in the heroku page in the settings add three domains:
*.xyz.example
xyz.example
www.xyz.example
This should work :) Check this video https://www.youtube.com/watch?v=kKGSGT7mSnQ&feature=youtu.be
I have about five different subdomains on my host that are all working fine with wordpress installed.
I recently switched from Godaddy to Namecheap and bought a new domain name.
I changed the domain on my WHM Server which was all fine with my current sites.
The problem I have is when adding a new subdomain and installing Wordpress the site breaks because of DNS issues.
The Wordpress auto install is also weird as it doesn't detect the root like it used to, it puts the sub domain name into a folder above public_html.
So old subdomains are working fine but adding a new subdomain brings dns errors with wordpress installed.
Any ideas please, I've spent a solid five hours on this already.
Thanks.
If I'm following you correctly, you...
Created an account and bought a new domain on Namecheap
In Namecheap's WHM (Webhost Manager), you changed the domain to the one you had with GoDaddy.
When you create a new subdomain in Namecheap's WHM, it's not resolving the subdomain
So based on the above assumptions, it sounds like your domain is still with GoDaddy, and it's still pointing to GoDaddy's name servers. So if you add a new subdomain in Namecheap, it won't do anything, because Namecheap doesn't have control of the DNS. And for that matter, I think your subdomains would still be pointing to GoDaddy's servers.
Again, assuming I followed your description correctly, I'd recommend you migrate your old domain to Namecheap since, I'd assume, you're going to close your GoDaddy account at some point. If you need to urgently create a subdomain, you would need to do that on GoDaddy's end.
Hope this helps.
Fixed the problem myself, for anyone with a similar issue. I even went through Hostgator support who couldn't figure out the problem.
Logged into WHM > DNS Functions > Edit DNS Zone
The sub domain in question was not named correctly, it was named as the directory name instead of the full url.